315 private links
In fact, yes for many reasons.
My hope is that as web standards improve, build tools can become slimmer and simpler, because abandoning them altogether is not a good option on larger projects.
For small apps, it doesn't matter.
About the xz backdoor
Another project built in Rust, compiled to wasm and used by a frontend in Svelte.
The feedback of a developers tired of the stress induced by the job, a disalignment of values and d
About learning between humans, it seems. Josh W. Comeau receently shared that the last course "sell roughly 1/3 as many copies as a typical course launch. [...] There's sort of a double whammy with AI:
- Many people are wondering whether developer jobs will even exist in a few months.
- Even if they do want to learn new dev skills, LLMs can provide personalized tutoring so there's less incentive to buy a paid course.
The entire vibe has shifted. The majority of [community] folks are still on Twitter but there’s so much AI grifting and misery and hate in that place. LinkedIn is a parody of itself at this point. Bluesky feels reasonably cosy but way too much of a bubble. The community isn’t there. The forums are dead, the new Discord is quiet.
The website has this comic style UI.
We have founded CTRLback based on shared values and similar experiences in the corporate world. We care deeply about people and the planet, and value them over profit.
Oui, c'est toujours un coût supplémentaire pour un gain minable.
Use UIs instead of writing code. Ok.
I don't believe this is the case. In my opinion, LLMs do not represent a layer of abstraction, but rather a layer of automation. It doesn't abstract away the code layer, it automates it.
I believe in the importance of making understandable software. To this end, I'm working on projects that further this goal.
Primarily, I develop ReTangled, an Entangled-compatible bi-directional tangler written in Rust. It's meant to extend literate programming as far as it can go while integrating it as tightly into existing toolchains as reasonable. As of writing, it's in the early stages of development. I welcome contributions!
YAGNI is not an excuse to never design as some critics have characterized it. If you need it, build it. YAGNI is a meditation on timing. Building structure too soon is as risky as building structure too late.
First bill: optionality
- When you build structure before the feature arrives, you're committing on a guess.
- The feature you prepared for usually isn’t the feature that shows up.
Second bill: NPV
- Money has time value. Structure you build now for a feature due in three months is cost pulled forward and revenue pushed back.
- The bill comes due even when your guess is right.
- The cost of typing the code is not even considered. What about maintenance?
Encore un kudo pour Fabrice Bellard, cette fois de John Carmack.
A way to create demo from UI components: create video in the browser directly, so the recordings can be changed, replayed or its speed can be updated.
The reason I will never go back: it is code, so it is repeatable. A stat is wrong? Change a number and rerun. A beat feels rushed? Nudge one timestamp. Want the same demo for four different products? Loop over four pages and render them all while you make coffee. There is no take to redo and no quality lost to another export.
It seems what the UI does can be a browser extension.
I lost my notes. The post explains a lot that is not considered while "only a translation". From the other specific translations: dates, expressions, name format, etc...
to the undergoing system to be maintained: a N+1 feature (each changes needs to be internationalized and localized accordingly), testing, user tests needs to be in other languages too.
Vendor the dependencies in the project directly. It will avoid to install the dependencies every time.
So just by not updating dependencies automatically, you turn every single package in an ecosystem into a fire-break for supply chain attacks.
A high-reciprocity copyleft license designed to close the SaaS, API, and Code Generation loopholes. If they use your code, they must share theirs.
instead of letting the call stack implicitly control what happens next (as recursion does), store the pending work in an explicit data structure such as a stack, queue, or heap. This turns control flow into ordinary data that can be inspected, paused, modified, or resumed.
Explicit stacks makes interruptions, limits, cancellation or interleaving work easier to work with. It's more adaptable to real-world constraints and test.
A stack (LIFO) produces depth-first search behavior.
A queue (FIFO) produces breadth-first search behavior.
Stop complaining, build as much as possible while you can do it for (almost) free, and enjoy the assets for the rest of your life. Code that you build today will still be usable and valuable in 10 years, and if you build stuff that let you reduce your expenses, you could retire early.