underwater

Look at his claim that Twitter is slow in India because of poorly batched backend calls [1].

He's simply regurgitating what he thinks he heard from others without really understanding how anything works. He knows less about software architecture than an intern picked at random.

1. https://mobile.twitter.com/elonmusk/status/15921762028730859...

> It was extremely demoralising and demotivating

This rings true to me. And I think it extends beyond that to being dehumanised. In a work environment you are made to feel powerless to stop bad things from happening. That breaks us.

A rewrite is not the same as a writing a similar app from scratch.

You need to worry about deciding what functionality to preserve, what to change, and what to throw away. Most rebuilds either fail because they skip this step and the result is inadequate for the job, or they do this step and get bogged down in the minutiae of locking down requirements, digging into edge cases, and stakeholder management.

That's why I said digital noise. If you're using randomness to generate something that emulates film grain then by definition it's not noise, it's a procedurally generated texture.

The point was that many editing tools offer noise generation that works at a pixel level. The author was explaining why those are unsuitable for the task. That doesn't make it nonsense.

The point seems valid: that digital noise will be per-pixel (as will noise from digital sensors). Whereas a scan of film grain is capturing literal grains which will not align perfectly with scanned pixels. The comparison image shows this.

People didn't smile in painted portraits because of cultural norms. A smile was perceived as looking foolish (or drunk). Early photography followed this lead.

A quote attributed to Mark Twain says “A photograph is a most important document, and there is nothing more damning to go down to posterity than a silly, foolish smile caught and fixed forever.“

Some companies uses bare hostnames for internal systems. Those same companies use HTTP Basic auth to log into those systems. And some routers have weird behaviour for DNS resolution, like prioritising .net as the default TLD.

I ran into a situation where, even on VPN, going to https://<company>vacation/ on my home network would take me to https://<company>vacation.net (a valid domain). It would have been trivial for the owner of that domain to phish for credentials.

Anything related to security should fail safe.

Failure is not lack of rigour, it's from fundamentally flawed architecture.

I've never had HR share that kind of information back to me. And I would consider it highly unethical if they tried.

His wife is a pediatrician. She can pay her own way.

I've had a few "well documented cases" shared with me in my time. Generally they are lengthy rants that make it clear that the author doesn't understand the constraints or goals of the business.

Occasionally, there will be some useful insights mixed in, but that is rare. I'd suggest rather than trying to make the case independently, find a trusted party, tell them that you have concerns about X, and let them drive the conversation. You may pique their interest, or give them a chance to validate concerns they already have.

And Fark and Something Awful are both dead.

In a culture that values doing what's best for the people as a whole, I can imagine people seeing it as a duty rather than in infringment of their individual rights.

I can also see those people struggling to understand the American style of fierce individualism that creates so much pain and interpersonal conflict for seemingly little gain.

A meta framework on top of a Meta library?

Not more sensors, different sensors.

In your metaphor it's like asking if you should have project managers as well as engineers on your project. And Tesla has decided that having only engineers allows them to focusing on having the best engineers. And they avoid the distraction of having to manage different types of employees.

You're assuming that the attributes that lead to success in those companies will also carry across. Social media is not just an engineering problem. Elon's personal brand and his temperament is a massive liability for something like Twitter.

OP, you might want to redesign your logo and re-think the name. The logo will be covered by both a trademark and copyright. Eventually Notion will come knocking with a strongly worded letter asking you to change one or both of them.

Every system makes tradeoffs. If you find yourself continually fighting to get something to support your specific workflow, it is usually best to be open to adjusting your workflow. Or swap to a different solution.

In my experience, WSL 2 with Node, Terminal and VSCode has felt like a first class experience. It's miles ahead of WSL 1, which was theoretically a great idea, but failed in practice.

Every manager I have ever worked with has struggled to quantify the performance of their employees, or to define the inputs that affect employee performance. Good luck building an AI that can manage without knowing either of those two things.

Making people like forever would automatically incentivise people to solve a whole host of problems.

The young care more about the future because they worry how emerging problems may affect them, and death is distant and abstract. Whereas older people feel their mortality more concretely, and wonder how they extract as much in the time they have left.

And they sell keyboards that only use the written names, and not the symbols. Plus make common keyboard shortcuts require multiple modifier keys.

Thanks for making flow-runtime. I used it on a previous project and it was so helpful.

OP is clearly not senior. If they were they would know how to get from A to B.

This aligns with my lived experience where many smart, well educated, affluent Americans I met had a shockingly limited understanding of how things work in other parts of the world.

This is still common today. They also run fire drills on a regular basis for major figures.

In that timeline Kodak makes an unbelievably massive pivot from being a chemical company to being a digital camera company, dominate throughout the 90s and into the 2000s, and then get absolutely smashed by Apple in the 2010s.

Ergo, affected passengers need to see infinite number of agents for each trip taken.

IT solves IT's problems by externalising the costs into the teams they purportedly serve.

This is such a naive take. I assume you don't have kids or teens?

Children don't exist in a neat subservient bubble. They have peers, social pressures, see advertising, consume television and movies.

Our kid's school had everyone buy an iPad. Already, at pre-phone age, so much socialisation has moved into the digital space. FaceTime, iMessage, Roblox, etc.

I was going to say banning phones would be like a kid in the 80s without television. But really it would be like being a kid in the 80s who wasn't allowed to have a TV, listen to the radio, have a phone line, and wasn't allowed to socialise outside of school.

The data was gathered from Twitter. I assume engineers from Twitter are much more active on the platform.