Tim E

Founder of @prodigentai and amongst others🧑‍💻. Tweets about software engineering and makes jokes

[Tim E @TimEngng]

@dramaricic At least you're genuine. Can't stand those "oh I've been running for 3 months and I've got $3 billion in revenue whats next"

[Tim E @TimEngng]

For those still reviewing code, what’s the most rage-inducing thing? Opening a PR and seeing 100+ files? A page full of nits?

[Adnaan @adnaannasir_]

AGI is here 💀

[Tim E @TimEngng]

@Marc06669 @yongfook Is this still available

[Tim E @TimEngng]

@JackEllis yeah but can you tweet about it?

[Tim E @TimEngng]

@kumard_3 @yongfook what tool/stack you using?

[Tim E @TimEngng]

@launch_llama @Chartsy Still very much a work in progress but trying to build an "institutional knowledge" layer to support other tooling for eng teams - https://t.co/2HsxAvQKwW

[Tim E @TimEngng]

@dhh People act like it means software is no longer going to be built. Quite the opposite. Demand for software is increasing and someone still has to tell the agents and models what to build. I can do my taxes but still have an accountant (until I trust the model for that 😝)

[Tim E @TimEngng]

@lightsilver323 https://t.co/2HsxAvQKwW

[Tim E @TimEngng]

@yongfook I just started building for dev 😅

[Tim E @TimEngng]

@lightsilver323 https://t.co/2HsxAvQKwW

[Tim E @TimEngng]

For all these companies out there building with #AI without developers, what tools are you using, where are you hosting, how are you deploying etc?

[Tim E @TimEngng]

@OngDevLab why would you buy ram when you can just download some more

[Tim E @TimEngng]

@marshallpittman @oldstackjournal Mine was buying a magazine to get a bootable Linux cd

[John @hello_code_]

What’s one thing every founder learns the hard way?

[Tim E @TimEngng]

@hello_code_ Software alone doesn't sell

[Adam @adamdotdev]

Me when that one guy still looking at the code asks why we have both a `createdAt` and `created_at` column in the `users_v2` table

[Tim E @TimEngng]

@owenthcarey Jev

[Tim E @TimEngng]

@makhmudov9807 @prodigentai It’s a very good point. One approach I’ve used in the past is to try and link knowledge to code versions (where applicable) so it’s easy to know when something changes because the underlying code or infrastructure changed. But I think it may also just require some human review.

[Tim E @TimEngng]

I have slightly pivoted @prodigentai into an engineering intelligence layer for the institutional (aka tribal) knowledge trapped in your team’s heads, docs and Slack. Now available on the web and through MCP #buildinpublic