Either Fullstack (senior/…/principlal), DevOps, Architect, or Team Lead/CTO, whatever - I grew up with having to do all the roles back in the day, from Startup Growth Hacking over Scale-Up Optimization to Enterprise Executive. Not crypto stuff or AI desperation.
I don't know, my own DevOps practises evolve around straightforward shell/go/js snippets that try to enforce the absolute bare reasonable minimum of infrastructure as cheap as possible, but with scaling paths laid bare if needed ever. sometimes a few lambdas/workers+CDN solve problems for essentially zero cost, sometimes people are amazed how far a single VPS can carry them nowadays. Or how fast SQLite can be. DevOps is about the art of shipping value to customers as fast as possible, at scale, with minimum cost (but not being the developer itself usually). With continuous improvement loops. But I can count on a single hand how often I actually needed to "scale up" something so hard I needed full on data migrations and all.
Huge fan of Cloudflare here actually. It’s always such a breath of fresh air compared to the heavyweight configuration hells like AWS. And for doing super convenient stuff like make node:http work on cloud functions recently, but guess only certain DevOps guys realize how cool that is compared to other FaaS wrapping ceremonies.
Too bad you don’t hire senior folks in Germany currently, would probably join in a heartbeat for emotional reasons alone. Keep going, lightweight features on a tap and solid reliability over years is exactly what I need and want at least.
also in the thinner camp here, and would gladly have accepted a way worse camera if they made the back uniformly thin actually. the closer we get to the "just a glass plate" thin design from the expanse the better :-)
but yeah, everywhere around all day there is charging options easily even in many public transports here around europe, battery life is simply not a convern anymore for most people at all. the only time i even thin kis when I forgot recharging over night for some reason, but then in the office theres plenty of options to recharge too
isn't this textbook "bitter lesson" playing out here again? whatever "frameworks" people try to build, the next generation of models will make them obsolete, no?
The models are still ingesting text, are they not? Those framework are providing textual guidance to what the task at hand should be aim for. Those are formalising part of the context passed to the LLM, regardless of the model itself.
Currently I am building a new JS web toolkit on the side with AI assistance for faster progress, and I came to have some prompts folder in the project root that I just drop into the agents (like cursor CMD+I) and point it to a direction (file/folder).
I think we should not split README and AGENT into different documents - the way its heading is that the coding agents are optimized to "act as" humans and use tools like them more and more - and understanding how something works or how to do something should be aimed for humans and expecting AI tools to pick it up like a human would... if they don't currently then probably they will in the the future.
Kind of my first thought... seems to me this could be part of README.md, or as another suggested CONTRIBUTING.md
I tend to put a lot of this type of info into the readme anyway... for more complex projects, I'll include a docs/ directory with more markdown, images as needed, etc.
For that matter, I think context hints from the likes of Dockerfile(s), compose, and .github/workflows also can serve a dual-purpose here.
Either Fullstack (senior/…/principlal), DevOps, Architect, or Team Lead/CTO, whatever - I grew up with having to do all the roles back in the day, from Startup Growth Hacking over Scale-Up Optimization to Enterprise Executive. Preferrably doing something _real_, not another purely digital product/service or crypto stuff. Connection to something physical I could touch, that also has a future.
In Elixir/Erlang thats quite common I think, at least I do this for when performance matters. Put the specific subset of commonly used data into a ETS table (= in memory cache, allowing concurrent reads) and have a GenServer (who owns that table) listen to certain database change events to update the data in the table as needed.
Helps a lot with high read situations and takes considerable load off the database with probably 1 hour of coding effort if you know what you're doing.
Remote: yes when timezone is reasonable
Willing to relocate: no
Technologies: Rust, Go, Elixir, JS/TS, Cloud stuff, AI/ML/Math, ...
Résumé/CV: https://anonyfox.com/cv
Email: max@anonyfox.com
—-
Either Fullstack (senior/…/principlal), DevOps, Architect, or Team Lead/CTO, whatever - I grew up with having to do all the roles back in the day, from Startup Growth Hacking over Scale-Up Optimization to Enterprise Executive. Not crypto stuff or AI desperation.
reply