The most interesting Articles
Writing code is easy. Once you have a solution in mind, and have mastered the syntax of your favorite programming language, writing code is easy. Having an LLM write entire functions for you? Even easier. But the hard part isn’t the writing. It’s the reading. It’s the time it takes to load the mental model of the system into your head. That’s where all the cost really is.
The 2010s was the Wild West of the mobile world. "Mobile-first" was the buzzword, much like "AI-first" is today. Every company, from the biggest social media giants to your local pizza parlor, seemed to be pestering you to download their app. There was a genuine hype train, and everyone was on board. The apps, frankly, were always mediocre, and a far cry from the full functionality of their website counterparts. But the message was clear. If you weren't on mobile, you were falling behind.
The majority of the traffic on the web is from bots. For the most part, these bots are used to discover new content. These are RSS Feed readers, search engines crawling your content, or nowadays AI bots crawling content to power LLMs. But then there are the malicious bots. These are from spammers, content scrapers or hackers. At my old employer, a bot discovered a wordpress vulnerability and inserted a malicious script into our server. It then turned the machine into a botnet used for DDOS. One of my first websites was yanked off of Google search entirely due to bots generating spam. At some point, I had to find a way to protect myself from these bots. That's when I started using zip bombs.
I once had a job interview for a backend position. Their stack was Node.js, MySQL, nothing exotic. The interviewer asked: "If you have an array containing a million entries, how would you sort the data by name?" My immediate thought was: If you have a JavaScript array with a million entries, you're certainly doing something wrong. The interviewer continued: "There are multiple fields that you should be able to sort by." This felt like a trick question. Surely the right answer was to explain why you shouldn't be sorting millions of records in JavaScript. Pagination, database indexing, server-side filtering. So I said exactly that.
Back in the 2010s, we had our own hype cycle. It was silly because it hijacked a term we were all already familiar with, then rebranded it as if it were new technology. Those two terms were "Server" and "Cloud." Yes, children, there was a time when we didn't say "cloud computers". We just called them servers.
"I'm sorry... did you want to go to the bathroom too?" "Oh no, I was just following you." "Oh, well I'd rather you not follow me." "Wait, it's not like you have something to hide, right? Make sure you don't leave the door closed."
A few years back, I was running a CI/CD pipeline from a codebase that just kept failing. It pulled the code successfully, it passed the test, the docker image was built, but then it would fail. Each run took around 15 minutes to fail, meaning whatever change I made had to take at least 15 minutes before I knew if it was successful or not. Of course, it failed multiple times before I figured out a solution. When I was done, I wasn't frustrated with the small mistake I had made, I was frustrated by the time it took to get any sort of feedback.
I still remember my first real job hunt. It was a different world. I had a system: a well organized spreadsheet tracking every company, contact name, and the date I emailed or mailed my physical resume (yes, mailed). I scoured Craigslist posts, navigated weird interview assignments, and even once stumbled into an interview that turned out to be a front for selling knives door-to-door instead of the web programming job it advertised.
At the end of every month, I used to religiously check the total internet bandwidth we'd consumed at home. A decade ago, my ISP would throttle our connection if we crossed some loosely defined threshold, so monitoring usage felt essential. Those days are long gone. With gigabit internet widely available and everyone streaming Netflix in different rooms simultaneously, I've spared myself the monthly ritual of bandwidth anxiety.
The most read articles
a book by Ibrahim Diallo
After the explosive reception of my story, The Machine Fired Me, I set out to write a book to tell the before and after.
I started as a minimum wage laborer in Los Angeles and I set out to reach the top of the echelon in Silicon Valley. Every time I made a step forward, I was greeted with the harsh changing reality of the modern work space.
Getting fired is no longer reserved to those who mess up. Instead, it's a popular company strategy to decrease expenses and increase productivity.