Also if your preferred method of non urgent communication is message based such as slack, good luck in an enterprise. Sure you'll get messages, but every one will be "quick call?"
I do this in a startup. Mostly when we have an ongoing conversation and it gets too tedious to explain something elaborate in text, when we could just talk it over and maybe share the screen or look at something together. I get the text-based communication preference, but I’ll stand by calls being far more efficient sometimes.
The Enterprise Experience
21–30 of 158 posts
Re: The Enterprise Experience
#22 - 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 I can escape.
Re: The Enterprise Experience
#23Joking 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 seem only to lead to more of the things they say are bad. In this list we have:
> There are actual opportunities for career development.
Does "career development" just mean "more money"? If so, why not just say "there are opportunities to make more money"? If not, what is "career development" that is not just becoming more deeply buried in an organization with the various dysfunctions described in the rest of the post?
> It's satisfying to write software used by millions of people.
Is it still satisfying if that software is bad, or harms many of those people?
Re: The Enterprise Experience
#24Also if your preferred method of non urgent communication is message based such as slack, good luck in an enterprise. Sure you'll get messages, but every one will be "quick call?"
This ends up a few outcomes, usually positive:
- They give up (pretty common)
- Writing it down helps them to answer the question themselves
- I can directly answer with a response or link to the relevant docs
- We have an actual agenda for the meeting they want to haveRe: The Enterprise Experience
#25Re: The Enterprise Experience
#26Also if your preferred method of non urgent communication is message based such as slack, good luck in an enterprise. Sure you'll get messages, but every one will be "quick call?"
Re: The Enterprise Experience
#27I can't handle such organisations. I simply cannot. I don't care if they pay 3x, they break me within a few months.
I'm currently at $MIDSIZENOLONGERSTARTUP, which incidentally has its own slew of insane and draining things that are breaking me in its own way.
Re: The Enterprise Experience
#28- new leadership will push out the old guard and replace them with friends
- 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
Re: The Enterprise Experience
#29Always 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…
Big companies means more opportunities to lead bugger project. At a big company, it’s not uncommon to in-house what would’ve been an entire startup’s product. And depending on the environment, you may work on several of those project over the course of a few years. Or if you want to try your hand at leading bigger teams, that’s usually easier to find in a big company.
> Is it still satisfying if that software is bad, or harms many of those people?
There’s nothing inherently good about startups and small companies. The good or bad is case-by-case.
Re: The Enterprise Experience
#30It 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…
The only time this shifts is when I have a couple weeks off. During that period I will inevitably start some kind of project, but I have to keep it small, because I know it will die as soon as I start back to work again.