gregors

Nintendo Switch

The majority of places I've worked don't adjust business rules on the fly because of flexibility. They do it because "we need this out the door next month". They need to ship and ship now. Asking clarifying questions at some of these dumpster fires is actually looked down upon, much less taking the time to write or even informally have a spec.

Timely post as a TN power plant is offline

https://www.local3news.com/local-news/tva-takes-sequoyah-nuc...

Timescale is sooooo much better. What a bad decision.

I think it depends a bit on perception. If you're coming from C, Go is a step up in my opinion. Everything surrounding Go's type system and lack luster error handling seems worse to me coming from almost any other language - except C.

Concurrency is also something they got more or less right. The most important thing is that they invented their (Google) language that they could exert complete control over. From a business perspective specifically, that was much better than Java.

>>>> n the study, the researchers leveraged data from 1.1 million Swedish men

So in other words, light years better shape through out all age ranges compared to your average American.

>>>> The simple great thing about doing everything through a single process (with threads, goroutines, or whatever inside it for concurrency) is that you have all the shared state you could ever want, and that shared state makes it so easy to do so many things.

If you like the sound of this, check out Elixir/Phoenix

Works completely fine in Haproxy

I'm actually happy about that. It specifically targets gamers who want to play video games.

So yeah you can say it's entitlement but if you build your business in one way and then change the fundamental limits AFTER you've gotten market saturation you really shouldn't be shocked at complaints. It's their fault because they fostered the previous user behavior.

People understand that bandwidth costs money but that seems to have been priced in to their previous strategy or they did it knowingly as a loss leader to gain market share. If they knew this was a fundamental limitation they should have addressed it years ago.

>>>> That's his decision to make and he doesn't owe anyone anything. If you want continued support, pay up.

Completely correct, and the users of Elm also don't owe him anything. They are free to hold their opinions and free to move away from Elm ...and they did.

In the end Elm will be remembered for being an extremely interesting technology but mainly failed in industry due to poor project/community relationship.

Sometimes interesting tech just isn't the right fit for business. C'est la vie.

It would be good to remember Joel did a complete rewrite and blogged about it.

https://www.joelonsoftware.com/2002/04/11/our-net-strategy/

The idea isn't that you can't rewrite in a new language, it's that want to do bit by bit. Don't just to the big bang thing.

Boring tech is really better described as extremely late adopter strategy.

Maybe it makes sense for your business maybe it doesn't. If you don't want to be on the forefront of technology, well don't. I don't think that launching every startup using the late adopter strategy is necessarily going to result in better business performance. Those that find a better way to do things will win.

>>>> We are destroying software by jumping on every new language, paradigm, and framework.

The young grow old and complain about change. The cycle of life continues.

The mba is definitely an amazingly refined laptop. I've purchased 2 over the years. That being said, I'd still be very interested in a linux powered snapdragon laptop.

AI imagery is pure disgusting garbage. It's 100% worse than no image at all. Anyone thinking of using AI imagery .....don't.

shopify, airbnb, github, hulu ....managed to make it work

It's always been a non-issue for me. However, when I do want to explore a new stack I generally go as a consultant or in a small startup i.e. not-well-funded. I'm more than willing to pay the price in wage for a few shorter-term engagements.

Rails is pretty amazing to get started. Rails is definitely the gold standard when it comes to Get Shit Done fast. I think the Active Record model can lead to some technical debt down the road, but for getting started nothing is faster from a dev perspective.

All that being said these days I'd start with Elixir/Phoenix.

Lots of other countries other than the US banned this dye years ago. So what changed in the US? Logically speaking we didn't just come to our collective senses. Did government lobbying budgets dry up? Or did the cost just increase where it wasn't worth paying anymore?

OKRs are a complete waste of time for everyone involved. Just avoid this corporate nonsense.

It's because it's not a race track. Race tracks are designed with safety in mind. Large areas on the outside of curves, gravel runouts, and padding on all fences.

The TT is a street track with rock walls, telephone poles and stop signs. Those things don't exist on race tracks for a reason. You're going to have a bad time hitting a rock wall at 180 mph.

You clearly come from a country without a social safety net. Most people never make it to the olympics much less professional sports. So all the people who don't make it die? No they transition into other industries.Trying and failing is much better than never trying at all. Long live the dreamers and artists.

>>>> there’s basically no money in it

Who cares there's no money in it? Lots of things that have been corrupted with money are also hardly worth pursuing.

Exactly this, the landing page seem much more about the reference implementation than the actual protocol. I will say the docs at https://mercure.rocks/spec are nice.

Lawmakers are generally beholden to their lobbyists i.e. the people who give them money. They don't care about anyone's safety, health or well-being. They do however, care a great deal about corporate profits.

That's the system we've built, and it's a very good one if you're a corporation.

Just keeps getting better! Congrats!!!

>>>> This kind of coordination is impossible in larger teams,

And that's the real reason service architecture took off

A story as old as acquisition itself

This skit on rails conventions is ancient, but I will never think it's not hilarious

https://www.youtube.com/watch?v=obOd7WrrTWQ

There's been arguments over the years that push back to rails magic led to a new generation of explicitness. You're also correct in saying that it's part of the value prop for productivity. But there's an overhead to learning the conventions in the first place and these days there is no denying less and less people are coming to Rails and even less learning Ruby. That's just the lifecycle of software I suppose. I'm extremely grateful for the large companies with massive ruby codebases that continue to move the language and ecosystem forward.