magic_lobster_party

What’s happening is that support from VC money is drying up. Tech companies have for a long time survived on the promise that they will eventually be much more profitable in the future. It doesn’t matter if it’s not profitable today. They will be in the future.

Now we’re in a period where there’s more pressure on tech companies to be profitable today. That’s why they’re going for such anti consumer behaviors. They want to make more with less.

I’m not sure if there’s a bubble bursting. It could just be a plateau.

Drawing hands is hard

He’s already beyond that

Isn’t problem solving mostly put things together of what you’ve learned before?

I didn’t read everything, but I mostly agree with the author, especially on this point:

While you can definitely abuse exceptions, functional-style error values are not a one-size-fits-all solution.

There are time and place for both. I think exceptions are good for bigger errors. Like database connection errors. Things that shouldn’t happen without any easy backup plan. Those errors might need to be escalated as high as possible where proper action can be made (like resetting the database connection and everything relying on it).

Functional style is great for smaller stuff. Like key not found in hash maps. In many cases there might be good defaults that can be used instead.

It’s a concept of a plan

Haven’t read through this, but this sounds like what C++ is to C. I’m not sure adding more complexity and features to an already complex language is the right way forward. What is needed is a language that cuts down all the burden that has accumulated in C++ over 3 decades.

Something like Zig sounds like the better path forward to me. A completely new language from scratch with cross interoperability to C++. I’m surprised it’s not mentioned even once in the page.

The great thing about Slack is how easy it is to make automations. I guess this one just reads RSS feeds.

At my work we have automations notifying us about production errors for example.

I have a great uncle. The best uncle. He’s telling I’m the best Pokémon player by the way. He works at Nintendo. It’s a wonderful company I tell you. And do you know what he say? It’s all true!

Imagine doing whatever I want with my free time.

It’s an entertaining video. I watched it to have something in the background while doing chores.

I like to mix between OOP and FP for different levels. OOP is great for higher architectural problems. FP is great for everything under it.

And yes, inheritance was a huge mistake. Just use composition and interfaces instead.

It’s headline grammar. It’s deliberate