It absolutely fucking BAFFLES me that Brooks’ Law isn’t known by every software manager on the planet.
I’ve quoted it so many times at work, even in engineering focused teams in at least two big tech companies. It’s not a concrete fact, but it explains why so many teams are hilariously shit at delivering software.
I got into cooking during lockdown, and have managed to get surprisingly good at it, to the point where if you asked me to make a meal of your choosing I could probably make it without looking up a recipe. It’s actually unbelievably simple to make even complex stuff, basically using all the same rules you apply at work:
I’ve fought this battle so many times.
My most recent battle was being told to implement Scrum and agile practices. When the subject of standup NOT being a status update came up, and I forcibly told people to keep their updates brief, it was changed to a “Sync Meeting” that lasted over an hour. Apparently, despite delivering stuff faster, being able to track velocity and ensure we’re not overextending ourselves each “sprint”, and actually knowing what we’re delivering through actionable tasks - we’re not doing agile any more…
Out of interest, what do you do and where are you based? It’s a shitty place to work, but if you’re near an Amazon office and you do Amazony things I’m happy to send a reference your way.
I’ll die on this hill.
If you want an easy language for beginners, Ruby is a much better alternative. It’s like a simpler Python, and aside from a crazy loop syntax teaches clean programming principles better than most languages.
With that said, Rails IS a ghetto, and many of the kinds of companies that use Ruby as their main language are stuck in the past or are full of the biggest toolbags you’ll ever meet. DHH, in particular, built a reputation on being a programming contrarian, so much so that there’s a golden rule where if he says something, the opposite is probably the correct choice.
IMO more people should be critical of the systems and tools that they use instead of shitting on the tools that others choose to use.
We do assume too much of our tools, but many people here are guilty of assuming that other OS’s are broken in ways that do not reflect the average customer experience.
Working in Ruby did 10x more to help me write clean code than reading Clean Code ever did.
Many of the lessons drilled into me with Ruby (keep a consistent style, tests are cheap, keep your methods relatively small where possible, reduce nesting where possible) carry over nicely into other languages without needing to go through any OO bullshit.
IMO, the best lesson around Clean Code is this: you’re not clever, write obvious code that works with as few tricks as possible.
You’ve just made your first post regarding Arch. The cycle is complete.
That is a wild assumption with two key flaws
Windows in many workplaces has updates locked down too, except in circumstances where critical security or vulnerability patches are pushed through.
The same is true for many servers that run Linux.
As someone that works on tier1 services for arguably the biggest tech company right now, that’s how it works in most of FAANG. Updates are gated, sure, but like with many things there’s a vetting process where some things that look super important and safe just slip through.
In regards to your edit, I guess most cases are different from others, but if your entire business requires you to be able to use a machine 100% of the time then you should have the means to either use a different machine to continue transactions (ideally one with a known state that won’t change, or has been tested in the last few months). If you need to log transactions and process 24-48 hours later do that on something that’s locked down hard, with printed/hard backups if necessary.
Ultimately, risk is always something you factor in. If you don’t care about 48 hours of downtime over several years, it’s not a huge concern. I’d probably argue that many companies lost more money during these days than they would have spent in both money and people-hours training them on a contingency system to use in case of downtime.
No. If everyone were on Linux and there was a breaking change introduced by a third-party there would be similar problems.
The problem is that critical infrastructure isn’t treated like critical infrastructure. If something you rely on can go down due to a single point of failure, maybe don’t fucking use it?! Have backups, have systems that can replace those systems, have contingency! Slapping Windows on to a small machine and running some shitty Chromium app to work as a cash register is a fucking stupid idea when you consider that it is responsible for your whole income.
The problem was never Windows. It was companies that were too cheap to have contingency, because an event like this was considered extraordinary and not worth investing in.
We installed Slackware. One kid bet me that Linux wouldn’t let him drag his entire drive into the bin to delete. It did, and we all laughed, including the professor - who still gave him the passing grade since he’d seen enough of it working before it went up in flames.
Atlassian is one of those companies that I equally laugh at, love, and hate.
They’re in so many markets in software and project management, and have so many large clients that pay for Confluence, Jira, BitBucket, etc. Despite this, people almost universally despise their products, with bugs being left open for years, features blissfully ignored, etc.
I often imagine what it would be like to work for Atlassian, and what “that” code based must look like. Working there must be fun as hell given the impact and breadth of opportunities, equally frustrating if you dogfood your own products, and infuriating given just how much stuff must be utter shit under the hood.
It’s a mix of both. My wife makes good money as a teacher, primarily because she’s very senior in her role, and takes leadership responsibilities. Teachers are required in (mostly) equal measure everywhere, whereas software engineers always gravitate towards HCOL areas where the jobs are. If you’re not in one of these areas, you’re stuck with limited jobs, with limited pay.
My commute is close to two hours, one way, but the pay I can get here is over double what I’ll get where I live. Comparably, as a senior I probably get paid less than a new graduate in a HCOL city in the US.
My wife is a teacher. Her pay was mostly comparable to mine throughout our careers. My pay has literally tripled since working in London.
Currently, there are senior design and development roles in my home city of Bristol that pay less than what you’d get paid as a fast food manager.
Not all programmers live in the US. In the UK, especially outside of London, the pay is surprisingly bad.
I’m not against bootcamps, but there are so many caveats.
Most bootcamp instructors have no business teaching. They have no qualifications for it, and rarely have the experience to teach the subject matter.
Many bootcamps are owned by agencies or companies looking for cheap labour, with many making false promises on employment - because they give them a temporary contract to get cheap devs. It was painful to see so many bootcamp grads last year, entering an empty market.
They are often very expensive, to the point where I’ve worked with people woefully unqualified, who put up with so much shit because they’re in debt. They were promised a career, only to be taught just enough to do basic tasks in React, and then being limited in what they can do.
You end up with a horrendous amount of imposter syndrome, in an industry where people already feel like frauds.
I’m in the UK, and you wouldn’t believe how many people go to bootcamps and assume we’re all making £100k salaries. Hell, where I live, I regularly get roles for senior engineers that are £40k a year. A woman I used to work with gave up her £30k a year job to be a front-end developer for £20k, with zero benefits, no union, etc.
After a year of Ruby.