Marko Kaznovac

Dijkstra on why he believed programmers should stop using the term "bug"

This is Algebrica. A mathematical knowledge base I’ve been building for 2.5 years. 215+ entries, carefully written and structured. 400k+ views over this time. Not much in absolute terms, but meaningful to me. No ads. No courses to sell. No gamification. No distractions. Just essential pages, aiming to explain mathematics as clearly as possible, for a university-level audience. Built simply for the pleasure of sharing knowledge. Content licensed under Creative Commons (BY-NC). Best experienced on desktop. If it helps even a few people understand something better, it’s worth it.

In 20 years, vibe coders will look at the Linux kernel repo the way we look at the pyramids. In awe, unable to imagine how they managed to drag all those giant stones and pile them up in the middle of the desert.

everyone's talking about their teams like they were at the peak of efficiency and bottlenecked by ability to produce code here's what things actually look like - your org rarely has good ideas. ideas being expensive to implement was actually helping - majority of workers have no reason to be super motivated, they want to do their 9-5 and get back to their life - they're not using AI to be 10x more effective they're using it to churn out their tasks with less energy spend - the 2 people on your team that actually tried are now flattened by the slop code everyone is producing, they will quit soon - even when you produce work faster you're still bottlenecked by bureaucracy and the dozen other realities of shipping something real - your CFO is like what do you mean each engineer now costs $2000 extra per month in LLM bills

What if GitHub made you take a quiz about your PR before requesting reviews, to make sure you know what's in it? And if you don't...

Open-source Free Domain For Everyone.

Na osnovu člana 46 u vezi sa članom 18 Ustava Republike Srbije (čiji sam državljanin od rođenja, što je jedino drž. koje sam ikada imao, jer nisam nikada ni pokušao da imam neko drugo drž.) da vam napišem svoje mišljenje: A) SRBIJA TREBA DA BUDE ČLANICA EU. Da bi to postigla, Srbija treba da dostigne određene propisane standarde u raznim oblastima (vladavina prava, ljudska prava, ekonomija, ekologija i dr.). B) STANDARDE ZA A) SRBIJA TREBA DA DOSTIGNE ZBOG SEBE SAME, SVOJIH GRAĐANA RADI, A NE RADI FORMALIZOVANJA A). Dakle, zbog svojih građana i zbog svog razvoja Srbiji je potrebno da postane “normalna” zemlja. Sa aspekta građana, formalizacija A) postaje tada realno nebitna, i ostaje kao političko, a ne kao civilizacijsko pitanje ili pitanje opstanka kao što je sada. C) REALNO NE POSTOJE PREPREKE DA B) SRBIJA OSTVARI SAMA. Srbiji ne treba nikakva pomoć “sa strane” da građani Srbije počnu da poštuju propise sopstvene zemlje. Čak je bolje da nam na tom putu NIKO ne pomaže. Nismo nesposobni. Svako ko tvrdi da ne možemo sami, nipodaštava građane Srbije. Pod “sa strane” mislim na sve koji nisu Srbija: SAD, EU, Rusija, Kina, bukvalno sve strance i strane faktore. D) TRENUTNI REŽIM MRDNUO NIJE KA A) I B). Svako ko podržava trenutni režim je protiv A) i B). E) TRENUTNO, EU PODRŽAVA TRENUTNI REŽIM. Namerno pišem “trenutno” jer se stanje možda promeni. EU je: - priznala sve rezultate svih pokradenih izbora u Srbiji, iako je i sama konstatovala krađu; - finansirala i finansira režim koji konstantno krade izbore; - na listu svojih strateških prioriteta stavila uništavanje prirode Srbije; - odustala od primene sopstvenih vrednosti kada je Srbija u pitanju. ZAKLJUČAK (ako grešim, ispravite me): 1) Ako EU (koliko vidim, na sve načine) podržava režim koji Srbiju već 13 godina drži dalje od EU, to onda znači da EU ne želi Srbiju u svom članstvu. 2) Bez obzira na 1), Srbija mora SAMA SEBE da dovede u red. Paradoksalno, Srbija će samu sebe dovesti u red primenom načela i vrednosti koje (formalno) propagira EU. Bez obzira na to što EU ta načela ne primenjuje, moramo mi. To je jedini put. 3) Građani Srbije JESU sposobni da 2). Uprkos svim pritiscima, kako od samog režima, tako i od ovih “sa strane”. Samo je pitanje želje i žrtve. Žao mi je što građani moraju da se žrtvuju da bi živeli u normalnoj državi. Tačnije da bi unormalili sopstvenu državu. Do sada to nije urađeno, ali šansa postoji. 4) Možda za mog života, a možda i kasnije, nebitno, u Srbiji će jednog dana osvanuti ŠESTI OKTOBAR. 5) Svi koji privrženost EU vrednostima sagledavaju brojanjem EU zastava na protestima protiv režima su samo za šminku, za kozmetičke a ne za suštinske promene u Srbiji. Privrženost EU vrednostima se gleda kroz borbu za njih, a ne kroz mahanje EU zastavama i stavljanjem EU zastavica na profile. Eto, toliko od mene ovim povodom.

I don't want to learn the new React Framework of the Week. I just want to drag UI widgets onto a canvas and hook up their event handlers to code I write. Like VB in 1995. Except the output should work on Windows, Mac, and Linux. I'd buy that.

LEGO doors [📹 Brick Experiment Channel]

Hiring engineers after a no-code MVP is like asking an architect to fix your LEGO tower. It might look like a product. It might work just enough to demo. But under the hood? It’s fragile, rigid, and impossible to scale. Here’s what most first-time founders don’t realize: Engineers don’t want to debug a maze of Airtable formulas, Zapier triggers, and Bubble workflows. They want to build, not reverse-engineer a brittle system they didn’t choose. And when you force them to work around it? Your roadmap suffers. Your delivery slows down. And your best hires walk away. The truth is, most MVPs built with no-code should be treated like what they are: Prototypes. Useful for validation. Great for speed. But not something you build your company on. The good news? You don’t have to throw everything away. You just need a clear plan for version 1. Something maintainable. Scalable. Built with the future in mind. That’s where a fractional CTO comes in. We help you transition from experiments to systems. From validation to velocity.

A computer scientist’s perspective on vibe coding:

I implemented an ssd, hdd, and tape device. In javascript. For a blog.

I’m starting a new business. After you fire your developers and start vibe coding everything, we’ll come in and fix all the bugs and security issues with your AI-generated code. We’ll take what you have and make it work. The service will start at $1,000/hour.

What does the CPU internally do? Check out the animation... The dance goes like - 1. Fetch 2. Decode 3. Execute 4. Memory Access 5. Write Back See it in action here: eseo-tech.github.io/emulsiV/

Found Beej's Guide to C Programming! For those who don't know, Beej is a cracked old timer who's done a ton of tech guides over the years. This one alone can probably bring you to expert-level in C. Check it out!

99% of YouTube videos lately are clickbait and stretch out ~1 paragraph of Wikipedia into 30+ minutes of content. Many videos are just questions with simple answers. So I built tldw.tube: put in the URL and save your time!

Through the Ages: Apple CPU Architecture , by @jacobs_handle blog.jacobstechtavern.com/p/through-the-…

Hi 👋 I'm Sam, I create interactive visualisations about programming. My posts from 2024: - samwho.dev/bloom-filters - encore.dev/blog/queueing - samwho.dev/turing-machines I also appeared on 2 podcasts : - hanselminutes.com/953/computer-s… - youtube.com/watch?v=ur9clT…

in case you didn't know, this is how you're actually supposed to do software versioning