Today I resolved a bug lurking deep within the workings of my Chlorine Boards framework and I have twitter to thank. When I made a blogpost about how drug use is not abuse a person following me on twitter immediatelly picked up on the post, gave it a read, retweeted and wanted to leave a comment. But couldn't. Immediately @OneLuvGurl tweeted to me about how she can't comment.
We tweeted back and forth for about an hour about the issue when I finally just asked her to send me the comment and I'll see what I can do. It turned out that it was indeed, as I feared, the comment's fault. So I started poking around until I found what was wrong. The comment was too long ... but how can this be? The darn thing isn't very long at all.
Two hours later I finally found out what the issue was and was able to resolve it. It would appear that three, or was it four, years ago I've made a terrible design flaw - I decided to use GET requests for ajax instead of POST requests. Since GET requests have a limited length this was naturally a disaster waiting to happen and I'm surprised the issue could go so long without being noticed, but I'm glad it's resolved and I've already updated all the websites running on Chlorine Boards with the surprisingly simple fix.
This event just goes to show how much more than just status updates Twitter has become and just how awful bugs can be.
Continue reading about Twitter solves massive bug
Semantically similar articles hand-picked by GPT-4
- Online buzz is quite cool
- Getting off twitter, an experiment
- Being hacked killed a 6k traffic spike on my blog yesterday
- I kicked myself in the balls
- Unit testing is anti-productive
Learned something new?
Read more Software Engineering Lessons from Production
I write articles with real insight into the career and skills of a modern software engineer. "Raw and honest from the heart!" as one reader described them. Fueled by lessons learned over 20 years of building production code for side-projects, small businesses, and hyper growth startups. Both successful and not.
Subscribe below 👇
Software Engineering Lessons from Production
Join Swizec's Newsletter and get insightful emails 💌 on mindsets, tactics, and technical skills for your career. Real lessons from building production software. No bullshit.
"Man, love your simple writing! Yours is the only newsletter I open and only blog that I give a fuck to read & scroll till the end. And wow always take away lessons with me. Inspiring! And very relatable. 👌"
Have a burning question that you think I can answer? Hit me up on twitter and I'll do my best.
Who am I and who do I help? I'm Swizec Teller and I turn coders into engineers with "Raw and honest from the heart!" writing. No bullshit. Real insights into the career and skills of a modern software engineer.
Want to become a true senior engineer? Take ownership, have autonomy, and be a force multiplier on your team. The Senior Engineer Mindset ebook can help 👉 swizec.com/senior-mindset. These are the shifts in mindset that unlocked my career.
Curious about Serverless and the modern backend? Check out Serverless Handbook, for frontend engineers 👉 ServerlessHandbook.dev
Want to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz React components your whole team can understand with React for Data Visualization
Want to get my best emails on JavaScript, React, Serverless, Fullstack Web, or Indie Hacking? Check out swizec.com/collections
Did someone amazing share this letter with you? Wonderful! You can sign up for my weekly letters for software engineers on their path to greatness, here: swizec.com/blog
Want to brush up on your modern JavaScript syntax? Check out my interactive cheatsheet: es6cheatsheet.com
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️