2) a strong history of understanding the limits of functional automation (why are there still project managers? Asana exists!)
3) an understanding that progress will slow in this space considerably once we have made the big wins and the hype cycle dies down. (see also; every tech hype cycle)
Yes, it's certainly possible for content to be curated and models to become biased in other ways but...
E.g. If you’re surrounded by yes men who will code whatever without question, product people greatly prefer that, and you end up sidelined.
There’s also plenty of companies who don’t want engineers getting involved with decisions, and product and UX people work upfront and in isolation until you’re handed tiny Jira tickets with Figma mockups attached. Discussion at that point is considered “disruptive“.
It honestly seems like this has gotten worse in the past 5 to 10 years.
I'm amazed at how non-obvious this seems to most engineers and how often this angst gets repeated in online tech communities. I mean, when I was in academia there was a tension between publishing impactful results or cozying up with the right professors into the right conferences vs outputting meaningful work (pressures into p-hacking or having big names author suspicious results is par for the course.) In industry it's the tension between product folks and engineers. Have you ever talked to high-level finance folks who deal with the tension of product folks just wanting to do things and finance folks who remind them how money works?
It turns out that the hardest thing about getting things done with people is... dealing with people. I wish there was a way to remove this weird somewhat-ascetic blockage found in tech communities about this. Many of the more physical engineering occupations have to deal with this in the form of contractors and supervisors. Wait until you have to work on a government contract lol.
When I mentor junior engineers with these feelings, I like to use an adage: "Where there are people there are politics." Look at pretty much any prominent FOSS project and you'll see tons of it (by dint of transparency) and those folks generally focus on the project and not a product!
Finance however, not once[0] have I either observed nor heard of someone working in finance being overruled by a product person. If finance says no go its no go, simple as that. People tend to listen to the money folks, even at a high-level.
[0]: I work both in fintech and have lots of professional colleagues that work at other financial firms from big banks to all manner of investment firms and much in-between, as well as several generations of family who have all worked in finance on various levels. Honestly, its high level finance people trying to pressure others into getting things done faster when they want something done, not the other way around.
Totally, but finance people want to see the company succeed too, and even if finance says it's a no-go, product people will still keep trying to push around them. I just mean that this tension exists between different stakeholders in every organization. If we knew ways out of this, we'd revolutionize government bureaucracies, vastly increase firm efficiencies, sort out FOSS issues, the world would be our oyster! But human coordination problems are really hard. The hardest problems out there really. That's my general point. Too much airtime is given to tech people who seem to not understand this. It's a bit like complaining that when I jump I fall down. I also can't imagine spending 20 years bemoaning this aspect of human nature.
I think this is where the tension comes from in the lasting, I'm still complaining about 20 years later sorta thing. Once you realize the value you are delivering to the company, naturally, you start to want to have some more say over the value chain, I think this is innante to human behavior, but there is alot of gates between ENG and the rest of the org, most of the time, from what I've observed.
Look at, for example, how "Agile" is implemented at a company. It focuses on ENG having to address stakeholders, without really saying that ENG should be its own stakeholder too. With SCRUM and other systems, the emphasis tends to be on outside stakeholders and what they want, rather than bringing ENG to parity with other stakeholders so everyone has more equal input on the work streams - which ultimately, when this is actually done, prevents more problems than it creates, nearly every time - yet you can feel the resistance in most orgs to giving ENG a full table stake
> sad but true: learn "yes" then learn blame other grugs when fail, ideal career advice
> but grug must to grug be true, and "no" is magic grug word. Hard say at first, especially if you nice grug and don't like disappoint people (many such grugs!) but easier over time even though shiney rock pile not as high as might otherwise be
> is ok: how many shiney rock grug really need anyway?
If you look at how "Agile" is implemented in most organizations - even in technology companies! - there's alot of barrier process put up to sideline / minimize engineering input by focusing on stakeholders where stakeholder is defined by everyone telling engineering what to do as opposed to engineering being seen as a valid and reasonable stakeholder too.
I think its because in part there is a linear pipeline that the non technical business side sees as how things go: you plan X, it gets designed by Y, and then "manufactured" by engineers, if you will.
Engineers - good ones, in my estimation - want more stake in each step, both in planning and design, because often its engineers that work on the system the closest (you'd be shocked how many designers don't use their own products on a daily basis, same goes for alot of business oriented folks) and this is not "the way the world works".
Thats my thesis anyway
> best weapon against complexity spirit demon is magic word: "no"
> "no, grug not build that feature"
> "no, grug not build that abstraction"
> "no, grug not put water on body every day or drink less black think juice you stop repeat ask now"
> note, this good engineering advice but bad career advice: "yes" is magic word for more shiney rock and put in charge of large tribe of developer
Perfection
*sometimes probably best just not tell project manager and do it 80/20 way.*
Does 80/20 in this context mean that we'll implement 80% of what is asked for an leave out the remaining complex parts?
What you don't want is for the last 20% to occupy 80% of the time.
But with some luck your project managers' butterfly mind will have flitted on to greener pastures and everybody is happy. No need for Grug to reach for his club (while remaining calm).
complexity very, very bad!
This site has more knowledge condensed in one page than a stack of randomly assorted books on software development do.
I teach the same thing, seemingly every day to my teams. It doesn't work, until it works reliably, within reason.
High-5 from the doers to the teachers! (Both are needed)
For the record, my partner teaches at a major university, just not tech. ;)
The hard part is building things sustainably at scale (people wise or performance wise). That's when a combination of knowing how to manage systemic complexity and knowing how to communicate very well (soft skills) really come into play.
But in general, reaching profitability (which is the real hard part) will require making scaling efficient and operations smooth.
I've been thinking about scaling a bit because I've been digging into a large SaaS product for a client and find I am able to replicate their locally relevant output at a fraction of the cost. Scaling up has allowed this SaaS to serve an entire country but a majority of their user base think in terms of one or two local counties. Consuming their output means subsidizing work they do that's irrelevant to (or might actually compete with) your own interests.
suppose you need to either be in the top percentile of handsome and the top percentile of emotionally aware to get a job as a hollywood actor, but these attributes are uncorrelated in the general population, so 99% of top-percentile-of-handsome people will be top-percentile-of-sensitive and vice versa
then the pool of hollywood actors you observe will contain, out of every 199 people, 99 who are top-percentile-of-handsome but not of sensitivity, 99 who are top-percentile-of-sensitive but not of handsomeness, and 1 who is both
someone observing this result but not understanding the process that led up to it might think that emotional sensitivity makes you ugly or that being handsome makes you emotionally oblivious, even though (by hypothesis) the traits are uncorrelated. in fact, this negative correlation in the selected group can survive even a fair bit of positive correlation between the traits in the general population
similarly, it's easier to get a programming job if you have a history of delivering successful products, or if you have a lot of line-by-line coding acumen
https://en.m.wikipedia.org/wiki/Berkson%27s_paradox#:~:text=....
> the hard part is wrangling systemic complexity in a good, sustainable and reliable way
in an early startup, this thinking is one of the most common ways to failure. people optimise their technology for its scalability, reliability, and "cleanliness", when none of that matters yet. all that matters is finding product market fit
Having an idea is like having a thought.
A startup needs product and distribution. If a tech cofounder builds what’s asked of him and the sales cofounder can’t sell, should the ownership revert to the tech cofounder?
If your product is successful enough that systemic complexity is your chief problem, congratulations, you've made it further than most startups - which die from lack of demand, lack of paying customers, and lack of users giving feedback.
Many non-tech people e.g. look at programmers and think the hard part is knowing what this garble of weird text means. But this is the easy part. And if you are a person who would think it is hard, you probably don't know about all the demons out there that will come to haunt you if you don't build a foundation that helps you actively keeping them away.