You have a story ready for your next interview. There’s a situation. A task. An action. A result.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
When a Linux machine can’t reach the network, first find out what interfaces the kernel sees and whether they have addresses. A quick check can distinguish a missing device from one that’s simply down or not configured. For a fast scan, run: ip -br addr show You’ll get one line per interface, including its state and any assigned IP addresses. If you only need interface names and link state, use: ip -br link show To print just the names, without parsing command output: ls /sys/class/net That last command reads the kernel’s sysfs interface, so it’s handy in minimal environments and scripts. The
Repository: https://github.com/albrescamily/semantic-image-search Some people say we learn more from our mistakes… well, I can say I've learned a LOT by doing this project. The goal was to create a system that receives an image or a text query and searches for matches in a database, similar to how Google Photos works. It seemed simple at first, but as I got into the mechanics, I kept running into problems that looked trivial on the surface and turned out to be much harder than I expected. I will start by explaining the architecture, the design decisions I made, and why I made them. Also, I wil
An Express health check page says the lesson-publishing API is unavailable. The Node.js /ready endpoint is failing while /live still answers, and the on-call view shows the last readiness transition; it does not merely say "CPU high." That evidence is enough to ask whether learners lost access, whether only new publishing failed, and which release was serving traffic. TL;DR: give an Express service three deliberately different endpoints: /live proves the process can answer, /ready says it may receive traffic, and /health returns a compact operator-facing summary. Record every readiness transit
Extending PcDevice Search: Regex Limits and Invoice Fields Integration TL;DR: I tightened the collaborator‑number regex to accept only 3‑6 digits and added invoiceNumber / purchaseOrder fields to the PcDevice model, making them searchable and visible in the device detail sheet. The changes touch the Prisma schema, the global search logic, the device store hook, and the UI component that renders device details. The internal inventory tool (pcview) allowed users to search for collaborator numbers without any length restriction. This caused false positives when a user typed a long numeric string
Discussion (0)
Log in to join the discussion and vote.
Log in