681 karma · joined November 1, 2018
Also, when creating technical docs and presentations, this turned out to be super helpful.
Just a fun side project I figured others might find useful!
Imagine if this was the 1500s and the man in the robe was a priest. Would you be okay with that? and if your answer is some form of distinction without a difference argument, I'd urge you to not even reply.
> Renewables are cheaper now than most forms of energy production. Grids need investment.
> Now we are rich it’s only fair we lead in transitioning to renewables.
> I despair at these short sighted and fairly wrong on the facts views.
The level of arrogance is unmatched while being both factually wrong AND self-contradictory.
Absolute cinema!
Bring the popcorn with you. No need for salt cause everyone got that in spades on both sides.
The difference is in the unit economics. OpenAI has to spend massively per free user it serves. The others you mentioned have SaaS economics where the marginal cost of onboarding and serving each non-paying user is essentially zero while also gaining money from these free users via advertising. Hence, the free users are actually a net positive rather than an endless money sink.
Keep also in mind that AI has always been, and will always be, a commodity. The moment you start forcing people to convert into paying customers is the moment they jump ship at scale.
Just something to keep in mind.
imho, user experience is nowhere to be found in the linux landscape. There is very little focus on that. People will tell you try this or that distro. But once you run into a simple problem, it´s often a rabbit hole of a gazilling cli commands to fix it. In the mean time you´re praying to god to not brick something that used to work before.
I for one think writing code is the rewarding part. You get to think through a problem and figure out why decision A is better than B. Learning about various domains and solving difficult problems is in itself a reward.
This is why Burry, schiff, and a bunch of others keep predicting a collapse for decades on end. They're directionally right, they see a pattern but cant seem to time it right.
My prediction: I think this clusterfuck will keep going until
1. Unbearable irrationality: The US owes more money than there is money in the whole world. Measured using something like global M1 or M2 or something of that nature. Basically the system will need to reach a level of irrationality that even its biggest defenders can't cope with. OR,
2. Demographics: Most boomers die of old age after raiding whatever remains of the treasury.
Coincidentally, if my quick math is right, both of these scenarios are very likely to coincide within the next ~10 years or so. So make of that what you want...
ZIRP, Covid, Anti-nuclear power, immigration crisis across the west, debt enslavement of future generations to buy votes, socializing losses and privatizing gains... Nancy is a better investor than Warren.
I am not defending billionaires, the vast majority of them are grifting scum. But to put this at their feet is not the right level of analysis when the institutions themselves are actively working to undermine the populace for the benefit of those that are supposed to be stewards of said institutions.
I honestly feel bad for people who fall victims to complexity. It burns you out when all you need is to keep things simple and fun. Life is too short for anything else.
Can I ask, what classifies as large scale project for the web?
I previously created and exited a trading platform that did billions in transactions via our servers with thousands of users streaming real time data. It's certainly more complicated and "larger" than 99.9% of things you'll ever do. So does that qualify?
If so, I can tell you that I did it with PHP and no JS frameworks. Hosted on a couple of VPS servers from digital ocean. From idea to execution to exit in ~9 months.
You know what the weird part is? I see your take repeated over and over by "shovel peddlers" and grifters. And every single time it comes with 0 substance or merit.
Even if LLMs were trained on the answer, that doesn't mean they'll ever recommend it. Regardless of how accurate it may be. LLMs are black box next token predictors and that's part of the issue.
Example, lets say a user forgot to provide a password when authenticating, then I will throw a ClientSideException(400, "need password yada yada");
That exception will bubble up to the exception_handler that logs and outputs the proper message to the screen. Similarly if ANY exception is thrown, regardless of where it originated, the same will happen.
When you embrace exceptions as control flow rather than try to avoid them, suddenly everything gets 10x easier and I end up writing much less code overall.
interface LoggerInterface {
// calls $this->system(LEVEL_ERROR, ...);
public function exception(Throwable $e): void;
// Typical system logs
public function system(string $level, string $message, ?string $category = null, mixed ...$extra): void;
// User specific logs that can be seen in the user's "my history"
public function log(string $event, int|string|null $user_id = null, ?string $category = null, ?string $message = null, mixed ...$extra): void;
}
I also have a global exception handler that is registered at application bootstrap time that takes any exception that happens at runtime and runs $logger->exception($e);There is obviously a tiny bit more of boilerplating to this to ensure reliability, but it works so well that I can't live without it anymore. The logs are then inserted into a wide DB table with all the field one could ever want to examine thanks to the variadic parameter.
It´s a semantics issue where the word caching is overloaded depending on context. For people that are not familiar with the inner workings of llm models, this can cause understandable confusion.
Great work. Learned a lot!
Sign me the f up!
In many cases I've seen projects increase their revenue substantially by making simple messaging pivots. Ex. Instead of having your website say "save X dollars on Y" try "earn X more dollars using Y". It's incredible how much impact simple messaging can have on your conversion rates.
This extends beyond just revenue. Focusing on revenue centers instead of cost centers is a great career advice as well.
I know a lot of people on here will disagree with me saying this but this is exactly how you get an ecosystem like javascript being as fragmented, insecure, and "trend prone" as the old school Wordpress days. It's the same problems over and over and every new "generation" of programmers has to relearn the lessons of old.
I get the convenience part. I am from Sweden. We have BankID. I really get it.
But in reality, when centralized systems go to shit, they go to shit REAL BAD. So I personally oppose any such measures on both principles but also... it's okay if life is a little bit less convenient. Not everything needs to be ultra optimized for efficiency. Privacy and systemic integrity is worth at least that much imo.