Nick Manning ⌨️ (@seenickcode) header
Nick Manning ⌨️ (@seenickcode) profile picture

Solopreneur, author, mentor, proud father of two. Building https://teapawt.net/t.co/XgY4W2H814. 🤘 Prev: Google, 3x startup CTO. 👨‍💻 Sharing my findings along the way.

EU 🇪🇺
Joined September 2008
Photo by Nick Manning ⌨️ (@seenickcode)Photo by Nick Manning ⌨️ (@seenickcode)Photo by Nick Manning ⌨️ (@seenickcode)Photo by Nick Manning ⌨️ (@seenickcode)Photo by Nick Manning ⌨️ (@seenickcode)Photo by Nick Manning ⌨️ (@seenickcode)Photo by Nick Manning ⌨️ (@seenickcode)
So I'm crafting content for a small book and course over this winter break - heck why not? Topic not yet public! Yesterday was day 0. I’ll be documenting my naive shot at this - because again, why not? Maybe it can cajole others to give a go? At minimum I can get some helpful feedback along the way from others. Here’s what I did yesterday starting from absolute 0: 1. I recorded a brain dump video, talking about who, what, why, how etc about my idea. Somehow video recording myself "put me on the spot" and I was able to focus more on conciseness. 2. I generated a book/course outline from this. I uploaded the video to otter.ai to transcribe it. I refined it into a tentative chapter outline and dumped it into Notion. Side note: I typically like the otter.ai iOS app to quickly record my thoughts so that's why I went with that. And for some reason I'm not a huge fan of writing like this in Markdown (i.e. via Obsidian) so I'm trying Notion. I like the writing experience in Notion especially with the prospect of later collaborating with an editor later. 3. Then I recorded a brain dump video on "topic A”. So this time not a video, just for convenience. I used willowvoice.com's macOS app to just talk away for 30 minutes directly into Notion. Talking for about 30 minutes gave me roughly 2000 words. Calculating how much I need to do this gave me a lot of motivation. For example, I want to craft a book and course where someone can choose to read or consume video. For video, I want to keep it to max 2-3 hours so I'm going for 10k words per hour. Therefore I whittle it down 2000 words with heavy editing. I think that after a few weeks of repeating this process I can achieve this goal, then heavily edit the content down further. Notes for the engineers reading this (warning, needless geeking out here). I may consider just self publishing later later + host the video version on a microsite served by a simple web-app that pulls the content straight from Notion (cached of course when served up). I can later host multiple publications courses using that same web app as it could support multi-tenant (extract domain from HTTP header -> determine tenant to serve up, host on same VPS for dollars a month). substack.com/@seenickcode if anyone wants to keep tabs on my progress and gain some insights. Definitely not an expert on this entire process but I think the conversations will be interesting along the way.
1
1
6
585
Nick Manning ⌨️ retweeted
RIP leetcode. anthropic’s hiring manager btw.
The coding interview is dead, at least for my team at Anthropic. I've seen enough to know that it no longer provides signal. I removed it from loops this month. I have a spicy, optimistic take - I think there's an opportunity for junior engineers: felixrieseberg.com/hunger-be…
8
23
2
283
42,534
Nick Manning ⌨️ retweeted
Replying to @jack
This is crazyyyyy.
52
65
64
1,026
278,632
Nick Manning ⌨️ retweeted
We believe voice is the most natural way to interact with intelligence, so we created Dessa, the most authentic full-duplex speech model ever built. Talking with it feels like talking with a person…full of emotion, nuance, pauses, and a natural cadence. block.xyz/dessa
4,188
7,136
4,746
69,122
13,553,574
Stressed navigating a challenge as an engineering manager? People challenges can be tough. I’ve found more and more that thinking in and leaning on frameworks to navigate those challenges at bare minimum can nudge one in the right direction. Stress can down immediately too thus leading to clarity of thought and an optimized outcome. And if the framework is repeatable and ends up useful, bonus – note it down for next time. My personal fav: SBI
139
Anyone else writing their first book, or thinking about it? I'm writing one for new engineering managers, aiming for about 17,000 words. Ultra hard mode now with a newborn at home so free time comes in short bursts. This past weekend I found a solid flow and setup that works 👇
2
1
4
327
Takeaway: it's far easier to shape a book as a list of crisp talking points than as pages of prose. Move them, cut them, merge them until the argument works. Then write.
1
40
Commit and push after every session. With herdr and Tailscale, I can riff from my phone and pick up where I left off. Interested to hear what has worked for others.
1
39
Nick Manning ⌨️ retweeted
Burnout happens when you work too hard with not enough meaning. "He who has a why to live for can bear almost any how" — Nietzsche
247
956
142
11,477
658,299
Je ne commanderai plus jamais chez @SGMJ_Officiel. Ces génies ont saisi MANUELLEMENT mon adresse de livraison INCORRECTEMENT dans @ChronopostSAV et l’ont envoyée à la mauvaise personne. Une incompétence scandaleuse.
1
141
Is it just me or do most engineers not really have a solid idea of what an engineering manager actually does?
149
Nick Manning ⌨️ retweeted
One of the best recent podcasts on AI. Neil has a gift for explaining all of the jargon and insights simply. (I’m not involved, just found it unusually educational).
Neil Movva (@neilmovva) started his career at Nvidia, working on GPUs and kernels, and has an unusually deep understanding of inference, from software to chips to power. We spend a lot of time on each of those layers, how they connect, and where the important tradeoffs are. What makes this conversation special is how detailed it is (like a 401-level class), yet Neil makes it remarkably clear and easy to follow. Today he runs Sail Research, a company building infrastructure for agents to make tokens as cheap as possible. We discuss: - Latency versus throughput - Why there are no bad chips, only bad pricing - The end of kernel engineering - Buying chips and power no one else wants - New chip architectures - Nvidia lore + his contrarian view of the company - Open source and the frontier labs I learned a ton. Enjoy! TIMESTAMPS 0:00 Intro 0:38 Building a “Token Factory” 4:21 The Future of Background Agents 13:09 Nvidia and the GPU Stack 23:27 Chips, Memory, and Transformers 36:14 The Future of AI Training Data 44:32 Chip Scarcity and Compute Arbitrage 52:44 Reinventing the AI Data Center 59:01 Power and the “Scavenger Strategy” 1:10:10 Open vs. Closed AI
162
1,501
27
14,856
1,748,008
who made this masterpiece ?
377
1,849
505
12,154
1,653,073
Nick Manning ⌨️ retweeted
Origin, our code hosting platform, is now live. It's fast, easy to use, and deeply integrated with Cursor. Get started by syncing your repos from GitHub.
1,507
2,362
2,814
25,332
26,325,850
Nick Manning ⌨️ retweeted
New: A map of the most important skills in AI Engineering.
569
4,136
484
24,596
6,993,284
Nick Manning ⌨️ retweeted
I got early access to Grok Bot and I'm hooked. I haven't been this excited about a new AI product in a while. It's like OpenClaw, but super easy, reliable, and less scary to use. I think this will be a huge new product line for Cursor/Grok/SpaceX. I've already found so many ways to use it that have meaningfully made my life better: 1. Matchmaking people looking for jobs with companies who are hiring (see below) 2. Auto-replying to support emails (saves me hours!) 3. Scanning my credit card statements and finding recurring subscriptions to cancel 4. Sending me (really good!) briefs for upcoming podcast guests See below for my actual set of agents that I've been using and chat with daily. Great work on this team Grok Bot. (I'm not an investor in this, nor do I have any ties to this product/company. I'm just a fan!)
Introducing Grok Bot, now in early beta. Bots are AI teammates that do real work for you. They sign in to your tools, use them just like you do, and come back with finished work.
228
228
43
4,181
1,369,776