To prepare for potential layoffs and job searching , I've been thinking of writing blogs about internal tools I built ( especially with AI ) during my years at Dell that has saved my org millions. Figured it might help build a strong portfolio..
Though how exactly would I write about this without compromising the company? Should I open a request to legal team and send them my drafts?
@a6 Not necessarily. That depends on a LOT of factors. Specifically what the contract says when you first sign as an employee.
As an example, if you wrote a script that assists in migrating xyz tool to a different tool and it was not during your employment at xyz company (maybe for another company, or just for fun,) that would not be company property even if it's used while you are employed at xyz. Any tool that is copywrited by you, can also not be company property/owned.
If this script is not required to be created by Dell, and is not part of your job duties, and you create it outside of working hours (not that they'd know) on your own machine, Dell cannot "own" it.
Get back to work.
@df - no one will buy it just like Michael's latest book. And you won't have a bunch of employees to dump them on for a write off
I kept a journal, not a blog, about my journey and frustration with Dell and their false starts with AI. I have retired. I am looking into turning it into a book
@OP You can talk about WHAT you did but you can't talk about HOW you did it, or how it was implemented. That would be a violation of confidentiality you signed as part of your employment contract.
I suspect most people reading an external blog like that couldn't care less though about internal improvements At Dell. Everyone already knows you can swing a dead cat in any direction and hit something that desperately needs improving.
Yes you can.
@a6 I tried to use AI and it told me the same thing you did. Except if I exclude all of those details, then there's really nothing left to write about ! I can't talk about the software architecture, the data I talk to, so what is left ? Nothing! I can, then at best write about the generic stuff.
So I guess it's no use after all...
@a6 Dell's AI probably recommended asking in this forum.
Dell owns the tools you built. List your skills you used to build the tools, but you have to protect confidentiality, architecture details, data sources, and internal names. No screenshots.
I'm confused though...if you've used AI...I would think you'd be savvy enough to just ask AI how to go about this. I guess you still need to be micro-managed.