I am a data analyst who got tired of reporting on problems and decided to learn how to build the solutions. My name is Kristian. I pivoted from Business Analyst to Developer without a bootcamp or university degree. My background was in data and reporting which was stable but limited. I realised that analysing value is not the same as creating it, so I taught myself to build. The transition was practical: - Automation (Python): I started by writing scripts to automate my own data entry. They were messy but saved time. - Internal tools (JS/CSS): I moved on to building dashboards for my team. This taught me how to structure data for users, not just reports. - Public products (React/Node): I eventually shipped tools to the open market. Reality is customers don’t audit your codebase. They audit your solution. If your product solves a painful problem, nobody cares whether you learned from documentation or a degree. - I’ve failed technical interviews. - I’ve written inefficient code. But I’ve shipped products that work. If you’re a non-technical operator building your way into a technical role: share your path! Let’s validate that the self-taught journey is a legitimate career strategy.

the feed is 90% recycled tweets and 10% actual unique thoughts. the algorithm is optimizing for virality but killing originality. please tweet something real today.

Claude is for vibe coding. Codex is for shipping. Made the switch this week: - Generated working auth in one prompt (Claude wanted to discuss the philosophy of auth first) - 3x rate limits = 3x faster launches - Interface that looks like 2026 not 1996

month 1: this is amazing i'm gonna be a developer month 3: why is everything broken month 6: built three things, finished zero month 8: still building, still haven't shipped the tutorial phase ends when you get comfortable being bad in public. nobody's coming to give you permission. you just start, stay consistent, and ship the messy version eventually.

Imagine your Net Worth increases 14% Congrats! maybe you got a promotion, or made a lucky investment For Elon Musk, that 14% percent is $107,000,000,000 9 ZEROS Jesus Christ.

Are you optimizing for rest today so you don’t burn out? Or are you working while the rest of the timeline is offline? There’s no wrong answer, but you can’t do both. What’s the move today?

I started posting/replying on X less than a month ago Yesterday, I got almost 300,000 impressions on one reply. ~7000 likes Fun fact: it converted into -> O new followers Why? Probably because it was completely out of niche You speak your thoughts, it resonates, and it bounces around the timeline Lesson: It doesn't always translate to direct growth, and that's okay!! Some are just for the love of the game😎

my first month posting on X just crossed 200k impressions on the day😅 it really just sky rockets when you least expect it. quality > quantity

Crossed 100k impressions in one day! No viral threads. No engagement pods. Just consistent, quality replies. The secret wasn't volume, I averaged 30 replies since I started. The strategy is boring: - Find good conversations. - Add actual value. -Saying quick 'Hello' once in a while doesn't hurt:) - Repeat until the algorithm notices. And it will. It's a slow grind to build momentum, but once the algorithm tags you as 'high signal,' you will be rewarded!

this is exactly why high performers leave the 'sharon tax' on your mental health is more expensive than the salary

I am a data analyst who got tired of reporting on problems and decided to learn how to build the solutions. My name is Kristian. I pivoted from Business Analyst to Developer without a bootcamp or university degree. My background was in data and reporting which was stable but limited. I realised that analysing value is not the same as creating it, so I taught myself to build. The transition was practical: - Automation (Python): I started by writing scripts to automate my own data entry. They were messy but saved time. - Internal tools (JS/CSS): I moved on to building dashboards for my team. This taught me how to structure data for users, not just reports. - Public products (React/Node): I eventually shipped tools to the open market. Reality is customers don’t audit your codebase. They audit your solution. If your product solves a painful problem, nobody cares whether you learned from documentation or a degree. - I’ve failed technical interviews. - I’ve written inefficient code. But I’ve shipped products that work. If you’re a non-technical operator building your way into a technical role: share your path! Let’s validate that the self-taught journey is a legitimate career strategy.

How to spot an AI reply: - Restates your tweet but longer. - Uses 3 different analogies in one sentence. - Jokes like a high schooler left in 10th grade for 3 years in a row. - You read the reply, and you just feel NO SOUL there. Share your favourite ones.

reached 200 followers! 0 to 100 was a grind 100 to 200 felt like it happened overnight. huge thanks to everyone who hit follow back to fixing (breaking) things

day 1: shipping to prod day 7: writing code day 14: validating the project day 21: asking, ‘wait, who is this for?’ am i doing this correctly? please advise

the price of freedom is a few years of unbalanced obsession in your 20s btw that’s it