226 private links
From a designer that ask for help. They design their prototypes on Figma.
Hyping yourself is about accurately explaining the value that you contribute. It’s about saying, “Here are all my accomplishments; here is what I’ve been up to; here are the ways that I’ve been growing and will continue to grow.” You demonstrate to others why you’re worth it and you show up with the receipts to back every claim you make.
Keep a Hype doc for it.
A Hype Doc is a running list of all your accomplishments and successes. It’s a place where you keep track of your growth, and regularly jot down the things you’re proud of doing.
It includes: technical work completed, projects led or contributed to, mentorship and development, leadership opportunities, blog psots and talks revelant to your work, involvment in recruiting and interviewing, valuable contributions to discussions, kudos and feedback from others, significant moments of growth or learning.
Update it regularly (weekly?), it should be easy to edit and can be shared to managers.
Compiling Rust with GCC?
Follow up: https://blog.antoyo.xyz/development-rustc_codegen_gcc-2
I didn't read but it can be useful someday.
What is a computer club?
a computer club is where a group of people hang out and do computer together
Doing computer is whatever you want...on computers, together.the political economy of computing is awful. have you read palo alto? me neither. we should read it. we deserve better than the darpa-funded visions of xerox parc technologists
Rules
- Hang ou in real life
- reject corporate sponsorship
- computer club is a collective project
Guidelines
- computing is political
- the recurse center social rules foster collaboration and psychological safety
be inspired by permaculture, small web, diy culture, computing as a medium through which better things are possible - try to host computer club's stuff on your own computers in the place that you live
- be open to interdisciplinary computing
- be open to different histories and "skill levels" with computing
There is also a list of computer clubs and a list of tools
Technically this whole site is already about me.
After seven years working as a Network Technician, I switched careers to be a web developer.
I.
Most things fail because nobody cares.
II.
Let’s start with what doesn’t work: copying success. Everyone trying to make the next Facebook creates a wasteland of social networks nobody wants.
III
Here’s the core principle: people give a shit about things that meaningfully change their lives.
IV
Solving real problems isn't enough. You also need to solve them in a way that resonates emotionally.
V.
Why didn't someone do it sooner? Because the obvious solution was previously impossible, illegal, or insane.
The sweet spot? When something just became possible, legal, or sane enough to try. That’s why timing matters more than ideas. Being too early is the same as being wrong.
VI.
Communicate why anyone should care. Focus on outcomes.
VII.
Making something people care about often means making something people already care about, just better.
VIII.
The most successful products are often worse in most ways but radically better in one way that matters.
IX.
Sometimes, making something people care about means removing things people hate.
X.
Finally, there’s the hardest truth: you have to give a shit yourself.
XI.
Hit 6/8 (from III. to X.). More is overkill. Less is self-sabotage.
making something people give a shit about doesn’t mean making something perfect. It means creating something meaningfully better in a way that touches people’s lives.
In the end, people don’t care about products, features, or specifications. They give a shit about their lives being better. Everything else is just details.
(XII.)
creating something people give a shit about isn't enough – you have to remember why they gave a shit in the first place.
How to destroy softwares on the long term?
Avoid, at all costs, arriving at a scenario where the ground-up rewrite starts to look attractive
Aim to be 90% done in 50% of the available time
Think about pathological data
Edge cases are our entire job.
There is usually a simpler way to write it
Write code to be testable
It is insufficient for code to be provably correct; it should be obviously, visibly, trivially correct
Try writing a tax code in chat messages. You can’t. [...] That’s why we use documents
You program by writing documents instead of chatting.
It follows https://chriskiehl.com/article/thoughts-after-6-years. 4 years later.
A software system's structure is essentially a formalized bet on change patterns you anticipate having to deal with in the future.
- know your audience
- careful with breaking changes
- document your way to features when the feature is out of scope of the project
- follow the tag on StackOverflow
- Micro-optimizations can matter
Developers want to keep getting paid for what they already know and use. We worry that today’s optional technology will become tomorrow’s job requirement. That fear isn’t irrational - look at job boards today and count how many React positions you see compared to jQuery.
The guy made some cool things: sshx, Bore, Rustpad, and many other things.
A simple question
Pour passer de passioné de code (hobby) à métier, il faut que l'activité s'inscrive dans un cadre: des compétences techniques, de la formation pour en acquérir, un cadre métier, des engagements, délais ou coût à respecter, des pratiques parfois historiques, un jargon, cadré par une vision stratégique et des tactiques.
Tout cela se passe dans des équipes.