News for hackers. Stuff that matters.

smartworkflow

Amazing insights - thank you so much for sharing! What tools are you using and within what environment (monolithic/microservices..). Your approach to asking the AI to "explain' is a real pivotal moment for the engineers...from what I'm seeing in such intensives at least! This was my first post on HN so am delighted for your engagement! Will keep sharing my observations. BTW, the intensive I was observing was with a Series B start-up; post-acquisition so there was a real mix of habits and expectations...just wanted to share in case you or any other readers are in a similar environment. Thanks again!
Thanks for the comment! I think the most surprising thing was how the engineers almost pushed each other to use the agent "better" - write clearer and more defined prompts engineer-style as opposed to open and generic instructions that I might use as a non-engineer. To be the architect and the staff manager of the code.

I loved seeing how they were trying to outdo each other when tasked to build something that they hadn't tried before due to their limited experience with unknown libraries. Was really fun to watch - one guy built a tool to tell users how faraway starts were relative to each other and us, one built a travel diary...I guess seeing them go from "meh" to being engaged and having fun was really cool to see!

What changes in engineering teams once AI tools "click"?

A founder I work with recently ran a small experiment with an engineering team at a Series B company that I thought was interesting; I'm not technical but was curious as to how this session would play out.The setup was simple: six engineers spent a few 2 days experimenting with AI in their real development workflows. Nothing theoretical — just trying things directly against their codebase and...

( Read More... | 4 comments | on HN )