Yes, it's been a way better deal to go for a subscription than pay as you go for me in the past. I had a month where I burnt through ~3.8b tokens which was somewhere in the ballpark of $8k worth of savings.
Now though I don't dare use spend tokens for basic note taking with Sonnet because I'm hitting the limit over a couple million tokens on the 20x plan, so they've really tightened the purse strings since November.
The point of a diagram is that you have something in your head to turn into the diagram. There's no point if you can't do it yourself and the image generator is coming up with it for you.
I disagree. Diagrams are a type of visual communication, and not everyone is good at translating things to visual. I open an excalidraw with clear concepts in my head, but nothing comes out of it. I try C4 or flow diagrams, and I spend an excessive amount of time refactoring them to end up mediocre anyway. Not just me, I know MANY developers that are amazing at explaining things but are mind-blocked when drawing simple circles and arrows.
Helping us navigate things we aren't good at has been one of the main selling points of AI.
It's not translation if it's completely AI generated to begin with. Instead of addressing your mental deficits (which sound severe), you're offloading it and making the problem worse.
Well, out of all the workflows I have seen, this one is rather nice, might give it a try.
I imagine if the context were being commited and kept up-to-date with CI would work for others to use as well.
However, I'm a little confused on the autocontext/globs narrowing part. Do you, the developer, provide them? Or you feed the full code map to flash + your prompt so it returns the globs based on your prompt?
Also, in general, is your map of a file relatively smaller than the file itself, even for very small files?
- The ..-code-map.json files are per "developer folder," which would create too many conflicts if they were kept in Git.
- I have two main globs, which are lists of globs: knowledge_globs and context_globs. Knowledge can be absolute and should be relatively static. context_globs have to be relative to the workspace, since they are the working files.
- As a dev, you provide them in the top YAML section of the coder-prompt.md.
- The auto-context sub-agent calls the code-map sub-agent. Sub-agents can add to or narrow the given globs, and that is the goal of the auto-context agent.
It looks complicated, but it actually works like a charm.
Hopefully, I answered some of your questions.
I need to make a video about it.
But regardless, I really think it's not about the tools, it's about the techniques. This is where the true value is.
Are we still complaining about Tailwind? This ship has sailed. The world is so much better than the old BEM/LESS hell, it is wonderful. UnoCSS is even greater in empowering frontend developers.
Agreed. I owe a beer to whoever thought of BEM. It's saved precious brain cycles thinking of names. At first I was like what is this bem__opinion--rubbish but then it clicked and my workflow improved.
> Tailwind or any other CSS-in-JS system is not the recommended way to implement styling
I see, I'm not the target audience here, I can't see myself going back to the old ways. But I am happy that people who can't get into the wonder world of utility classes also have frameworks with their philosophy in mind from the core, which could provide more modern solutions for their preferred way of styling.
Let's see how this projects evolves overtime, best of luck!
Translation is a killer feature. All https//bitecode.dev is in english, but I'm French.
When I needed some complicated translation, deepl and google translate were rarely up to the task. They has about the same level of proficiency than me with auto-correct, sometimes less.
For single rare or technical words, I used Wikipedia a lot: you chose your topic in your language, you look for the article in English, and voila.
For slang and cultural references, urbandictionary.com is unmatched.
But for translating jokes or expressions, there is no good tool.
Until chatgpt. It also finds typo, suggest alternative, offer rhymes and synonymous. It does everything, in a single flexible interface.
I'm using it to write a browser based game engine.
The world doesn't need another game engine, and especially not by someone who has only technically written JavaScript professionally before, but there's some games that I wish existed on the browser, and one thing that world does need is for all the un-performant websites in the world to be embarrassed by the comparison.
reply