Is this a thing? Working in construction is usually my first day dream when I'm feeling fed up with work or a little burned out.
1,144 karma · joined August 19, 2011
Is this a thing? Working in construction is usually my first day dream when I'm feeling fed up with work or a little burned out.
[0] https://github.com/aspnet/KestrelHttpServer
[1] https://github.com/aspnet/KestrelHttpServer/blob/3a424f6abac...
[2] https://github.com/aspnet/KestrelHttpServer/blob/dev/src/Mic...
[3] https://github.com/aspnet/KestrelHttpServer/blob/dev/src/Mic...
Spot on. I find myself frequently and increasingly frustrated with how slow most software is nowadays. Every app in my phone takes 2-3 seconds to load. Lots of websites/webapps take several seconds to load before they are readable/usable (Google Sheets is particularly offensive here).
Years ago I had a lot less hardware than today, and the software I use had less features, but I remember response times being much faster. I hope we're able to reverse this situation soon.
When I was fresh out of college I would jump at any such puzzle that was presented to me and would not sleep until I had solved it. I never stopped to think about the larger picture where that puzzle was embedded in, and if it actually required solving or if a more pragmatic solution was at hand and would lead to the same outcome.
Now that I have some years of experience in the industry, I realize that 80% of the "puzzles" I face at work are bullshit. They are usually complicated situations generated by organic and uncontrolled growth in codebase complexity that lead to horrible scenarios requiring a lot of brain power to solve. The thing is, if things had been more properly thought out, those situations would have not occurred in the first place, because the code would have a lot more sound architecture. But because it was allowed to grow without thought and refactoring, it now offers many "puzzles" that the younger people in the team don't even question at a more fundamental level.
Sorry for the cynicism but it's honestly the way I feel about most of the work I do these days. Too much in terms of stability, maintainability and soundness is sacrificed for performance and for pushing things out the door asap.
What are you trying to imply here?
I'm fairly sure I would fall in OP's "incompetent" bucket, but this point of yours nailed it. I'm not among the oldest people around and I haven't been that long at the company I work at, but I definitely don't have the passion and drive of the single, early 20s guys in my team.
Give me a task and I'll do it well. But don't expect me to be 100% of the time on social media promoting the product, and don't expect to see me voluntarily working nights and weekends just because the product is really cool (which it really is, but it's still work). I have 1) a family and 2) multiple other interests outside of work.
That's what gets to me the most. I'm fairly confident in my problem solving abilities and coding skills. But I frequently lose all motivation to do good work when 80% of what I do is "feed the machine". There are times when doing it makes sense for the problem at hand, and then I feel motivated, but most of the time feeding the machine is about dealing with shitty code, bad documentation and unnecessary overengineering.
Are you kidding? Almost every public school I know of has to run fundraisers because government funding is not enough to last through the school year.
I was quite happy to learn recently that it's pretty popular with my wife's team at Amazon. She had a pleasant surprise when she installed it on her machine and noticed my name in the About dialog :)
It's due for an update though...