@Vercantez Very interesting approach! Something I couldn't find during the read is network isolation. Does the model have full unrestricted network access?
@saranshhx Exactly what I'm trying to figure out. I see lots of people mention SKILLS, AGENTS md. But what do you write there? Perhaps documenting the architecture of project is something that could fix AI from doing random stuff every time.
Layered, domain-driven, hexagonal, clean, micro services, etc? There are so many around. My project is hono/next/react-router app. How to know which one to use? Turned out your project can be multiple of them at once.
Could it be that architecture is the answer to project's maintainability during AI? Like you border AI by certain rules, boundaries. Curious what kind of tool, skill or any other AI capability can help me to make it? Or is it just enough to write docs?
In these AI-driven times of vibe-coding, how do you guys keep your projects maintainable? Does anyone even have an example of a maintainable AI-written project? So far it looks that just a simple prompting is not enough.
we taught TypeScript to understand GraphQL queries!
๐ today weโre releasing gql.tada, which infers types for GraphQL docs right in TS as you type them! together with our LSP plugin, this is the smoothest GraphQL client experience yet โจ
What works for me to get into the focus mode:
โธ๏ธ Take a break before jumping in to next project. Walking, meditating, running, or anything that helps you switch your brain from what you've done and makes you start with a clean state of mind.
๐ฅ๏ธ Dedicate a zone specifically for work. No eating there, no playing games. You make an anchor for your brain, having a dedicated zone teaches yourself that every time you enter the zone you focus on work and nothing else. When making breaks, step away from the zone. This approach is described well in "Study less study smart" book and youtube video by Marty Lodbell
๐ Prepare a plan. Think about what you will work on the next half an hour - hour, the tasks should be small and achievable. Tho, it comes with a practice, at the beginning you may find that you ended up working on something else or the task took more time then you expected. It happens from time to time, this is fine, reflect on why that happened. Summarize what you actually have done and how your plan should have looked like. Keep doing and your plans will become more and more stable.
Hope it would be helpful. Let me know what worked for you or what made you struggle.
What do you do when life gets in the way?
Between my 9-5 and apartment moving, I find it hard to work on my projects at the same intensity as before
I tend to work a few times per week in longer sessions as it takes me a bit of time to get into flow/focus mode.
I've found it a bit hard lately to find enough time for a proper session - only bits of time here and there.
Is anyone here able to utilize small sessions (30 mins ~1 hr) for actually productive work?
How do you get into focus/flow mode quickly?
Stumbled upon this nice article, great cheatsheet for choosing a tech stack for your next project.
Well done, @watchclock123! ๐ช
https://t.co/2qwZBNZ7yn
I love refactoring! Transforming an old, unmaintainable piece of art into a structured, reasonable code is so satisfying. ๐คค Even tho after some time, it turns back into an unmaintainable mess.
@MyBrainDrip Yep, fully agree with that.
What I wanted to say. It's better to keep code documentation within the project, set up validation/linter for it, which would make it easier to detect when it gets outdated.
โ ๏ธ Don't document your code in external tools like Confluence. Use it to describe the concepts, flows, high-level architecture, cross-project designs, etc., but not the code. It's hard to maintain and keep up to date.
@MyBrainDrip That's a great advice!
The problem I see with documenting code in external tools is that they are disconnected from the code and don't have appropriate validation, which makes it easy to get outdated. Even if it's incorporated into the workflow.