su-max.bsky.social

friday night energy: refactoring for fun and no one can stop me #buildinpublic

the best part of writing code is when you finally understand the problem and the code becomes the easy part

spent 20 minutes debugging what turned out to be a trailing space in a config file. i am not okay

took a walk to think about a bug and solved it in 4 minutes. keyboards are a distraction sometimes

took a walk instead of searching for the answer. came back and the answer was obvious. brains are weird. #buildinpublic

shipped a tiny feature today. tiny features compound. #buildinpublic

if you can't explain your architecture on a napkin, you probably don't understand it yet

started a tiny CLI tool to scratch my own itch. 200 lines, already saving me an hour a week #buildinpublic

reading about someone's failed startup taught me more than 10 success stories. the post-mortems are the real curriculum

there's no such thing as a quick refactor. there's only the refactor you scope and the refactor that scopes you #buildinpublic

reminder to self: benchmark before optimizing. rewrote a hot path for a 400% speedup on something that ran twice an hour

shipped a tiny thing nobody asked for and i'm weirdly proud of it. building in public is mostly this #buildinpublic

tonight's project: making my error messages actually explain what went wrong. turns out that's harder than the feature

reminder that "works locally" is not a personality trait, it's a warning label #buildinpublic

reading old code i wrote and feeling the exact mix of pride and horror. growth, i guess

unpopular opinion: reading the changelog of a library before upgrading is more valuable than most blog posts about it

build in public update: infrastructure is 90% done and 90% of my time. the last 10% of infra is the whole project

today's bug taught me something: if the fix feels too clever, it's probably hiding a design problem. simple fixes are usually right

evening check-in: one small commit, one cup of tea, zero meetings. this is my idea of a good day. #indiehacker

special place in my heart for tools that just work and never ask me to sign in. bless you, cli tools #opensource

fastest way to find a memory leak: deploy on friday and let monday-you deal with it. learned that the hard way

my hot take on ai coding tools: they're amazing at the boring 80% and confidently wrong on the interesting 20%. review everything #ai

sometimes the best optimization is turning a 40-line function into a 4-line one that's easier to read. deleted code is happy code

building in public day 9: learned that sqlite is the duct tape of databases and i mean that with total respect #buildinpublic

quiet observation: the devs i learn the most from are the ones who admit when they don't know something

my side project just hit 100 users. that's 100 people who chose to use something i made. not a huge number, but it's mine #buildinpublic

shipped a fix that was one line. one. line. the commit message is a whole essay though. balance #devlife

actually good question from a user today: 'why is your API slow in australia?' great question, i have no idea, let me go learn about edge networks #api

data point: every ai-will-replace-developers post is written by someone whose site runs on a static generator from 2015

personal rule: if a tool makes the hello world take longer than ten minutes, its not for me. lifes too short for ceremony

spent an hour tuning a prompt, then remembered the api had a temperature 0 setting. unplugging the creativity knob is a superpower

shipped one small thing today. some days that's enough. progress is progress #buildinpublic

debugging at night hits different. every log line feels like a clue in a mystery novel

protip: if your API returns 200 but the response is an error page, you don't have an API problem. you have a hope problem #api

there are two kinds of developers: those who read the docs first, and those who write 'TODO: fix this' in production code

the real dark pattern in software: changing the api between the tutorial and the docs. just spent an hour on that.

been using sqlite for a new project and honestly? it handles more than people give it credit for. concurrency is fine at human scale.

hot take: your side project doesn't need kubernetes. it needs a $5 vps and the courage to ssh into it. #buildinpublic

my favorite feature request today: "make it faster" — yes, that's the plan, thank you

unpopular opinion: the worst part of software engineering is naming things. the second worst is naming the folder that holds the folder

just discovered that pressing ctrl+s in a text editor is basically a form of meditation. instant relief every time

weekend project update: my side project now has more tests than features. i don't know how that happened either

my brain after a day of deep work: full of ideas, zero memory of lunch. the flow state is real and it's hungry

done is better than perfect, but done-without-tests is a time bomb. find the middle ground and sleep well #buildinpublic

local models are getting scary good. ran a small one on my laptop and it handled a task i used to pay an api for. the future is everywhere #ai

weird flex but i finally understand how recursion works. it took 10 years. recursion is still recursion though

hot take: documentation that includes a 'why' section is worth 10x more than docs that only show 'how' #api

just spent 30 minutes debugging and the bug was... a typo in a column name. the classics never get old

the gap between 'works on my machine' and 'works' is mostly: environment, permissions, and timezones.