Activity
Mon
Wed
Fri
Sun
Nov
Dec
Jan
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
What is this?
Less
More
9 contributions to Snappy Community
Question for people running companies in the US.
I am an entrepreneur and a tech professional. Been working with software systems for quite a while, and one pattern comes up a lot. The first version works fine. Then customers grow, operations get bigger, and little technical problems start showing up everywhere. Too many manual steps. APIs that don’t talk properly. Slow backend. Data sitting in different places. AI added, but not really connected to the actual workflow. Usually not one huge problem. More like five small ones quietly costing time every day. For those running a company now, what’s becoming harder on the technical side as you grow?
0 likes • 2d
Those quiet, small breakdowns across disconnected tools usually drain more momentum than one major bug. My rule of thumb is keeping technical task tracking in Floment AI right alongside our GitHub commits so edge cases do not slip between tools. Having clear progress updates outside the codebase stops those small daily friction points from piling up unnoticed.
The more I use coding agents, the more I realize the bottleneck is shifting.
Writing the code is getting faster. Keeping the agent focused on the right problem is becoming the harder part. My setup lately is claude.ai for working through the codebase, github.com for the actual code/history, and floment.ai for keeping the project, tasks, and next steps clear outside the agent. Feels like agentic development needs good project context almost as much as good prompts. How are you guys keeping agents aligned on longer builds?
0 likes • 5d
@Robert Boulos Having the agent check its own output against repo docs via hooks is a game changer. I'd love to see a breakdown of how you have Jev configured in that loop!
Speed and Ownability: The Two Promises of Modern Development
Speed and ownability have emerged as the defining promises of modern software development, particularly in the no-code and low-code spaces. These twin commitments address clients' most pressing concerns: the need to move quickly in competitive markets and the desire to truly own their technology assets. Speed addresses the existential business concern of opportunity cost and market timing. Clients often have a limited window to capitalize on market opportunities, and delays can mean the difference between success and failure. Speed is about collapsing the timeline from concept to functional deployment. It means reducing friction throughout the entire development process, from initial meetings to final handoff. Ownability refers to the client's ability to understand, maintain, and extend the software without continuous dependency on the original developer. It manifests in clean, documented code, logical data structures, and transparent systems. Clients who feel able to understand their systems can make bolder business decisions. They value not just the functionality but the fact that they can explain it to others—the system becomes a genuine business asset rather than a black box they fear to touch. By focusing on these promises, developers can create significantly more value for their clients. You won't just deliver functional software—you will deliver business transformation through systems that launch quickly and can be confidently owned by the client.
Speed and Ownability: The Two Promises of Modern Development
0 likes • 9d
Client ownability really comes down to how clean your handoff documentation looks once the initial build sprint wraps up. I make a habit of logging architectural decisions and data flow notes in Floment AI right alongside repository updates on GitHub so the client has full context. That way the system never turns into an intimidating black box when internal teams take over maintenance.
Memory MCP?
Hey y'all. Fairly new to all of this. Does anyone have a good method for claude to store memory so that I can start a new chat without having to repeat prompt background and instructions for my project?
0 likes • 16d
Rebuilding context for every new chat gets exhausting quickly when working across multiple features. Instead of relying solely on chat history, I keep code organized on GitHub and maintain core architecture rules on Floment AI project cards so I can reference them instantly. That gives the model a clear boundary without needing a massive prompt every single time.
Week Two Reflection: Consistency Over Comfort Self accountability 🥈
This week taught me one important lesson: progress doesn’t come from feeling ready; it comes from showing up anyway. 🚀 I’ve been developing a tool that I keep referred to in the video as an “automation” tool. However, I know better it’s a custom quote generator. 🧾 This tool features reusable templates, allowing companies to avoid the tedious process of rebuilding quotes from scratch. They won’t have to jump into Canva, place images, format text, and repeat that entire process each time. Or constantly looking for files to copy paste The contents to not have to write it down every time The real value lies not in buzzwords, but in the time saved. ⏱️ I’m new to this, and things break; some features only work halfway. My laptop moves as if it's on vacation! 💻🐢 However, I still committed. 🔁 Here’s what I learned: - Consistency beats talent when talent gets tired. 💪 - Confidence comes after taking action. 💼 - Broken things are feedback, not failure. 🧠 Nothing is perfect yet. The user interface still needs improvement, and the templates aren’t finished. But I’m not the same person I was two weeks ago Heck! I’m not even the same person I was a year ago. 🌟 This journey isn’t just about building one app; it’s about developing discipline. 📈 If I occasionally use the wrong words, understand that my intentions are right. I might call it “automation,” but what I really mean is saving people time and reducing stress. 😊 And if my Accent sounds different, that’s just the Caribbean in me! 🌴 I’m focused on fixing code, not my accent. So for those that might have an accent remember what matters most is your hard work and dedication 😂🫡👊🏾 Week two is complete, and week three is on the way. I’m not stopping! 🚀
Week Two Reflection: Consistency Over Comfort Self accountability 🥈
1 like • 23d
Showing up consistently is definitely the hardest part when you are trying to ship something real. I usually keep my templates in Canva, but I use Floment to track my weekly tasks so I can see the progress building up. It keeps things a lot more grounded when you are juggling multiple moving parts.
1-9 of 9
Tony Iverson
1
2 points to level up
@tony-iverson-7089
Building things online and trying to optimize my daily workflow. Here to learn from founders who are a few steps ahead.

Active 20h ago
Joined Jul 8, 2026
Powered by