1,638 karma · joined April 8, 2016
Abstraction helps you to be productive. It's certainly good to understand everything all the way down to the actual physics behind computing, but its not necessary especially at the start. I don't have to know exactly how logic gates work to program in JS and make a difference. I assume the same applies to ML. Motivation is what prevents most people from learning difficult to learn skills. Finding ways to produce value early on can help keep you motivated.
Doing what's best for the company long term is generally what's best for employees in the long term. Sometimes layoffs are what's best. Companies that deeply care about their employees will still have layoffs.
This one is pretty good.
After that he was Pres of ycombinator for a while.
Lucky? Sure. But I'd guess he's responsible for a significant amount of OpenAI's success.
It may remain, however that doesn't mean the temptation isn't crippled.
A 1 billion net worth person is less likely to be tempted by a $50,000 "enrichment" opportunity compared to someone making $174,000 with a net worth of less than 100k.
I find that hard to believe.
There's plenty of decisions devs make that impact how quickly they deliver a solution.
A lot can be done most of the time to help devs optimize to deliver quickly. However, most businesses get stuck in their ways, struggle to give sufficient autonomy, and... sometimes get burned by giving too much to a dev when they aren't yet ready for it.
In short, getting efficiency "right" is a balancing act, and each "story" could be unique which makes it difficult to balance well consistently.
In my experience, don't get too caught up with estimates. Devs do need goals (even artificial ones) to help focus effort and prevent too much "bad" distraction (sometimes distraction is exactly what they need though--stepping away from the problem for some amount of time can help them look at it differently).
Give estimates. Motivate with goals. Build a real team environment where delivering is contagious. Its actually much harder to do than say, and I'd guess many devs have never experienced this before.
Startups on the other hand, (normally) must accept some risk of failure in order to have any chance of success.
Most startups fail. And everyone involved should know that going into it.
To operate a startup protecting against all risk will likely guarantee failure in almost all cases.
If the actual journalists paid for the blue checkmark, that'd solve the issue wouldn't it?
Twitter prior to Musk was a sinking ship (cancel culture exaggerated the problem). Asking people to pay is one of the attempts to solve that problem. If a journalist is unwilling to pay, they're going to be deprioritized and can't really complain about it. But Twitter has been very open and transparent about the need to reduce bots by paying for the checkmark.
It still is isn't it?
I could buy a 2x4 and smack someone over the head with it. Then they get to sue home depot? No, I should be charged for smacking them over the head.
If the manufacturer becomes responsible for the actions of individuals the economy would immediately cease due to the litigation that would unfold.
Cars kill more people in the US than just about everything. Yet we still drive. I don't think the world agrees with you.
You can be the customer, which helps. But other customers, ideally paying customers, is motivating assuming you have a goal of making some money.
A business requires both.
The fact there's a competitor actually reduces your risk because it shows the market does exist.