16,803 karma · joined May 21, 2012
Phone + not being an english native speaker can result in serious comment injury.
But again ancient greeks complained writing would make people deskill their memory abilities.
And it did.
Yet we don't regret it.
And people still accepted the ToS and fed the machine all their data.
That's why we can't have nice things.
I do want my phone to just go again without complaining without a crash, after all.
You can finish what you are doing right now, and start something else to get a clear view of the next step. Or take something you want to fix, and put a breakpoint it it and plenty of print, to make it sure nothing works and the day after you know where to start.
It's all about breaking the inertia.
But if you want your win, you can have your win.
The truth is we have no idea what will happen. This would be obvious to anybody whole lived through the .com bubble.
Gandhi will not produce an iphone, for obvious reasons.
It came naturally, not out of some design, but I guess having better and better typing support everywhere makes it more and more convenient.
It's declarative, and can scale up to quite complex requirements. But the best things is that it scales down.
It's a design choice by Youtube.
I felt like fighting this fight alone for years in the golden years of node, webpack and react where everybody was creating crazy stacks and adding GraphQL and so on, to basically get what Django + jquery did 10 years ago in a tenth of the time and code.
So far I also survived:
- xml is the future
- let's use nosql for all the things
- you must use the same language at the back and front
- yes, you site must have an AMP version (ah, you forgot this one, didn't you? It was sooo imporant, and then pouf, it was gone like tear in the rain)
- yes, your home page must be an SPA
- you can't code anything without async
- you can't live without a message queue
- everything must become a micro service
- of course you need a container for that
- of course you need a orchestrator to organize those containers
- of course you need the cloud, it would be crazy to deal with those containers and orchestrators yourself
- dude, why do you have a server? Use a serveless backend!
- dude, why do you have a backend? Just call saas from the edge!
Every year, some generation of engineers have to learn the concepts of "there is no silver bullet", "use the right tech for the right problem", "your are not google", "rewriting a codebase every 2 years is not a good business decision", "things cost money".
In theory, they would be the perfect plugin system, but in practice, they are so slow if all your stack add a couple of them, Python start up takes seconds.
And this is why we are all using the .pth hack.
And the rest will follow.
Like every outrage on the internet, it's a tantrum, not a protest.
Because a real protest costs a lot to the people protesting, and you quickly see through virtual signaling once the bill comes due.
Characters scream for a bigger screen, with colorful personalities and back stories, plus they got a design made to scale to awesomeness.
And with the world building, you got a solid base plus endless possibilities.
I enjoyed the game very much, but let's face it, it's too old for most new gamers to appreciate.
Plus on the long run, parskng ruby is difficult for my brain because of optional parenthesis.
Enventuly I sticked to python. I know people critize python packaging a lot, but it was the least of evils in 2010, much better than the competition.
The real magic arrived with GPT3, which is proprietary, so it's fair to assume your audience understands this and imply it.
This is why trip advisor is so useless, at least in France.
Between the vocal unhappy outliers and the happy idiots that think those french fries coming out of the freezer were delicious, the noise/signal ratio is abysmal.
- It will be easy => I will guide you through it
- This will make your life easy => It will make your life easier / It will help you
- To do X, simply do Y => The most common way to get to X is first to do Y