Jamie Tsao

Lucky Husband, Proud Father, and Cal Bear. Head of Engineering @Gametime. Formerly @salesforce, @SumAll, @Squarespace, @IGTNews, @WellsFargo, Scient.

[Jamie Tsao @eimajination]

Built a personal poker tracking app with Claude Code.

A project I'd wanted to build for years. Empty repo to MVP in 3 hours. Full-fledged app in ~25 total hours.

The "100x engineer" thing isn't an exaggeration.

Blog post: https://t.co/LX9rr9wjfT

#claudecode #poker #ai

[WembyMuse @Wemby_Muse]

Same exact miss by JDub and Westbrook.

Same exact shot by Wemby and Curry.

The resemblance is uncanny 🤯

[Mitchell Hashimoto @mitchellh]

I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out.

I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really).

It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely.

The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture.

We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying.

I worry.

[I Am Devloper @iamdevloper]

Black Mirror S8E1: In 2027, developers are allocated a daily Claude token allowance by the government. A junior dev burns through his entire month's supply trying to centre a div. His family starve. He is forced to write the code himself. He can't. Society collapses.

[Om Patel @om_patel5]

stop spending money on Claude Code.

Chipotle's support bot is free:

[Jason Bosco @jasonbosco]

"We used to debate using tabs vs spaces in code we'd type out"

[Dan @robustus]

Turns out with claude code, my decades long strategy of NOT deeply learning:
- regexs
- sql
- nginx confs
- elaborate shell commands
- advanced shell scripting
- any javascript framework
- perf optimization
- webpack, cdns, bundlers
- 1000 other things

...was entirely correct.

[Jamie Tsao @eimajination]

@ClubWPTGold @WPT @WynnLasVegas @jamietsao - LFG!

[Jamie Tsao @eimajination]

Also, I’m looking to hire a Senior Backend Engineer: https://t.co/YwlX8v9VKm

[Jamie Tsao @eimajination]

Some observations and thoughts regarding AI and Hiring:

https://t.co/fN3sI321yu

#ai #hiring #recruiting

[Jamie Tsao @eimajination]

FINALLY - I’ve wanted this for so long!

[Kyle Daigle @kdaigle]

Been at GitHub for nearly 13 years and I'm pretty sure this request is more than 10 years old...

🆕Comment on unchanged lines in any file inside a Pull Request is now available

Gotta keep the core of GitHub getting better every day. 🫡

[Andrew Ng @AndrewYNg]

Some people today are discouraging others from learning programming on the grounds AI will automate it. This advice will be seen as some of the worst career advice ever given. I disagree with the Turing Award and Nobel prize winner who wrote, “It is far more likely that the programming occupation will become extinct [...] than that it will become all-powerful. More and more, computers will program themselves.”​ Statements discouraging people from learning to code are harmful!

In the 1960s, when programming moved from punchcards (where a programmer had to laboriously make holes in physical cards to write code character by character) to keyboards with terminals, programming became easier. And that made it a better time than before to begin programming. Yet it was in this era that Nobel laureate Herb Simon wrote the words quoted in the first paragraph. Today’s arguments not to learn to code continue to echo his comment.

As coding becomes easier, more people should code, not fewer!

Over the past few decades, as programming has moved from assembly language to higher-level languages like C, from desktop to cloud, from raw text editors to IDEs to AI assisted coding where sometimes one barely even looks at the generated code (which some coders recently started to call vibe coding), it is getting easier with each step.

I wrote previously that I see tech-savvy people coordinating AI tools to move toward being 10x professionals — individuals who have 10 times the impact of the average person in their field. I am increasingly convinced that the best way for many people to accomplish this is not to be just consumers of AI applications, but to learn enough coding to use AI-assisted coding tools effectively.

One question I’m asked most often is what someone should do who is worried about job displacement by AI. My answer is: Learn about AI and take control of it, because one of the most important skills in the future will be the ability to tell a computer exactly what you want, so it can do that for you. Coding (or getting AI to code for you) is a great way to do that.

When I was working on the course Generative AI for Everyone and needed to generate AI artwork for the background images, I worked with a collaborator who had studied art history and knew the language of art. He prompted Midjourney with terminology based on the historical style, palette, artist inspiration and so on — using the language of art — to get the result he wanted. I didn’t know this language, and my paltry attempts at prompting could not deliver as effective a result.

Similarly, scientists, analysts, marketers, recruiters, and people of a wide range of professions who understand the language of software through their knowledge of coding can tell an LLM or an AI-enabled IDE what they want much more precisely, and get much better results. As these tools are continuing to make coding easier, this is the best time yet to learn to code, to learn the language of software, and learn to make computers do exactly what you want them to do.

[Original text: https://t.co/HdI3Jb9HmF ]

[Jamie Tsao @eimajination]

@ClubWPTGold #BlackFriday

[Jamie Tsao @eimajination]

@tammygu 😂😂😂

[Jamie Tsao @eimajination]

@tammygu 3 painful weeks in a row

[Jamie Tsao @eimajination]

@tammygu 😠

[Awful Announcing @awfulannouncing]

Larry Beil of KGO (Bay Area's ABC affiliate) read "a great work of fiction," AKA John Fisher's letter to Oakland A's fans.

Then strongly reacted to it.

Well worth the time.

(H/T @LastDiveBar)

[Haralabos Voulgaris @haralabob]

Sheesh what a shot

[Jamie Tsao @eimajination]

@tammygu Now you understand the joy of being a Warriors fan 😜