Director of Engineering. Building AI products + AI-native engineering teams. Talks SDLC, architecture, and dev craft. Find your next read using Bookwise.
Joined October 2011
- Tweets11.4K
- Following495
- Followers1.4K
- Likes7.1K
The diligence questions I care about most are 3 and 5 together: can the org absorb new tooling without turning every tool into a six-month project, and is engineering actually bought in?
The greatest myth across the entire industry right now is that after this feature we will start making good technical decisions
You can't vibe code empathy!
Empathize with your user and you’ll build the right thing
Empathize with your team and you’ll make the right decisions
Empathize with your project and you’ll solve the right problems
The problem with AI is that we end up trying to build too much too fast
Your real competitive advantage is restraint
AI gave me the false impression that i can multitask more than im actually able to. i'm refining my workflow to focus more on single tasks
i think this is true for B2C but for B2B it matters a whole lot to people outside of tech
eg how/where your data is held is a legal issue
stack can influence browser support for web apps which is important for the whole org etc etc
most software has alwasy been CRUD operations with some workflow on top so at least we have a bit more now
its fine if they represent the persons opinion and but just throwing slop out there for the sake of exposure is so annoying
100% agree. people that think having an equivalent product is all thats needed have clearly never worked in a competitive market
Sha Alibhai | Director of Engineering retweeted
I have been coming back to this advice so much recently
“The questions you ask yourself determine your future; they guide your focus, which guides your actions and ultimately your results.”
— @geoffwoods , The AI-Driven Leader
via Bookwise
bkws.app/s/DB8n6f
