Febriss33

can't it shift from just building a software to create a new "skill"? for non dev people its just easier to see it in this way.. fullfilling may come with the possibility to create some idea you can't bring to life before vibes. i'm vibe coding and i would be fullfilled if i could achieve reliability on an llm!!

you are right. i went to the paper, the original post is not clear about it.. they claim 11 bar instead of 9 of the normal espresso. well, just curious now to try it....

mmm.. what about pressure? the real espresso need pressure... is not just hot water. is the pressure of the expanding water that pushes it... not sure it would be the same stuff lol

had you ever been to rome? totally normal.. there is an entire hill made of roman pottery waste.. is a public park! best city ever

i'm not a dev and surfing vibe coding. for me is not just a matter of brevity but a matter of clear scope instead. foggy but short prompt is far worste than clear but a little bit longer. just transfer a clear and bright idea, first set it up in your mind, well fixed with the infrastructure you are working with, than try to transfer it in the most direct way

i let the main loop spawn sub terminal via tmux to prevent large contexts. it's great to divide tasks in small patterns and consolidate it step by step.

i'm not a dev. but i do a lot of stuff with claude code. waiting for the answer is tiring. i run different terminals on a project so i can skip one to the next. tiring as well because you need to be focused on the multi session but much better than prompting and wait.

just put an hard budget cap.. a good agent should have it. a protection for irreversible action as well. i run agents daily and use this way. another cool stuff is to have a triage protocol to downgrade the model for mechanical tasks, it burns a lot less tokens

in my opinion giving a strong idea helps a lot. just bring it clear in your mind and try to transfer with strong and clear scheme. in my experience this reduces the do and re do thing