Adam Jorgensen

💭 Thoughts on the tech hiring market right now… Despite all the noise around AI automating software development, I’m seeing strong demand for software engineers — but with a clear shift. Most of the hiring activity is focused on senior engineers: People who can design systems, not just write code Engineers who can work with AI tools effectively Those who can take ownership, make trade-offs, and move fast in complex environments My sense is that companies will hire senior developers more than ever before as leverage points — especially in startups and scale-ups where execution really matters. The open question for me is 👇 👉 What happens to the junior developer job market? Will entry-level roles shrink? Do juniors need a completely different skill set to get hired? Companies invest less in training and more in experience? I’d love to hear what others are seeing — founders, CTOs, engineers, recruiters. And if anyone is currently hiring software developers (especially senior engineers) or thinking about it, feel free to comment or DM me — always happy to share market insight or help where it makes sense. 👇 Over to you — what’s your take?

7

2 Comments

If your Node.js apps rely on **AsyncLocalStorage / async_hooks** (read: *most production services + a lot of observability tooling*), this one’s worth bumping to the top of your patch list. A newly disclosed issue (**CVE-2025-59466**, CVSS **7.5**) can turn a stack overflow into a **hard process exit (code 7)** instead of a catchable error — meaning **unsanitized, input-controlled recursion** can become a very effective **DoS “kill switch.”** And yes, that includes common stacks like **Next.js / React Server Components** and many **APM/telemetry agents** that hook async context. What to be concerned about: - **“It’s just a stack overflow”** becomes **“the whole server is down”** when async_hooks is in play - **APM ≠ free**: instrumentation can change failure modes in surprising ways - **EoL Node versions (8–18)** stay vulnerable—no patch coming, so upgrades aren’t optional Fixed in: **Node 20.20.0 / 22.22.0 / 24.13.0 / 25.3.0** Article: https://lnkd.in/eeDpexAz #NodeJS #JavaScript #AppSec #CyberSecurity #VulnerabilityManagement #DevSecOps #SRE #Observability #NextJS #OpenTelemetry #APM #DoS #CVE Security is a streak you can’t afford to break.

What Firms Actually Mean by “Strong C++” in 2026 𝗣𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝗼𝗻-𝗴𝗿𝗮𝗱𝗲 𝗖++  • Modern C++ (17/20+), RAII, ownership models  • Memory safety, cache locality, predictable allocation  • Writing systems that run 24/7 under load 𝗟𝗼𝘄-𝗹𝗮𝘁𝗲𝗻𝗰𝘆 𝗳𝘂𝗻𝗱𝗮𝗺𝗲𝗻𝘁𝗮𝗹𝘀  • Lock-free / wait-free design where it matters  • CPU pinning, NUMA awareness, branch prediction  • Understanding when optimization helps and when it doesn’t 𝗗𝗲𝗯𝘂𝗴𝗴𝗮𝗯𝗹𝗲 𝘀𝗽𝗲𝗲𝗱  • Deterministic behavior  • Reproducible performance issues  • Instrumentation and profiling built in, not bolted on 𝗪𝗵𝗲𝗿𝗲 𝗖++ 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝘀 𝗔𝗿𝗲 𝗕𝗲𝗶𝗻𝗴 𝗗𝗲𝗽𝗹𝗼𝘆𝗲𝗱  • Market data & feed handlers  • Execution & order routing  • Strategy infrastructure  • Core trading platforms 𝗪𝗵𝗮𝘁’𝘀 𝗖𝗵𝗮𝗻𝗴𝗲𝗱 𝗦𝗶𝗻𝗰𝗲 𝟮𝟬𝟮𝟯–𝟮𝟬𝟮𝟰  • Fewer “rewrite everything” projects  • More precise optimization of critical paths  • Tighter coupling between C++ engineers, quants, and FPGA teams  • Higher expectations per hire, smaller teams Connect & Follow to get more market insights! 

14

As a Vue developer living in a React world, I find myself often trying to bridge the gap between the Vue SFC, and TSX in an attempt to bring contributions from other devs. With defineComponent, and TSX we can get "close" to a React-like DX, however a lot of nice-to-haves are missing. 1. No macros Not being able to use defineProps as a macro when working with defineComponent brings us back to the Vue 2 object definition for props which is verbose. Same with defineEmits. 2. Slots feel awkward When coming from React we have "children" which are first-class tools, however in Vue / TSX you find things like slots.default?.() which means you're writing defensive code around slots. 3. Generic typing breaks down for components In React, a generic TSX component can infer its types directly from usage, but in defineComponent there is no way to parameterize a component over a type, so inference stops at the boundary. A simple generic list becomes difficult to work with as Vue will infer everything as unknown. Anyone else trying to use defineComponent? Any success stories?

3

Rails recruiters spend about 30 seconds on your GitHub profile during initial screening. Here's what actually matters: What recruiters notice first: 🔹 Pinned repositories - Choose 6 that show production Rails work, not tutorial projects 🔹 Recent activity - Consistent commits matter more than intensity 🔹 README quality - Clear setup instructions and project context signal professionalism 🔹 Code quality - Recruiters often spot-check your pinned projects What hurts your profile: 🔹 Dozens of abandoned tutorial repositories 🔹 No commits in 6+ months whilst claiming active Rails work 🔹 Vague descriptions like "Rails app" with no context 🔹 Poor code quality in showcase projects Quick wins for Rails developers: 🔹 Pin projects demonstrating Rails-specific skills (Hotwire, testing, performance) 🔹 Write clear README files explaining what problems you solved 🔹 Archive or delete incomplete learning projects 🔹 Update your bio with current role and specialisation 🔹 Add "Open to opportunities" if you're job seeking Pro tip: Contributing to Rails gems or the framework itself carries more weight than personal projects. Even documentation improvements demonstrate community engagement. Your GitHub profile often determines whether recruiters contact you. Worth 30 minutes to optimise it properly. What's on your pinned repositories? We're connecting Rails developers who showcase their capabilities effectively with companies seeking proven expertise. #GitHubTips #RailsDevelopers #TechRecruitment #CareerAdvice

6

3 Comments

CockroachDB now supports Protocol Buffers as a first-class CDC output. Teams using Protobuf—especially in Kafka—can stream changes directly, no conversion layers or glue code required. Protobuf changefeeds produce smaller, typed, language-neutral messages using a shared .proto schema, making pipelines simpler and faster. More here: https://cockroa.ch/4auk4FC

47

We just released Taro's newest course about what life is really like at FAANG. So much of the discussion about working at FAANG focuses on things like the scale of the work or the free snacks. But on the day-to-day level, an engineer at Google or Facebook doesn't think about these topics. They are spending most of their waking hours on things like: - how much scope do they have? - how much control do they have vs just being a cog in the machine - what do their coworkers think about them? As a 5 year veteran of Meta, I break down the real pros and cons of working in Big Tech. Check it out here: https://lnkd.in/gfkwVDf9

58

4 Comments