Sk @codelit09

10-15 years into your career you shouldn't need to cold interview for jobs if you need to you fucked up - it's not too late to fix it but you did fuck up fix it

# on technical accessibility One interesting observation I think back to often: - when I first published the micrograd repo, it got some traction on GitHub but then somewhat stagnated and it didn't seem that people cared much. - then I made the video building it from scratch, and the repo immediately went through hockey stick growth and became a verty often cited reference for people learning backpropagation. This was interesting because the micrograd code itself didn't change at all and it was up on GitHub for many months before, stagnating. The code made sense to me (because I wrote it), it was only ~200 lines of code, it was extensively commented in the .py files and in the Readme, so I thought surely it was clear and/or self-explanatory. I was very happy with myself about how minimal the code was for explaining backprop - it strips away a ton of complexity and just gets to the very heart of an autograd engine on one page of code. But others didn't seem to think so, so I just kind of brushed it off and moved on. Except it turned out that what stood in its way was "just" a matter of accessibility. When I made the video that built it and walked through it, it suddenly almost 100X'd the overall interest and engagement with that exact same piece of code. Not only from beginners in the field who needed the full intro and explanation, but even from more technical/expert friends, who I think could have understood it if they looked at it long enough, but were deterred by a barrier to entry. I think as technical people we have a strong bias to put up code or papers or the final thing and feel like things are mostly self-explanatory. It's there, and also it's commented, there is a Readme, so all is well, and if people don't engage then it's just because the thing is not good enough. But the reality is that there is still a large barrier to engage with your thing (even for other experts who might not feel like spending time/effort!), and you might be leaving somewhere 10-100X of the potential of that exact same piece of work on the table just because you haven't made it sufficiently accessible. TLDR: Step 1 build the thing. Step 2 build the ramp. 📈 Some voice in your head will tell you that this is not necessary, but it is wrong.

thought about this more and it's actually just the old devtools problem good devtools are built by top 1% of programmers for everyone else most devtools companies treat it like a normal product that can be built by anyone

dax @thdxr

a year ago

the majority of AI tooling for programmers doesn't feel like it was built by programmers it feels like people on the outside trying to make things for programmers there's just a smell you can't shake

24 15 443 67K 46

unfortunately the lead dev of opencode is pursuing selling it to a company we couldn't work out a way to keep it independent so adam and i are working on our own version more info in the thread

I am getting SO tired of these posts from influencers: “We literally cloned an N billion-dollar company in 20 minutes with {vibe coding tool}. This changes the game forever.” No, you didn’t “clone” a billion-dollar business. You created a landing page similar to it. That’s all.

you're not going to launch and have instant success you will need to market, acquire user by user, drag the world to your product and there will be plateaus now look again at what you're building and see if you're really willing to do all that for this idea

I vibe coded around 5 hours today with Cursor on a very simple and stupid side project, and I can safely say any dev who's afraid about AI taking their job any time soon has major skill issue and shouldn't have a job in the first place.

Unpopular opinion: you’ll learn more from building a toy operating system or a text editor than from 10 leetcode challenges. break things, debug, repeat. that’s how you actually get good.

Big news: Windows Subsystem for Linux is now Open Source! 🎉 Download WSL, build from source, contribute fixes & features, and join its active development. Learn more: msft.it/6018SjYoE

George Hotz explains how to get hired @__tinygrad__

😭

ThePrimeagen @ThePrimeagen

a year ago

LLM proompt maxxing is astrology for software devs

62 128 2K 170K 110

I built a game engine in C++ - Calls malloc once - Not a single destructor - No RAII - No smart pointers You don't need that stuff if you understand a bit about how memory works

CI/CD feels complex until you treat each step like a function. Learn how GitHub Actions works in 5 minutes. { author: @codelit09 } #DEVCommunity #JavaScript dev.to/sfundomhlungu/…

A step-by-step guide to printing Hello World in x86 assembly on Linux. Discover low-level coding without the fluff. { author: @codelit09 } #DEVCommunity dev.to/sfundomhlungu/…

Step through a detailed guide on compiling a Hello World in x86 assembly on Linux. Learn essential low-level steps. { author: @codelit09 } #DEVCommunity dev.to/sfundomhlungu/…

Anything else is mental illness.

Vic 📠 @VicVijayakumar

2 years ago

There are 2 types of engineers at big tech cos: - those who write very detailed software design docs first - those who build working proofs of concepts first

112 101 2K 1.0M 455

This is a good point and one of the many reasons we promote low-level knowledge of video/audio processing and programming. LLMs can easily use FFmpeg by writing commands, but they don't understand FFmpeg.

Agustin Gomes @agustingomes

2 years ago

@FFmpeg Specialists knowledge will be valuable in the future, will all the noise on the internet nowadays being consumed by LLM's.

1 0 28 18K 2

🎉 I did it again! A while back, I ported charmcli Lipgloss to WASM, and the response was amazing. So, I decided to tackle another favorite: Huh Forms! shoutout to the Charm team for their awesome work. Check out the forms 👇 🔗 dev.to/sfundomhlungu/…

Every “Programming is dead” take I’ve seen so far is coming from people who have no clue about programming.