TheUnsureDev

85 posts

TheUnsureDev banner
TheUnsureDev

TheUnsureDev

@theunsuredev

Code, Insight, Inspiration. https://t.co/f14YICqs9J

Auckland, New Zealand Katılım Haziran 2025
143 Takip Edilen29 Takipçiler
muskan sharma
muskan sharma@muskaan___07·
Which programming language made you fall in love with coding?
muskan sharma tweet media
English
25
3
61
1.1K
TheUnsureDev
TheUnsureDev@theunsuredev·
@embersunn I wrote an entire Masters thesis about Java! Narrator: "The Masters thesis was about Java applets..."
English
0
0
0
53
embersunn
embersunn@embersunn·
Java didn’t survive 30 years because it’s exciting It survived because predictability scales better than hype Doesn’t matter how many times vibe coders say “Java is outdated” while their global banking system is literally running on it
English
37
6
136
6.4K
TheUnsureDev
TheUnsureDev@theunsuredev·
@Bhoomikagj Different interpretations usually point to something that either isn't specified or isn't specified well enough. So the general solution is to kill the ambiguity by making the definition sufficiently specific. This would typically be done by a human, not the AI!
English
1
0
0
6
Bhoomika -
Bhoomika -@Bhoomikagj·
@theunsuredev This is solving a real gap — dev and PM alignment breaks down so fast, especially when AI agents are in the loop too. How are you handling conflicts when all three have different interpretations of the same definition?
English
1
0
0
10
Bhoomika -
Bhoomika -@Bhoomikagj·
Heyy Builders! 👋 Happy Wednesday ! What are you building (or planning to build) !? Drop your category + a quick update • Mobile Apps • AI/ML • Data Science • Open Source • Indie/SaaS • Other cool stuff! Let’s #connect, share wins, and support each other! #BuildInPublic #WebDev #AI #OpenSource
English
43
0
25
826
LottBerson
LottBerson@Berson_lott·
Yesterday our project got viewed by 2.5k people.🥳 Still here today, Looking to #connect with more builders in: 🤖 AI tools 💻 SaaS 🦾 Automation 🧑🏻‍💻 Tech ⚙️ Devs Drop what you've working on!👇🏻
LottBerson tweet media
English
49
0
43
1.1K
Germán Merlo 💻 🇦🇷
Building a SaaS solo in 2026? Drop your link. Genuinely curious what people are working on right now.
English
49
0
35
2.2K
Davic | UI/UX Designer
Davic | UI/UX Designer@victory_payne1·
Hey @X 200+ friends in and I'm still looking to #connect with more people 😼 •UI/UX design • Web Development • Mobile Apps • AI & Machine Learning • Data Science / Analytics • Graphics design •Startups Drop in your projects and let's support each other.
English
25
0
20
643
TheUnsureDev
TheUnsureDev@theunsuredev·
In my work, I classify mini-prompts into two broad categories: (1) tools - that do "one thing well" - access Jira, access GitHub, etc. (2) workflows - that encode my desired workflows - and call tools as needed/specified e.g. "implement-feature" - update product definition, acceptance criteria, write prod and test code, review, notify But: (a) coding agents are for some reason moving away from "commands" and more towards "skills", and (b) agents are *not* looking hierarchically at a skills directory. Leaving the unsavoury option of mashing all "tools" and "workflow" mini-prompts into a single non-sub-foldered skills directory. I do it. But yuck.
English
0
0
0
319
Matt Pocock
Matt Pocock@mattpocockuk·
I've been feeling the itch to divide my skills repo into two kinds of skills: - Model-invocable skills (skills) - User-invocable skills (commands) I.e. you'd be able to run /improve-codebase-architecture (a command), which would use /deep-modules (a skill) You'd run /grill-with-docs, which relies on /domain-modeling That way, skills become more composable. You can ask "give me a report on the /deep-modules in this repo", or "help me with /domain-modelling a new concept"
English
52
8
402
21.7K
Paul the Dev
Paul the Dev@Pablo0097195867·
Hey @X algorithm 👋 Looking to #connect with more builders, hackers, and creators on here. If you're into: • Full-stack dev (Frontend/Backend) • Building SaaS & Micro-SaaS • Solopreneurship & Freelancing • Vibe coding & Startup life • Building in public Drop a reply with what you’re currently working on, and let’s connect
English
37
0
26
832
Eva Rammar
Eva Rammar@rammarpro·
looking to connect with founders, engineers, and ambitious people shipping cool things : SaaS, AI agents, growth, web apps. reply with what you're building. let's grow together.
English
22
0
15
601
Leah
Leah@leahlibest·
Builders & marketers on X What are you working on right now? → SaaS → AI tool → Growth experiment → Content engine → Side project with a landing page Drop your URL below 👇 Let's support each other
English
45
0
25
1K
Sarthak Shaurya
Sarthak Shaurya@alwaysSarthak·
The week ends today and I am marketing my app But as we all know networking is the most important If you are into: Vibe coding SaaS SEO UGC content Reddit marketing Indie hacking Drop the projects you are working on👇
English
14
0
7
414
Tom Otto
Tom Otto@launch_llama·
𝗦𝗵𝗼𝘄 𝘂𝘀 𝘄𝗵𝗮𝘁 𝘆𝗼𝘂'𝗿𝗲 𝗯𝘂𝗶𝗹𝗱𝗶𝗻𝗴.
 Drop your product in the comments.
 If we love it, 𝗪𝗲'𝗹𝗹 𝗹𝗶𝘀𝘁 𝗶𝘁 𝗼𝗻 𝗟𝗮𝘂𝗻𝗰𝗵 𝗟𝗹𝗮𝗺𝗮 𝗗𝗶𝗿𝗲𝗰𝘁𝗼𝗿𝗶𝗲𝘀. 🦙✨
