There's also a new Dr Eggbot v2 bot template that you can install. It comes with new skills that help with automating your work and life. It's different from the old template, so reinstall this one and ask the old eggbot to transfer anything you want to preserve in the new bot!
https://t.co/wjUP052SmV
@wellzittto@gabrielbuzziv O Dreamina (feito pela Capcut / Bytedance) tá com planos de 1 real pra novas contas no primeiro mês por conta da black friday. Não achei nada melhor até agora.
https://t.co/OJLpoARFWs
Roles are collapsing.
If you're a "Software Engineer" today, you may be a "Product Engineer" soon - with many more responsibilities.
So:
- Learn design/UX/QA/PM skills.
- Focus more on the user, and less on the syntax.
Image via Gartner.
It’s reassuring to see that many people share this concern, and I’m glad most understood that this was never about one component or one project.
I see shadcn/ui components copied and ported all the time. Man, the whole idea of the project is: copy these components. No attribution required.
I’ve welcomed many direct ports, and I’m genuinely happy to see the work reach other frameworks.
That’s also why I didn’t tag the person who made this port. They did nothing wrong.
I wrote the post because this was the first time I had seen something ported so quickly.
The gap between a launch and a port (or a copy) has already collapsed.
This isn’t about open source.
This is about copying becoming automated and infinitely scalable.
And it is no longer enough to say, “Just build better,” or, “They can copy your product, but they can’t copy your taste.”
Anything you put out there can now be copied.
Really fast. At scale.
That is the shift we should be thinking about, and what it will do to the will to create.
"Monolith" is a deployment strategy, not an architecture. All it tells you is that you deploy the entire system in one go. It tells you nothing about the structure of that system.
"Microservice" is also a deployment strategy, not an architecture. Microservices allow you to deploy individual components (that's the architecture—autonomous components) without deploying the rest of the system at the same time.
🚨🗣️ Carlo Ancelotti on why Neymar didn’t play today vs. Japan:
"I was waiting for extra time… I talked it over with him: If we didn't score the equalizer, he was coming in around the 60th or 65th minute."
"I just didn't want to change the structure because we had control of the match."
inference is very profitable and probably a good opportunity to understand some basic business math
1. companies buy long lived assets like GPUs. these are one time costs and the asset depreciates over time
2. once you own this asset, you can plug it in and produce tokens which you can sell. the cost of goods sold here can be very low and you might be making 90% margins at scale, this is why we say inference is profitable
3. then you also hire employees to do r&d work to improve your systems, come up with new models, expand the business
if you add these 3 up you end up with $0. you're not producing a profit because the business is growing and you're reinvesting it all buying assets or r&d to meet demand
if it's obvious to other people the business is working, you can raise money from them to accelerate all these numbers so they max out in 5 years instead of 25
so on paper you'll be "losing money" every year but that's because you want to make sure you lock down the opportunity before someone else
the bigger your market is the bigger this burn can be because it's a function of potential
so when you see these companies losing a lot of money it doesn't mean the whole concept of their business broken
it's possible they misjudge and overinvest on 1+3 and will suffer some consequences but fundamentally 2 does work
@NathanaelBenne7 @WarrenInTheBuff@thdxr I’ve been using asdf for that and it’s awesome. You can manage versions for almost any programming language using the same neat cli