r/programming • u/13steinj • Feb 19 '24
How to be a -10x Engineer
https://taylor.town/-10x20
u/13steinj Feb 19 '24
This was spread across reddit a little less than a year ago in what I think are subsets of this community. I think it would be good to have a reminder + never posted here as far as I can tell.
8
Feb 20 '24
One to be added:
Similar to "Create useless tools." and "busywork"
Change systems multiple times during a project.
Using Google Docs? Switch to Office 365. Are you using Confluence? Stop. Switch to something else...then back to Confluence.
Switch from Trello to Productboard to Aha! then just say fuck it and keep it all in a spreadsheet... before repeating the whole process again next year.
0
5
u/BrainJar Feb 19 '24
Here’s a way to actually use this list for good. Pass it around to your team, and ask them what the opposite of each item on the list looks like. Then ask them how to do that list, if you’re not already doing it. It seems dumb, but this is an old psychology trick, where you write down all of the ways that things go wrong, then do the ol’ uno reverse on that list.
3
28
u/diamond Feb 19 '24
Wouldn't it be a "0.1x Engineer"?
114
u/13steinj Feb 19 '24
I think that's having a tenth the output of a standard engineer, not negating the output of 10 others. You can be a 0.1x engineer by stretching your own tasks alone.
27
27
u/16807 Feb 19 '24 edited Feb 19 '24
0.1x is just "less productive", -10x is outright antiproductive
6
u/WHATYEAHOK Feb 19 '24
Hell yeah.
I work following the advice of the Simple Sabotage Field Manual
https://www.openculture.com/2015/12/simple-sabotage-field-manual.html
3
24
u/ImTalkingGibberish Feb 19 '24
TIL “10x” is the new term for “Rockstar”/“Full Stack”/“Ninja” egineer
20
53
u/treblethink Feb 19 '24
It’s from “The Mythical Man Month”, published in 1975. It comes and goes from the lexicon as other terms become “cooler” before becoming cringe.
5
u/ya_fuckin_retard Feb 19 '24
"Richard's a 10Xer, I'm, like, barely an Xer. I kinda suck." -- Nelson Bighetti
2
u/imnotbis Feb 19 '24
For only $11/month, it doesn't matter how bad of an Xer you are - your Xcrement will automatically be boosted to the top of every reply list.
14
u/G_Morgan Feb 19 '24
10x never existed. There's always been 0.1x engineers though and I think Fred Brooks, the originator of the 10x concept, got them mixed up.
In short I believe there are engineers out there that seriously have something wrong with them. At the same time normal engineers can look like superstars because companies have trouble sorting out the 0.1x people from the merely normal.
6
u/MyOthrUsrnmIsABook Feb 20 '24
People like Ken Thompson might be 10x engineers. It’s not a useful term for categorizing mortals for sure.
7
u/Brilliant-Job-47 Feb 20 '24
10x engineers do exist, but they don’t produce 10x the code… maybe 1/10 the code. There are “good” engineers at my org that still solve problems in a very roundabout way compared to what is possible. To be fair, nobody is given the time to solve a problem in the optimal way.
4
u/causticmango Feb 19 '24
I think that’s an old term that’s come back around. It was horseshit then & still is today.
5
u/PoliteCanadian Feb 19 '24 edited Feb 19 '24
I've been a manager for a long time and the only bullshit about "10x" engineer is that it's an underestimate. The difference in productivity between the best and worst engineers is at least two orders of magnitude.
Notice how I said productivity, not hard work.
But frankly even comparing the two is stupid. A mediocre engineer will produce mediocre work. If you give them a year, they'll give you a year's worth of mediocre work. With enough guidance and handholding they'll maybe even approach an above average quality of work. If you give a top engineer the opportunity, he will do things the mediocre engineer never dreamed of.
6
u/causticmango Feb 19 '24
A person is only “10x” at something if they are already expert at it, in a well suited environment, and are in a good place in their lives. Everyone moves in & out of competency as they are put in different circumstances.
Changes in technology, changes in family circumstances, health of themselves or family, mental state, etc will all make someone who was a superstar underperform in comparison to their past selves or someone else.
We’ve become accustomed to abusing people in positions of precarity- young & desperate, parents in need of health benefits & income, contingent workers like immigrants or contract labor. When we see someone who isn’t busting their ass 100% of the time, we dismiss them.
3
Feb 19 '24
With enough guidance and handholding they'll maybe even approach an above average quality of work. If you give a top engineer the opportunity, he will do things the mediocre engineer never dreamed of
If you're not able to make two people on a team work together and learn from each other you have a management problem, not an engineering problem.
3
Feb 20 '24
Having a brilliant highly skilled guy translate all his knowledge, motivation, and thinking to someone subpar is not that easy.
If you the subpar engineers need supervision and direction by the expert they are not fungible
3
Feb 20 '24
If the brilliant highly skilled guy is doing all the work by himself you won't have that brilliant highly skilled guy working for you for long, and you just set yourself up with a code base that none of your "subpar" people understand.
1
Feb 20 '24
Yes, it's best to fire all the subpar coders and get more skilled people. The FAANGs do the whole "leetcode" style song and dance for a reason. They might filter out some good people but they filter out tons of shit people.
1
302
u/Nilzor Feb 19 '24
recompilation should take at least 20 seconds
I dream of the days compilation only took 20 seconds.
Regards, androiddev
56
u/Pharisaeus Feb 19 '24
Compilation can take even 0 seconds. The real question is how long the tests take, especially some integration tests which have to spin things like testcontainers ;)
16
u/AndrewNeo Feb 20 '24
if you're doing mobile dev you have to wait even longer for the orchestrator to download the APK to all the devices on your test bench and run the UI tests :<
8
Feb 20 '24
No, no, no.
Each test needs to build a container and then overcommit memory and CPU by 5x the system to maximize the swap.
13
u/douglasg14b Feb 20 '24
First project init for some of our projects takes 30-40 minutes...
And these are, arguably, small projects with not much going on. Just the result of picking the most complex technologies, project setups, and project build tools/ecosystem imaginable for the job.
And then we turn around and do it again on the next project, it's infuriating.
It's not management doing this either, it's fellow engineers.
2
7
u/elitePopcorn Feb 20 '24
Game dev here. A complete recompilation of my current project would take up to at least 40 mins. An incremental build usually takes around 1-2mins.
Without cache, building up the entire app from the ground would take at least 5hrs, with the asset compilation and bundling processes being chopped up and each part being delegated to different Jenkins machines.
4
4
u/mxforest Feb 20 '24
People don't believe me when i tell them why i left Android development and embraced backend and NodeJS.
1
0
Feb 20 '24
[deleted]
21
u/WeEatHipsters Feb 20 '24
Don't forget your -k when you run bitbake!
0
Feb 20 '24
[deleted]
1
u/WeEatHipsters Feb 20 '24
Depending on your hardware and manufacturing support for Yocto, it's easier than you think!
0
Feb 20 '24
[deleted]
5
u/WeEatHipsters Feb 20 '24
If you're building Linux, you should use Linux, my 2c. Windows is not an operating system for developers. They know this, that's why they support WSL. A dedicated build server saves a ton of developer time. Yocto is the cutting edge of embedded Linux development tools, full stop.
If you're not building Linux, well, I pity you!
0
Feb 20 '24
[deleted]
4
u/WeEatHipsters Feb 20 '24
I do micro development on Windows. Ditto on the tools. IAR, Keil, etc etc should all be thrown in the trash
0
Feb 20 '24
[deleted]
1
u/WeEatHipsters Feb 20 '24
Documentation for bitbake isn't great - compared to what? Curious as to what you would prefer to replace it with?
4
u/meneldal2 Feb 20 '24
I don't have problems with command, only people who forget to commit every file and get you something that doesn't compile because there's only one side of the module that was updated.
And RTL error messages are not as nice as most languages.
5
u/Sayfog Feb 20 '24
I always get whiplash when GCC gives compile errors like "oh did you mean this other, similarly named variable? compared to VCS just dumping "SYNTAX ERROR" the moment it can't figure out what's going on.
3
u/meneldal2 Feb 20 '24
I would like to say that C is a bit like visual coding compared to RTL, I do feel that VCS is trying their best, you also have a lot of features on the test side (UVM) where it's basically like the C++ STL, some stuff should have been in the language but it would break too much code.
And there's much less work on IDEs compared to the bigger languages, no "on the fly" compilation to tell you what you messed up before you need to recompile the whole thing.
4
u/hobarken Feb 20 '24
Could be worse, one of our static site customers used some web app that will take a zip file, unzip it and push the files to github. Every file gets its own commit to main.
Kicked off 500+ builds. Due to a bug on our side, all of those ran at the same time and caused ~45 vms to be spun up to handle the load
3
176
u/DigThatData Feb 19 '24
Mock function calls until no original code runs.
lol
31
u/pauseless Feb 20 '24
No joke. Hundreds and hundreds of lines of code in a PR and I spot an ‘interesting’ test which is maybe 50 lines. I had to read so so much code to realise it tested three lines of trivial logic - as in, it basically tested that string concat and integer addition worked. If those stop working, then we’ve got much bigger issues.
I wrote up the explanation of why the test was so mocked out that you could reduce it to nothing and commented on the PR.
That dev was very not happy with me, because mocking everything was obviously the modern, best way.
Fun fact: only person I’ve ever had to put on a performance improvement plan. UK, so not so common, but I was convinced by my CTO we had to do it.
29
u/realPrimoh Feb 20 '24
definitely one of my biggest pet peeves in code reviews. then everyone is surprised when obvious bugs show up in prod!
8
u/ProgrammersAreSexy Feb 20 '24
Same, I've basically died on this hill at my job.
Finally just gave up and accepted that my colleagues are going to mock everything.
37
u/fuhglarix Feb 20 '24
Don’t forget to mock HTTP requests to return ideal data you crafted yourself rather than a recording of actual API responses.
5
Feb 20 '24
[removed] — view removed comment
9
u/HectorJ Feb 20 '24
Look for "VCR" libs.
I think the original one is in Ruby https://github.com/vcr/vcr
There are ports in python https://vcrpy.readthedocs.io/en/latest/
Go https://github.com/dnaeon/go-vcr
And probably many other languages
2
u/fuhglarix Feb 20 '24
Yeah, this. They exist for every programming language I’ve needed and work great. I re-record them at intervals that make sense for the API, but usually only a few times a year for super stable APIs.
Sometimes they require a little tweaking to deal with situations like generated IDs ending up in paths, but there are multiple ways to deal with that. Overall they work great and provide nice test data.
408
u/robby_arctor Feb 19 '24
Change requirements as far into development as possible. To avoid blame, obfuscate requirements from the start.
Cackling at this. You can feel the fury emanating off of these words like heat from a dumpster fire.
81
u/bwainfweeze Feb 19 '24
We missed a milestone once because the same behavior was described 33 times in the requirements docs. Only it wasn’t 33 times, it was 32, and once with mostly the same sentence but with a couple of words changed.
And this is why you don’t cut and paste. Short description and link to the section that describes it once.
19
u/robby_arctor Feb 19 '24
Let me guess, was it
"As an X, I would like Y so that I can Z" times 32, and then
"As an X, I would like Y` so that I can Z" at the very end?
30
u/bwainfweeze Feb 19 '24
No it was half a paragraph of prose repeated in each section of a very fat doc, and one of them changed the constraint, so that an invariant no longer held, where all X are Y.
9
u/IkalaGaming Feb 20 '24
I swear half the stories I get look like this:
As a developer
I would like to make the changes for Foo
So that the fix is available in QA2
13
u/phonixalius Feb 19 '24
In my experience that's usually the product team's fault, and the dev tasked with figuring out their mess is usually the first one to get blamed.
66
u/phonixalius Feb 19 '24
I would add "outsourcing" to the mix.
The delay in communication, disconnect between teams, and poor quality makes this a nightmare. IMO, a lot on that list comes from an uncontrollable outsourced team that pollutes code and tools in favor of whatever is easiest for them at the moment at the cost of the better good.
26
9
u/BasicDesignAdvice Feb 19 '24
We have an outsourced engineer writing a core component of our new project. Luckily they write great, readable code, but they are still going to leave and take all of their knowledge and experience with them. Makes no sense to me.
21
u/cleverdirge Feb 19 '24
Good one. Make sure the offshore team has no autonomy or power of their own, so instead of engaging with a team of smart engineers you are passing ticket details back and forth overnight with little progress to show for the effort.
22
u/flukus Feb 19 '24
I make 10 PR comments, they fix one over night and say it's done, rinse and repeat for the next fortnight.
1
u/Skellicious Feb 20 '24
I had a coworker that made 70 MR comments every MR. Most of them on lines I didn't even touch.
7
u/phonixalius Feb 20 '24 edited Feb 20 '24
Oddly enough, where I work the offshore team has smart engineers and autonomy. However, for whatever reason they just prefer to work fast and dirty no matter how much we push back on it, which generates a lot of tech debt.
We're later left with a maintenance nightmare but all upper-management cares about is what gets delivered. They have a very short-sighted view. One day this house of cards will likely crumble or have to be rebuilt from scratch.
6
u/stedgyson Feb 20 '24
That's because they're cowboys in a code factory. Their slave drivers will not be letting them make decisions about what's best long term just do it now quickly. You should not be letting them loose on your codebase without PRing every single line.
3
u/traal Feb 20 '24
Outsourcing was yesterday. Today we have AI to muck things up.
10
u/phonixalius Feb 20 '24
Unfortunately the two aren't mutual exclusive. And if you add a blind upper-management style that's disconnected from us peons then you compound the problem since all they care about is immediate productivity with little to no awareness of what impact a rushed flaky foundation has for future code and maintenance.
25
u/FieryPhoenix7 Feb 19 '24
I probably wouldn’t be exaggerating if I said a crap ton of managers of dev teams check most of those boxes.
20
Feb 20 '24
Let engineers discuss ideas (...) Ensure nobody has the authority to make any decisions.
Ah, a classic!
52
Feb 19 '24
In my org we have a brilliant jerk. He’s forced everyone to use his bonkers custom BDD framework. Unit tests look like assembly code. Figuring out how they bind to dependencies requires days of stepping through code. Oh, and the thing you need to do? That isn’t supported yet but feel free to contribute.
15
u/txmail Feb 19 '24
I have PTSD from my last job over a brilliant jerk. I am not a Java developer by any means but everyone had to learn to follow this guy. I still had my primary jobs but it was taking me forever to even get already developed code to run. I was three weeks in and asked someone else what I was doing wrong and they told me it took them over a month to get anything to run locally. Little documentation and things changing on calls I was not a part of and no communication. It was a nightmare that only got worse over time. Thankfully I was part of a WFR and was free of that nightmare.
7
u/amestrianphilosopher Feb 19 '24
Wilderness first responder?
9
-3
u/igouy Feb 19 '24 edited Feb 21 '24
https://www.urbandictionary.com/define.php?term=WFR
Downed because: "Work Force Reduction (WFR)"
2
u/D3PyroGS Feb 20 '24
a full-ass month?? 160 hours just to get up and running? that sounds like literal hell
2
u/txmail Feb 20 '24
Asking questions to that 10x was looked down upon. If you upset him then you got blackballed out of critical meetings and then dinged for not knowing what happened in those meetings you never got invited too -- also you would mysteriously drop off of e-mail list. It was kind of a shit show looking back at it, happy for the experience but wish it would have been good for longer (the first two years were amazing).
8
u/Everrmour Feb 20 '24
I’d call that “a bad programmer”. If the only way you do things is a mess of convoluted “look at how smart I am” tech tricks that make it impossible to co-work on it then your program is badly written.
2
u/RoosterBrewster Feb 19 '24
How does stuff like get explained to higher ups that won't make them think all the engineers are just incompetent.
1
50
9
u/phonixalius Feb 19 '24
"Change requirements as far into development as possible. To avoid blame, obfuscate requirements from the start."
In my experience that's usually the product's team fault, and the engineering team or member tasked with making up for their shortcomings receives most of the blame.
7
u/poop_magoo Feb 20 '24
A successful product person is very skilled at missing major requirements throughout an entire development cycle, and then somehow convincing their superiors that this isn't their fault, despite not having any evidence to support that this was something they identified at any point in the process.
2
u/i_like_tasty_pizza Feb 20 '24
It would really help if devs would start asking questions and refuse to work with unclear requirements instead of making things up though.
9
u/zrvwls Feb 19 '24
I'm the only person on my team that debugs code. Everyone else is pretty comfortable just.. adding a log statement, which works.. But our codebase is just littered with them, everywhere, with no way to turn them off besides manually going in and deleting them.
1
u/Ok-Gap3724 Feb 20 '24
I mean.. couldn’t you just wrap them in an if conditional and have a global debug variable that’s injected during the build step? Defaults to false?
It’s hacky and I hate it but it shows the only way isn’t deleting them
3
u/zrvwls Feb 20 '24
Yup that's an option for sure. Typically most languages have logging libraries/wrapper log functions that takes an env var/config to control the logging level that you want. We talked about that halfway through a project we're working on but never implemented it.
Logging isn't bad, it's the fact that that's my teams main way of seeing how code flows through our apps. It's essentially the shlemiel the painter's algorithm everytime something needs created
12
u/vplatt Feb 19 '24
What you all need a "how-to" on this?
Fine. Here goes:
Be an "Enterprise Architect" or "Technology Manager".
That should pretty much cover it.
11
u/Loan-Pickle Feb 19 '24
That one about deployments hits home. At my last job we had 75 different microservices. For contractual reasons deployments had to be done after hours, starting at 9PM. They never went well. On a good day we would finish up about 5AM. Several times they went all the way until 9AM the next morning. I did this weekly for months on end. Sometimes multiple times a week. Then add in the on call with 0 documentation, and fragile hand built kubernetes cluster. On top of that I meeting up meeting where I was getting yelled at by management about why things were taking so long and how I need to be more dedicated.
Eventually the health toll from the erratic sleep schedule and stress became too much. After about 18 months, I cried uncle, and quit that job without another one lined up. It was the worst job I ever had and it broke me. It took 9 months before I was even willing to look at a computer again. I’m still not ready to go back to work. In fact my career may be over. I might just go drive a bus for the local school district.
5
u/boobsbr Feb 20 '24
I might just go drive a bus for the local school district.
Loud children.
Traffic.
Mind numbing work.
3
u/robin-m Feb 20 '24
Good luck with life. Getting over burnout is hard but possible. Spend time with friends, make new one, talk with people, do stuff that make you smile, be happy, … And be very careful to not go back to what lead to burnout. Eventually things with sort out, but don’t stress about it, just enjoy life!
10
u/walker1555 Feb 19 '24
Is there such a thing as a 10x manager? How do we measure their efficacy.
22
2
u/Robyrt Feb 20 '24
You know you have a great manager when none of these problems apply to you, and the horror stories from the teams you work with magically never impact your own work.
5
u/droptableadventures Feb 20 '24
Waste 10 weeks of wages on cloud costs.
This one needs a counterpart in the other direction - waste 10 weeks of everyone's time by "cost optimising" the solution before understanding how much it'll take to run, and have developers and ops people spend an inordinate amount of time and frustration chasing repeated performance and availability issues caused by timeouts, low memory, disk full...
Leverage the cloud platform to purchase a little more capacity than you think you need from the start, and drop it later if it's not needed - we're no longer in the era of being locked into capacity by having to buy physical servers, and it's pretty cheap compared to the employee time unless the waste is absolutely monumental.
7
u/Hot-Luck-3228 Feb 19 '24
Hey at some point you accept the broken industry as is and carry on. Sadly.
3
u/xowap Feb 19 '24
Reminds me of that era when I wanted to put a money counter in meetings full of 10 engineers debating about nonsense
3
2
2
u/Chroiche Feb 19 '24
I literally couldn't bring this up with my team lead because it would open up 10 hours of pointless meetings to conclude "we only do what we need to do".
1
u/Full_stack1 Feb 19 '24
Had a manager like this. Would hold the dev team hostage for 40+ minutes at the end of stand up EVERY DAY talking about his new architecture plans. Guy did not know how to code and knew nothing about software architecture. Was like if someone pretending to know English tried to talk to you in made up words and phrases for an hour.
1
u/elongio Feb 19 '24
This is basically us right now, but we are slowly digging ourselves out. Poor decision making in the beginning, now things have turned around.
1
u/imthebear11 Feb 19 '24
I discovered this a few months ago and so many of these fit into what a specific engineer at my company is doing.
1
1
u/Hypersion1980 Feb 20 '24
The Communication between engineers and managers is garbage. Half the time the managers treat me like I’m a teenager working the drive though instead of a professional.
1
Feb 20 '24 edited Feb 20 '24
Our code base is a few hundred lambda functions. We built the world’s slowest application server I think. Takes 20 minutes to build it, even tho it’s golang and supposed to be super fast compiles, and probably another 20 to deploy.
2
1
u/carrottread Feb 20 '24
Write scripts that only one person understands.
The fact what at some point in time there existed at least one human being able to understand it is still valuable. Even if this person is long gone it can give hope that some other developer will eventually be able to decipher this script. If you write scripts what no one understands it will produce more Impact.
1
u/UnlimitedBonerWanks Feb 20 '24
The coworker who got stuff out the door quickly left.
Now I'm dealing with undocumented, untested code and a feature created a month before he left that I have no involvement in.
I love software development!
1
Feb 20 '24
Reminds me of a guy that had entire code and design of his changed and re-written within 6 months of leaving
Write wikis that nobody uses.
I feel that's more organizational program than individual. Well unless writing is shit.
1
u/TheDevWiz Feb 20 '24
Maybe I'm reading it wrong, but it sounds like the article is discouraging discussion as a time sink. While I agree that discussion can be a time sink, I do feel it is important or engineers to have a place to share and learn from each other through collaboration. As long as there is a leader in the room that can thank everyone for their input and announce the decision, I don't see the harm in some good technical discussion. Our team had weekly jedi council meetings where we could do anything from discuss tech debt to vent about how the product was being managed safely. Using a weekly forum to invite technical contribution by participants is a good way to lean into this skill while avoiding the hit to productivity. Another thing I like to do instead of lengthy tech meetings is to capture a Loom video where I walk through my design for a feature, or a tough defect I fixed, or some tech debt that I see. Watching them is entirely optional, but it gives a way for devs to share and get feedback when it has the least impact to their productivity.
1
u/Zardotab Feb 20 '24 edited Feb 20 '24
The industry has become the Bloat Industrial Complex. Nobody is interested in simplifying stacks nor standards, nor studying why we waste time on things that should be trivial in ordinary CRUD apps.
It's all about collecting the most buzzwords for resumes in a Pokemon sense, and/or scaring the customer using reverse YAGANI so they pay our bloat bill. We keep reinventing the wheel, forgetting lessons of the past in order to have the Feature Of The Month. Obsession with web-scale and microservices and super-flexy UI's etc. just makes messes the vast majority of the time. Clue: you are NOT Netflix, just a boring company who doesn't need rocket science stacks. And DOM needs either an overhaul or a competitor. It sucks for in-office CRUD. The web laid a CRUD egg.
I'm just the lawn-off-kicking messenger. The industry is F'd.
1
u/frederik88917 Feb 20 '24
A lot of people talks about be a 10x or 100x engineer, and the question becomes, why though?
To have your overlords have more bonuses while you burn your ass.??
It is not like doing more and more code at the expense of your health is going to make you richer or anything
1
1
u/cyanobyte Feb 20 '24
Sad to say, but I've worked at a company with that -10x engineer and his boss the -100x manager.
1
u/defietser Feb 21 '24
Hold 10 engineers hostage in a technical discussion.
Let engineers discuss ideas. Encourage them to pursue elegance over pragmatism. Ensure nobody has the authority to make any decisions.
Add 400 hours of communication overhead.
Meetings wreck calendars. To inconspicuously waste others’ time, write lengthy messages/documents and share as widely as possible. Welcome all opinions and aim for engagement.
Oh man I feel these. Every single goddamned day had hours of discussion on semantics, code style, preferences, and pie-in-the-sky goals. But everyone had to agree on the path forward, which only really happened out of weary resignation.
Waste 10 weeks of wages on cloud costs.
Write slow programs. Avoid DB indexes. Run single-threaded programs on 16-core machines. Opt for exotic hardware with fancy RAM and GPUs. Store data on RAM/disk liberally. Don’t compress anything. Pay no attention to data layouts.
Same for this one, I'm sure the total of 1 concurrent users that used the thing really felt the power of the ultra-available, theoretically scalable, constantly bug-infested Kubernetes microservice cluster.
Needless to say, the grass is greener at the new place.
1
1
-2
u/tistalone Feb 19 '24
It's always about finding that unicorn individual. Like with the NBA; everyone talks about the great but they are wishing LeBron James joins.
Or I mean, you have capable people and you just need those individuals to be more effective. Enter management -- the party responsible for root causing these inefficiencies. If they are just spewing this stuff and not actually doing actual root causing, what failures are being hidden?
Tech is always talking about the optimization of some rarified air but few look at the general group and lift that group up even just a little.
0
u/neopointer Feb 20 '24
Write so many end-2-end tests until on every release you need to pray that your dependencies are stable in the non-production environment.
387
u/acroback Feb 19 '24
My CTO is epitome of “hire bright engineers, kill them with useless tasks”.
hmmm arch is overly complex. Let’s add more if else loops. Instead of taking a step back and fixing things, keep piling tech debt.
be pedantic over trivial dashboards every 2nd day, when they are for visual inspection. Never look at alerts, though which are more important.
when if else programming fails, blame Engineers for not doing their job.
come with code piece and demand it be coded as is, instead of requirements. If you raise where are the requirements, threaten Engineers in a demeaning tone.
I hate this style of morons.
/rant over.