English
178
2
48
5.8K
Germán Merlo 💻 🇦🇷
If you're building with AI tools and actually shipping—not just talking about shipping—I want to connect. Drop your product link below. No pitching required.
English
243
6
143
13.7K
TheUnsureDev
TheUnsureDev@theunsuredev·
Thanks Sanskriti! I started building this a year ago, when LLM agents struggled for correctness. One year on, LLMs/agents are now a lot better, but using a product definition as the core of development has nevertheless been really successful for team visibility as well as keeping agent implementations on track with production and test code. This is a little different to the current spec-driven development drive in that it focuses on permanent product definition - which I think is a relatively unexplored gap in agentic development at the moment.
English
0
0
0
9
Sanskriti Bokde
Sanskriti Bokde@sans_builds·
@theunsuredev This is cool! I am curious what drives your passion to build this tool? Did you see any specific gap in the market?
English
1
0
0
25
Sanskriti Bokde
Sanskriti Bokde@sans_builds·
My feed is dead! Full of noise. No real people. No real conversations. I want to change that today. If you're out here building : → SaaS / AI tools → Vibe coding → Shipping in public → Figuring it out as you go Say Hi Drop what you're working on below.
English
220
3
197
8.8K
Silas Reinagel ⚛️
Silas Reinagel ⚛️@SilasReinagel·
@theunsuredev @systemdesignone nice! this is right concept! i think for human users though, the primary surface area needs to be really terse and/or visual most users are getting burnt out on walls of text
English
1
0
0
23
Neo Kim
Neo Kim@systemdesignone·
A pattern I've noticed in people using AI to code: They're always shipping... They never stop generating... They've got Claude to code, CodeRabbit to review, and a prompt library larger than the codebase... But if you ask them what they understand about the code they merged last week, their minds go blank... Productivity isn't the same as mastery. Focus on the fundamentals. (This is not just an opinion, but a fact.)
Lee Robinson@leerob

You might believe you should spend less time thinking about code because of AI. I strongly disagree! We’re watching this play out live where tons of AI generated code becomes a liability. At the end of the day, an engineer needs to be responsible / on call for code that gets shipped to production. If you don’t understand the system you’re trying to debug, you’re probably going to have a bad time. Yes, AI can help with all of this, if you set up the proper systems. You can have agents triage prod logs, look at errors, etc. You can speed up parts of the investigation, but an engineer needs to make the call. There might be serious customer or financial implications from that change. I expect the trend continue for trimming dependencies, vendoring code so you can modify it directly, preferring simpler systems with fewer abstractions, and spending waaaay more time thinking about system design and code maintenance. I’ve said this before, but it’s a great time to get familiar with CS fundamentals and some of the history behind what great software looks like. Many parts will be different in the coming years as AI progresses, but also a lot more than people realize will stay the same.

English
21
9
264
36.5K