redleader9345

6 ms·

1.
by redleader9345 5y ago
I've seen companies go on hiring sprees just prior to being acquired, which I don't fully understand. I guess the company tries to puff itself up to fetch a larger asking price? Guessing base cost factors in to sale price. It&#x
2.
by redleader9345 5y ago
Pushing back, standing up for yourself, not being a doormat. All this is key to being treated with respect. The problem is that today, we've got a perfect storm. Developers do tend to be more naturally non-confrontational. Combine
3.
by redleader9345 5y ago
Sometimes it's a matter of hygiene and humane working conditions. You might be surprised at the amount of codebases that are just the equivalent of working in filth. If your workspace has shit smeared on the walls, you don't ask
4.
by redleader9345 5y ago
The quote from this article that really hit home for me, was this: "Coding is generally a team sport. If you’re hacking away on your own then you can do what you want, but when we’re working with a team then we’ve got to discuss our id
5.
by redleader9345 5y ago
The folks in charge who don't want the foot soldiers to have any agency at all, they call it Shadow IT
6.
by redleader9345 5y ago
Well said. Typically in year two your job has more than doubled in the workload and responsibility that you're asked to carry. Which makes the line chart even worse. Pay is flat but the demands of the job are not.
7.
by redleader9345 5y ago
Sounds like Darwin award material. But seriously, those who can't survive the sea change of digital onslaught are eliminated from gene pool. Do the evolution.
8.
by redleader9345 6y ago
Correct. What's best for the long term health of the business is not taken into consideration. The Board of Directors and the CEO only care about this quarter and this year, why would the foot soldiers take a long view? As an enginee
9.
by redleader9345 6y ago
I wonder how much wfh and distributed teams change this dynamic. I totally get what you're saying with the whole experience of staying in the office after dark, ordering pizza, and just working through a problem, whatever it takes. I
10.
by redleader9345 6y ago
"larger group of developers" is the phrase that caught my attention. Humans don't scale well. This is where microservices do become attractive. This service is owned by a small team, and that team makes these types of ju
11.
by redleader9345 7y ago
Just commentary on the engineer turned manager narrative. Please forgive if it is out of place. Should I delete it?
12.
by redleader9345 7y ago
Warning ... cynical, pessimistic viewpoint coming. Here is a pattern that I've observed over a few jobs that I've held as a developer at different companies. Wondering if anyone has any similar experience. The first line manager
13.
by redleader9345 7y ago
Agreed. The market for super snappy user experience seems to be underserved. Maybe not enough demand? Or maybe a symptom of the "everything is free and paid for with advertising" model we have today.
14.
by redleader9345 7y ago
I agree. I've used Octopus to automate deployments of internal LOB crud apps in the insurance space for a few years now. My questions is, is it still aimed at .NET? I know it leans on Nuget as the package repo. But have they broaden
15.
by redleader9345 7y ago
Privacy deprivation. It's cruel.
16.
by redleader9345 7y ago
I've been doing the same. I even tell recruiters and interviewers "if I was unemployed, you'd be getting a very different version of me". It adds more fuel to the notion of why employed people are so much better to rec
17.
by redleader9345 7y ago
Manager of what? Some things require skill, some things don't. Low skill trades can be transformed into paint-by-numbers processes. High skill trades cannot be so easily encoded into a process.
18.
by redleader9345 7y ago
Isn't this really an incentive problem? I find it hard to believe that snoopware will foster a high trust environment.
19.
by redleader9345 7y ago
Every job in corporate land has the person, at every level, who makes you ask "how is this person still here?"
20.
by redleader9345 7y ago
I don't know. But I do know that the way to prevent that is to handcuff all the developers with crushing process heaviness. Then they won't introduce anything malicious, because they won't introduce anything at all.
21.
by redleader9345 7y ago
huh. who'd of guessed that coal miners can't code?
22.
by redleader9345 7y ago
Template zombies, as coined by Mark Schwartz in the book "A seat at the table". Managers who think that they can turn everything into a template, and then hire monkeys to take those templates and fill in the blanks.
23.
by redleader9345 7y ago
Can't one be ambitious about not getting overworked?
24.
by redleader9345 7y ago
If someone has figured out how to measure developer productivity, they're positioned to win a Nobel prize or something. I have yet to see it done. That's why butts in seats is the de facto measurement.
25.
by redleader9345 7y ago
see relevant post from 2017 https://news.ycombinator.com/item?id=15740926