The Claude frontend skill outputs are already recognizable. Off-the-shelf aesthetics become cringe so fast. See Bootstrap, Material, etc etc.
There’s no way around learning what goes into good design. That means open eyes, lots of practice. Easier than ever but fundamentals same
screenshot of the one-pager version of the servo readiness report
How do we get to more than just three web engines owned by three US companies?
It's a gargantuan question, with no easy or right answer.
I've put together a draft report, thinking about it through a very specific approach - please enjoy:
Servo Readiness Report
webtransitions.org/servo-readin...
Amusing - I'm hearing a comeback of XP (Extreme Programming) practice.
In the early 2000s these used to be popular (championed by @kentbeck.com). Then died down. They are now surging again.
XP practices like small releases, frequent integration, and constant customer input!
Sure, but one thing I find when I understand UI/UX, my designer friend appreciated it that I can emphatize with their works
We cal it as agency over here
I am a developer, but trying to learn about design too. Designers can learn a thing or two about development
You don't have that in Brave
That is one way you have power towards software projects. Fork the projects, improve the designs, and maintain it.
Please, begin forking
I hadn't updated my personal site in 8 years.
Felt a little embarrassed by that, tbh, so spent some time on it this weekend.
www.kevinpowell.co
This will change this year because I plan to train my own llms
I think I just find one of the efficient ways to talk at conferences:
1. build some features on public open source projects
2. present it in conferences.
You get something to work on and you have something to talk about. Skills, contributions, networking, and visibility combo.
Hi, Joyee. I am new to node codebase, but this is a massive PR. How long did it take you this far? Kudos for the hard work. I am gonna take time to read the PR
In Node v20.19.0+, v22.12.0+, you can require commonjs modules from esm files.
Finished two retrospective blog posts on the journey of require(esm) before 2025 ends:
joyeecheung.github.io/blog/2025/12...
joyeecheung.github.io/blog/2025/12...
Hey, Dan. Sorry, I just opened bsky. Did you get a job in Japan finally?
So much calmer here compared to Twitter and Threads :)
Ah, the era of coding with AI. Have you reached a point where you think you "can build" something, but you don't honestly know what the code the AI produces is doing when you look at it? So, how are you going to fix if there is a blocker?
I am in acceptance mode that I will perhaps never train my own llm.
One kernel to rule them all, One kernel to find them, One kernel to bring them all, and in the freedom bind them; In the user space and kernel space where the mind of kernel developers lie.
This project can be an exciting one to contribute to. If you have the skills, consider to contribute. They have been around for a long time. I remember using this software in 2007 and they are still around. That is something about the longevity of the project
Just checked it out, it basically html files on your local computer
rustup doc --book
Cool. It is powerful enough
Hello, anybody in tech? I am a computer programmer in Indonesia.
My daily tech is typescript, but I am drifting towards python and Rust. Let's connect
Screenshot of my Bluesky profile, showing @nicolo-ribaudo.github.io as the handle
Developers, do you want to verify yourself here but don't have a personal domain? You can use your GitHub account! 🦋🐱
I temporarily renamed myself to @nicolo-ribaudo.github.io :)
Sorry, not user interface, but user experience. That includes trying to reduce service time by looking at service time percentiles
![An excerpt from Kleppmann's Designing Data Intensive Application that reads:
"High percentiles of response times, also known as tail latencies, are important because they directly affect users' experience of the service. For example, Amazon describes response time requirements for internal services in terms of the 99.9th percentile, even though it only affects 1 in 1,000 requests. This is because the customers with the slowest requests are often those who have the most data on their accounts because they have made many purchases—that is, they're the most valuable customers [19]. It's important to keep those customers happy by ensuring the website is fast for them: Amazon has also observed that a 100 ms increase in response time reduces sales by 1% [20], and others report that a 1-second slowdown reduces a customer satisfaction metric by 16% [21, 22]."](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:2wwd275ty5rdhb5l45hqdsgk/bafkreih6bq3maeiuugxrkq2ovjqhajbapozicg32rkbk52nxjiqjdomeoi)
An excerpt from Kleppmann's Designing Data Intensive Application that reads: "High percentiles of response times, also known as tail latencies, are important because they directly affect users' experience of the service. For example, Amazon describes response time requirements for internal services in terms of the 99.9th percentile, even though it only affects 1 in 1,000 requests. This is because the customers with the slowest requests are often those who have the most data on their accounts because they have made many purchases—that is, they're the most valuable customers [19]. It's important to keep those customers happy by ensuring the website is fast for them: Amazon has also observed that a 100 ms increase in response time reduces sales by 1% [20], and others report that a 1-second slowdown reduces a customer satisfaction metric by 16% [21, 22]."
Up to this point of reading this book, I get the impression that spending time to make a general rule for every users and to uniform their user experience shouldn't be a goal. Prioritizing a better user interface for users that generates more revenue can be a good goal
