But honestly YC probably doesn't even think about any of this, for good or bad. Most companies are super duper behind the ball on privacy regulations, despite the negative consequences.
500 karma · joined September 14, 2022
But honestly YC probably doesn't even think about any of this, for good or bad. Most companies are super duper behind the ball on privacy regulations, despite the negative consequences.
Some parts of GDPR at least call out company size explicitly, other parts allow for "cost of implementation" to be considered, which for HN would probably be "prohibitively high" regardless of triviality, considering the team size.
However what we're discussing here is how the code and otherwise hidden implementation is designed and built. OP is not a UX designer, OP is a software engineer, and should not waste time building things that are "beautiful" in that capacity.
UX and systems design are almost entirely unrelated, and should not spend time in one another's domain.
Wars have been fought over defining beauty, but the important thing to note is that beauty is orthogonal to function. Clean code has clear criteria and value, beautiful code does not.
A program is not like a car, a chair, or a house, and if any of this were brought up in a design meeting for code, you’d rightfully be laughed out of the meeting.
But it’s fine to disagree about these things up to the moment where you attempt to slow progress towards delivery for these values. At that point, the point at which functionality is hindered in any way by your artistry, are you now a problem on a development team.
There are plenty of productive ways to deal with problems, but make no mistake, on any competent software team you will be disabused of this “art” notion, not the other way around.
Ugly code that works pays bills. Beautiful code that doesn't work is, in a very literal sense, worthless.
I'm not against writing clean code (there's utility in that), but I feel like some folks lose the plot and quit their jobs when they can't make "beautiful" things anymore, and I think that's more often a sign of burnout than it is a desire to "return" to creating art.
It's not art. Art requires no function, it exists as a representation. (Professional) code, and software engineering generally, must produce valuable things, and sometimes the process of making those valuable things isn't "fun", but that's never been part of the equation. Aligning "fun" with "valuable" is nearly impossible, and when you try you're dooming yourself to almost certain failure.
This is really burnout, and the mental health effects that cause burnout. I'm sorry the author has gotten to this place, but wrapping it up in "passion" is a disguise.
Nothing is gained without risk, and this woman likely now regrets accepting that plea deal. Her attorney should have explained to her what the outcome would have been for taking this deal, and clearly had she known she would not have, since she is now attempting to have the verdict expunged from her record.
Nowhere did I say, "It is obvious how to design a good microservice." but it seems like you're arguing against that statement, not the one I made.
And for what it's worth, I don't give a hoot who you are, who Bryan Cantrill is, or what your supposed competencies are; make your argument, don't rely on your pedigree to speak for you. That should be obvious.
The real mistake was pleading guilty. She should have gotten better representation...
There is no 9-9-6 culture shift, there is no value shift in software engineers across the country, there is no need to build a Twitter competitor, none of this actually matters.
I recommend you find a way to spend time with someone who knows how to design a quality microservices architecture. It will completely change your opinion about how microservices interact and the supposed "pain" therein.
...which is a fairly obvious observation. "Bad <x> imposes a heavy penalty on team co-ordination" is generalizable.
But more fundamentally, it sounds like you just don't believe the product works, which is fair, just not a very helpful comment. "How would the AI even know what that feature even is?" by learning about how its documented in the rest of Notion.
Fundamentally though, your comment has serious "Uber? No way that's going to work! Why would I get into a stranger's car?" vibes.
Edit (don't want to give folks a second comment do downvote into oblivion): I need y'all to understand, "Just try it." is not the counterargument you think it is. I'd expect that from Scientologists and homeopathy advocates. I don't need to "just try" NSAIDs to believe they work, and plenty of people feel "good" after visiting a chiropractor despite that being much more obvious and clear hokum.
And no, one or a dozen studies do not validate a damn thing on their own. There is not the level of consensus you think there is when it comes to any of this, the article even points this out at the top.
Also most top tier MBA programs are an excuse to get wildly drunk basically daily and make a bunch of powerful friends, so it's very possible most people who go don't learn a damn thing.
From a #teamchaos point of view I'm a little hopeful this new push is a bridge too far, and it gets us to rethink tipping culture.