101–110 of 158 posts
Pretty accurate having worked for startups and $ENTERPRISE alike. I recently switched from startup to $ENTERPRISE and the thing I’m struggling with the most is time zones. My manager is 11 hours ahead and infrastructure/security change approvers are 6 hours behind. Now add the big shift back to on-premises infrastructure and it’ll be impossible to get anything done.
Earlier quoted context omitted.
> - groups get renamed for the Nth time in N years. People continue to do the same job, but now the department has an additional "Innovation", "Discovery", or "Leadership" inserted into the title Sometimes, I wish we name the team ‘Pikachu’ and continue on working. This way, others would know the name does not really matter, so they would stop changing the name. The amount of work to change the documentation and lets…
God do I hate teams and systems with cute names. It's all cute and fun until you're the one from another team who needs to integrate with you and decode what Pikachu and Tyrion are responsible for, and discover that Fassbender is just a nickname for a Postgresdb maintained by the "It's over 9000" team. AuthService, CacheService, Db and EntrypointTeam are perfectly fine names. I don't care that namespaces are still al…
Earlier quoted context omitted.
> Does "career development" just mean "more money"? If so, why not just say "there are opportunities to make more money"? That was not my takeaway, because earlier he alluded (twice) to the fact that titles are a thing: 1. A senior technical person who can't turn on a computer and an analyst not being able to speak english, 2. `I have met no less than 6 (six) people with the title "head of architecture".` So I am gue…
I've never understood why anyone would care about titles at all.
I cannot understand this sort of notion at all.
1. You don't care about $SOMETHING - great, I can understand that.
2. You don't understand why others care about $SOMETHING - Sure, I can understand that too.
3. You feel a need to broadcast this lack of understanding to the world - wtf?
I mean, I'm ignorant on a lot of subjects, but I hardly ever boast about my ignorance.
It's like when people proudly tell me "Oh no, I've never been any good at Maths": sure, lots of people aren't good at reasoning, but is being stupid something to brag about?
Earlier quoted context omitted.
> ... Remy's Law of Enterprise Software ... the list of good things at the end of the post. Like the poster of the blog article, I too have worked in very large enterprise. Think 200K staff, 10K distinct servers, etc... I had the lucky opportunity to assist the CTO in hundred-million-dollar enterprise software purchasing decisions. I got to interview vendor after vendor, grilling them to see if they're compatible wit…
> For example, I didn't understand why Active Directory uses search dialog boxes for every "picker" GUI control instead of a simpler drop-down or something similar... until I worked in an environment with 2 million objects in the directory. And that’s when you realize that searching in AD is actually dog slow, and you are better off just syncing the whole thing to a proper database, then checking if the object still…
Because when specialization occurs, every specialized component (including people) is selected against performance and other non-essential metrics.
It hurt to read this. I have seen all of this and more. - Teams that produce negative output for years with no consequence - Six figure monthly AWS bills on unused resources - Technical people who can't use a computer - Constant re-orgs and turn over Wait until this guy experiences the wrath of big consultants... It is hell, but it pays. I get my fulfillment building my own things outside of work and dream of the day…
Amen, Amen... Preach brother!
All this rings true, from the complete org dysfunction, to the security theatre, all of it paints the hellscape of large enterprises in great detail.
My own personal struggles in this corner world resonate strongly here. I worked in a large energy company, with layers upon layers of incompetence and waste.
Including paying a consulting company a small fortune to build a data warehouse that was so locked down that they had to pay them more and regularly, to access the data it contained.
Security theatre where bozos would open your desk drawer if it was unlocked and confiscate your paper notes and books unless you crawled back to the apologizing.
Always worth keeping in mind Remy's Law of Enterprise Software ( https://thedailywtf.com/articles/graceful-depredations ): if a piece of software is in any way described as being “enterprise”, it’s a piece of garbage. Joking aside, I was intrigued by the list of good things at the end of the post. Some I could understand, but some seemed to fall into that strange category of things that people say are good but really…
> ... Remy's Law of Enterprise Software ... the list of good things at the end of the post. Like the poster of the blog article, I too have worked in very large enterprise. Think 200K staff, 10K distinct servers, etc... I had the lucky opportunity to assist the CTO in hundred-million-dollar enterprise software purchasing decisions. I got to interview vendor after vendor, grilling them to see if they're compatible wit…
As paradoxically as it sounds, aside from the rounds of russian roulette my health feels quite good. ... what?
Should you really just accept that and still claim job security?
Is this what stockholm syndrome feels like?
Been at $ENTERPRISE for 18 months. This is true it hurts.