choiway

Good to know that I'm not alone. I now use it for music recommendations (not so great) and keeping track of restaurants I want to try (really good at this but so are a lot of other apps).

This is really cool. Out of curiosity did you know how to do this sort of programming prior to LLMs?

Naming so lit

How much money do you have to raise to buy a decent mic?

If you type a lot for a work, spending the time and money for better tooling is not only healthy but should be encouraged. Unhealthy, is when you try to track down an after market Key Cult for $2,000 and spend $500 on switches because you feel like you have to try them all.

I do like me some static typing but it took me a while to realize that the guards and pattern matching provides runtime guarantees and not just compile time guarantees.

Feels more like a Lisa moment than an IPhone moment.

You're not missing anything if you can and don't mind building a framework of tools that run long running processes, handle the start up, failure and state of those processes and be able to introspect the status and internal state of those processes in a standard way.

The way isolated processes can be created and managed allows for the "let it crash" ideology in Erlang. For example, when you visit a Phoenix Framework site, you have your own process. If I was visiting the same site and encountered a state that crashed my process your process would be unaffected. The "exception" would only affect me until you ran into the same state that caused the crashed.

If I reported the crash to the developer, the developer could fix the bug and soft start the entire application without affecting your process. This isn't possible because of the language per se but really because of the entire Erlang ecosystem around fault tolerance.

*edited for more stuff

Just because a cookie doesn't crumble the same way doesn't mean the cookie isn't crumbling.

Unix Mercenary, LLC is brazenly on the nose.

I got stuck at init

This is the best response I've seen to the question: "What's the easiest way to get started developing a native Windows app". Better than anything Microsoft has put out.

Isn't WPF getting phased out tho?

#1 is the #1 complaint. In 2021, I still don't know what Windows framework I should invest my time in if I want to develop a native Windows app.

Took me a while to realize that ORMs are fine as long as you don't use them for the "R".

It's funny how this context changes the entire the article. I didn't realize that this was related to Mighty and thought it was a good "call to arms" for domain experts in non-tech industries to disrupt their markets.

The problem that I have with Tailwind is that it's not that different than using inlined styles but adds a lot of bloat without a path to clean abstractions.

I hope this is true.

Can't Nvidia do this without buying ARM?

I'm confused. What is it that Nvidia can do by owning ARM that it can't do by just licensing the architecture? Can't they just license and build all the chips people think they'll build without buying the whole thing?

Is this an April Fools joke?

Ending the duopoly is easy: create a payment processing system that charges nothing. However, you start peeling the onion on that and you wonder if it's just easier to create a new search engine.

A couple thoughts after using it for a couple years.

1. It actually takes a while to get your head around the fact that the biggest advantage of elixir is having access to the battle tested features in OTP. It takes longer to realize that these benefits don't come for free and elixir might not be the best solution to your problem.

2. The learning curve for writing functional code is different for different people. As a result, it's impossible to figure out before hand how long it will take a team used to writing pythonic code, for example, to start writing functional, elixir code.

3. You're able to emulate something like type checking between pattern matching and ecto schemas but it's not type checking. Be prepared to spend time coming up with best practices for writing tests.

I don't think the microservice vs monolith process is as cut and dry as people make it out to be. Microservices are hard because abstractions are hard. I've found working on abstracting code within a monolith usually results in better microservices. Haven't seen a good process for starting a project with a series of microservices.

That GUI has aged well.

This could happen in the next year.

Is the $200M net of what he made as employee number 10? Also, Microsoft's stock is up 5x since 2003 so he would have done well by just staying put.

Does he have the Pied Piper USB key?

There's survivorship bias here. Where's the list of companies that pivoted to oblivion?

This article just makes matters worse. Saying nothing would have been better. Not selling would have been the best.

This seriously falls in the "I didn't know you could do that category" for me.

No at the start of a project. Yes for refactoring.

I used to write tests for all pure functions because they were the easiest tests to set up. They are also the easiest to debug so the test didn't really help unless you're checking for type signatures.

I think that implementation tests are important but I found that I suck at figuring our how to set up a test before the actual implementation. So I do them after the fact and judiciously.