Weslley ➜ broto.work (@Wezo) header
Weslley ➜ broto.work (@Wezo) profile picture

Technical builder Building SaaS & AI in public Shipping systems, not ideas

Joined May 2007
Photo by Weslley ➜ broto.work (@Wezo)Photo by Weslley ➜ broto.work (@Wezo)Photo by Weslley ➜ broto.work (@Wezo)Photo by Weslley ➜ broto.work (@Wezo)Photo by Weslley ➜ broto.work (@Wezo)Photo by Weslley ➜ broto.work (@Wezo)Photo by Weslley ➜ broto.work (@Wezo)Photo by Weslley ➜ broto.work (@Wezo)Photo by Weslley ➜ broto.work (@Wezo)Photo by Weslley ➜ broto.work (@Wezo)
Working on a side project at this scale is uncomfortable. Slow progress. Limited time. Constant trade-offs. broto.work is far from ready. But seeing it already move between list, kanban and calendar hits different. Because it stops being an idea. And starts becoming a tool.
1
5
147
One of the best decisions I made in my MVP I persisted everything in JSON instead of using a database. It wasn’t a mock. The CRUD was real. All entities were related. But I didn’t lock myself into schemas.
1
2
164
Why? Because during MVP, your model changes every week. Adding a new property shouldn’t require: » Schema migrations » ORM updates » Refactoring half the stack My local API manipulated JSON arrays directly. When you use AI/vibe coding in a structured way - clear prompts + full context - you can evolve your model safely without fighting your infrastructure. MVP is about learning velocity. You can normalize later. #BuildingInPublic
3
114
I adjusted the Sprint management drawer. Reason: teams were taking longer than they should to understand sprint state.
1
1
3
213
What was happening: » Active sprint wasn’t visually obvious » All cards had the same weight » Actions had too much prominence » Too much gray, low hierarchy Result: every time someone opened it, they had to re-parse the screen. That’s wasted seconds. And in sprint planning, seconds multiply. What I changed: » Clear visual hierarchy » Stronger distinction for the active sprint » Reduced action noise » Better spacing and grouping No new feature. Just less friction. #buildinpublic
1
139
I’m building SaaS & AI side projects in public. Sharing: – Architecture decisions – Revenue experiments – Automation systems – What works (and what doesn’t) Let’s build.
1
1
2
234
| ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄ ̄| |Don't Push To Production On Friday| |_________________| \ (•◡•) / \ / —— | | |_ |_
175
560
101
4,034
228,959
Lol
Devo ter fumado um sem saber #bolhadev Não consigo parar de rir
3
1,718
Weslley ➜ broto.work retweeted
Não fique triste jovem da #bolhadev mas essa é uma verdade! Resolva problemas! 💰💰💰
2
6
2,037
Weslley ➜ broto.work retweeted
What kind of a hooligan would write this 😢🥹
363
555
151
5,506
281,356
UI/UX Design Trends For 2024 shakuro.com/blog/ui-ux-desig… – at Guarulhos, Brasil
2
437
Weslley ➜ broto.work retweeted
Transform your course material into an AI tutor: flashcards, quizzes, and more coming soon. ✨Accelerate✨ your learnign with your personalized AI tutor Spark.E. Get started at studyfetch.com
2
10
1
236
49,124
Weslley ➜ broto.work retweeted
Agora o @kiko666 entra um pouco em detalhes sobre algo que interessa a muitos: PREÇO da @magalu Cloud #CloudFutures
38
65
82
911
148,642
Weslley ➜ broto.work retweeted
let mind = "Star Trek" let real = mind.replace("Star", "Life") console.log(real) #dev
3
1
3
397