Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Had an interview on 10 Sept for Junior Backend role I and an engineer from the their team pair coded A multi tenant Key value store which stores and retrieves json data 100 MB storage quotas per tenant with LRU eviction when limits are exceeded

190,653 Aufrufe • vor 11 Monaten •via X (Twitter)

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

i just built a 4-agent software team. everything runs from Telegram and gets managed on a kanban board. a project manager who plans the work, a backend developer, a frontend developer, and a tester. the PM reads a goal, breaks it into linked tasks, and assigns each to the right agent. the thing that makes them a team instead of four strangers is a shared kanban board. every task is a row that survives crashes, and when an agent finishes, it writes a summary of what it built and what the next agent needs to know. the next agent reads that summary before it starts. so the frontend developer never has to guess the API shape, and the tester knows exactly what to verify. the hardest part was not the coordination. it was building an agent that could actually act like a backend engineer. a backend engineer stands up a database, wires auth, manages storage, deploys functions, and keeps all of it consistent while the rest of the team builds on top. an agent doing this from scratch drowns. it burns its context window remembering which tables exist and which endpoint it created three steps ago, and the work degrades fast. so the backend agent needs a backend built for agents, not for humans clicking through a dashboard. that is where InsForge came in. it is an open-source, agent-native backend, and i added it to my backend developer agent as a skill. a skill is a step-by-step guide that teaches the agent how to do a specific kind of work. with InsForge installed, the agent stopped improvising infrastructure and followed a reliable path: create the project, define the database, set up auth, deploy functions. to test the whole team, i had them build a working Google Docs clone, AI features included. the backend agent spun up the full service on its own. database tables, user auth, document handling, and edge functions running real TypeScript, all in one dashboard. the frontend agent read that summary and built the UI on top of it, and the tester closed the loop. the result was a backend an agent could reason about end to end, instead of one it kept getting lost inside. if you are building an AI backend engineer, InsForge is worth a look, it's 100% open-source. InsForge GitHub: (don't forget to star 🌟) the full article on Hermes Kanban: Mission Control for your Agents is quoted below.

Akshay 🚀

122,548 Aufrufe • vor 2 Monaten

David Friedberg: Michael Burry’s Datacenter Math is Wrong “I actually think Michael Burberry's got this wrong.” “What Michael Burry is saying is that all of these hyperscalers have extended their depreciation schedule or the useful life of their data centers by roughly 2x, which cuts the operating costs in half when they report it in earnings. And so it's making their earnings inflate.” “So he's claiming they're cooking the books. Google first made this change in Q1 of 2021, where they said the servers are now going from 3 to 4 years. Separately in 2021, Google took networking equipment from 3 to 5 years. And then in 2023, they took it from 5 to 6 years.” “And so this is a result of this effort where they went in and did an analysis. So what happened?” “What happened in the data centers is that the data centers transitioned from being primarily data storage and data transfer systems, where you would use hard drives and RAM and memory to store data and then transmit it back out, to being data processing centers because of the AI boom.” “So as AI became more important in the data center, more of the dollars that are going into data centers were allocated towards chips from data storage, which initially was hard drives.” “And then suddenly, when you put these processors in to process the data to do AI, the majority of the spend and the majority of the energy is going towards the processors.” “I made some calls and I checked around with some other friends, and everyone says the same thing: that these 7-8 year old TPUs and GPUs that are sitting in the data centers are still being used and they're being used at 100% utilization.” “So that actually justifies and validates the depreciation schedule being much longer versus shorter.”

The All-In Podcast

304,297 Aufrufe • vor 9 Monaten