He/Him; Senior Software Developer, IT Swiss-army-knife, 3 programming blades, 1 hardware, 1 networking and infrastructure and a corkscrew. The tweezers have long since been lost. (Recent ADHD diag.)
All of them?
Personally, more seriously I have about 3 that are 'current' as in I'm planning on returning to them in the near future.
I also have about 7-10 future projects that have initial planning done, and are waiting on cycles to flesh out the details.
Professionally, for work, about 4. I usually have tasks assigned on multiple projects in a sprint and require feedback/input on those tasks during the sprint so they get worked on until that happens, I reach out and context switch. Not idea, but it's the reality of the situation.
He/Him; Senior Software Developer, IT Swiss-army-knife, 3 programming blades, 1 hardware, 1 networking and infrastructure and a corkscrew. The tweezers have long since been lost. (Recent ADHD diag.)
I'm a software developer at a company who's primary product isn't software. But we integrate with TONS of vendor stuff and have lots of internal products to fill small gaps. We probably have about 150 indivudal software products, comprised of 1-4 components (binary, web, data, reporting assets)
Only having to keep 4 projects in my meat-based-memory at a time is a good day.
At one point, I was the internal software developer for the company I worked for at the time. I developed many small programs to automate things in the company (ASIC International - We developed ASIC chips for other companies). Internal company software is a common thing.
I had worked for another company that built embedded diffibulators where everything (OS, hardware, software, etc) was internally made. Very inefficient and a maintanance nightmare, but it did work well together.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
All of them?
Personally, more seriously I have about 3 that are 'current' as in I'm planning on returning to them in the near future.
I also have about 7-10 future projects that have initial planning done, and are waiting on cycles to flesh out the details.
Professionally, for work, about 4. I usually have tasks assigned on multiple projects in a sprint and require feedback/input on those tasks during the sprint so they get worked on until that happens, I reach out and context switch. Not idea, but it's the reality of the situation.
Seems like a lot of sides to be responsible for š
I'm a software developer at a company who's primary product isn't software. But we integrate with TONS of vendor stuff and have lots of internal products to fill small gaps. We probably have about 150 indivudal software products, comprised of 1-4 components (binary, web, data, reporting assets)
Only having to keep 4 projects in my meat-based-memory at a time is a good day.
At one point, I was the internal software developer for the company I worked for at the time. I developed many small programs to automate things in the company (ASIC International - We developed ASIC chips for other companies). Internal company software is a common thing.
I had worked for another company that built embedded diffibulators where everything (OS, hardware, software, etc) was internally made. Very inefficient and a maintanance nightmare, but it did work well together.