21–30 of 81 posts
I recently read a good medium article[1] about why they are a terrible idea.
[1]: https://m.signalvnoise.com/the-open-plan-office-is-a-terribl...
Besides just spending far too much time on actually doing a chunk of the actual work (which might not yet be commissioned for), I have not found effective ways of fixing this issue.
Thinking you are finished with a project, then taking on another project that's suddenly taking all of your time - while fixing bugs or making improvements to the previous one. Now you're suddenly under a lot of pressure.
I hear that. I was once employed as the sole full time internal webapp developer for a local company with 600-ish employees to serve. Over time, more applications == more code == more bugs == more features/improvements == more "customers" to interact with... Being able to move that quickly was a lot of fun, but managing everything was challenging.
Absolute technical freedom with absolute responsibility.
It's made me very cautious about adopting any 'new'/'shiny' technology, I'm sticking to things that already have mass market adoption and a proven track record because I simply don't have the time to disappear down rabbit holes.
I keep a scratch list of "this looks interesting, check back in a year" and sometimes even then it goes back on the "check back in a year" list.
The need to be stationary for 8 hours a day. standing desks help, but not enough. I plan to start doing yoga, which I think will help with this.
Unfortunately, standing desks, under-desk cycles, and I would guess (though have not tried) treadmill desks, are not complete solutions.
I am certainly not as focussed while I'm using my under-desk cycle than I am when I am sitting still in a chair. It's great for certain types of dev work, but not great for when I need to learn something new or tackle a really critical situation. I wish this work was more physical, but alas, it's just not.
I've yet to see a belts and braces solution that works when introducing it on an existing database (rather than from the start with something like Flyaway).
I mostly like SQL but I kind of wish someone would do a clean slate design of a relational data store and unfuck the last 40 odd years of cruft.
I work in an environment where our data is eminently relational and generally mapping to a relational db type structure is quite simple but actually dealing with the minutiae of the various RDBMS's is just painful.
Earlier quoted context omitted.
I hear that. I was once employed as the sole full time internal webapp developer for a local company with 600-ish employees to serve. Over time, more applications == more code == more bugs == more features/improvements == more "customers" to interact with... Being able to move that quickly was a lot of fun, but managing everything was challenging.
That's basically my job now. Absolute technical freedom with absolute responsibility. It's made me very cautious about adopting any 'new'/'shiny' technology, I'm sticking to things that already have mass market adoption and a proven track record because I simply don't have the time to disappear down rabbit holes. I keep a scratch list of "this looks interesting, check back in a year" and sometimes even then it goes b…