Show HN: Company hiring trends and insights from job postings
6 by sp1982 | 0 comments on Hacker News.
I been building a view into companies based on their job postings. I am hoping it is useful to get a quick snapshot on the company say for interview prep etc. Please be advised that it is still a WIP in terms of data quality. Example urls: https://ift.tt/ymQuFE5 https://ift.tt/fuizvXV...
Wednesday, 21 January 2026
Tuesday, 20 January 2026
New top story on Hacker News: Ask HN: Do you have any evidence that agentic coding works?
Ask HN: Do you have any evidence that agentic coding works?
9 by terabytest | 4 comments on Hacker News.
I've been trying to get agentic coding to work, but the dissonance between what I'm seeing online and what I'm able to achieve is doing my head in. Is there real evidence, beyond hype, that agentic coding produces net-positive results? If any of you have actually got it to work, could you share (in detail) how you did it? By "getting it to work" I mean: * creating more value than technical debt, and * producing code that’s structurally sound enough for someone responsible for the architecture to sign off on. Lately I’ve seen a push toward minimal or nonexistent code review, with the claim that we should move from “validating architecture” to “validating behavior.” In practice, this seems to mean: don’t look at the code; if tests and CI pass, ship it. I can’t see how this holds up long-term. My expectation is that you end up with "spaghetti" code that works on the happy path but accumulates subtle, hard-to-debug failures over time. When I tried using Codex on my existing codebases, with or without guardrails, half of my time went into fixing the subtle mistakes it made or the duplication it introduced. Last weekend I tried building an iOS app for pet feeding reminders from scratch. I instructed Codex to research and propose an architectural blueprint for SwiftUI first. Then, I worked with it to write a spec describing what should be implemented and how. The first implementation pass was surprisingly good, although it had a number of bugs. Things went downhill fast, however. I spent the rest of my weekend getting Codex to make things work, fix bugs without introducing new ones, and research best practices instead of making stuff up. Although I made it record new guidelines and guardrails as I found them, things didn't improve. In the end I just gave up. I personally can't accept shipping unreviewed code. It feels wrong. The product has to work, but the code must also be high-quality.
9 by terabytest | 4 comments on Hacker News.
I've been trying to get agentic coding to work, but the dissonance between what I'm seeing online and what I'm able to achieve is doing my head in. Is there real evidence, beyond hype, that agentic coding produces net-positive results? If any of you have actually got it to work, could you share (in detail) how you did it? By "getting it to work" I mean: * creating more value than technical debt, and * producing code that’s structurally sound enough for someone responsible for the architecture to sign off on. Lately I’ve seen a push toward minimal or nonexistent code review, with the claim that we should move from “validating architecture” to “validating behavior.” In practice, this seems to mean: don’t look at the code; if tests and CI pass, ship it. I can’t see how this holds up long-term. My expectation is that you end up with "spaghetti" code that works on the happy path but accumulates subtle, hard-to-debug failures over time. When I tried using Codex on my existing codebases, with or without guardrails, half of my time went into fixing the subtle mistakes it made or the duplication it introduced. Last weekend I tried building an iOS app for pet feeding reminders from scratch. I instructed Codex to research and propose an architectural blueprint for SwiftUI first. Then, I worked with it to write a spec describing what should be implemented and how. The first implementation pass was surprisingly good, although it had a number of bugs. Things went downhill fast, however. I spent the rest of my weekend getting Codex to make things work, fix bugs without introducing new ones, and research best practices instead of making stuff up. Although I made it record new guidelines and guardrails as I found them, things didn't improve. In the end I just gave up. I personally can't accept shipping unreviewed code. It feels wrong. The product has to work, but the code must also be high-quality.
Monday, 19 January 2026
New top story on Hacker News: Show HN: Subth.ink – write something and see how many others wrote the same
Show HN: Subth.ink – write something and see how many others wrote the same
3 by sonnig | 0 comments on Hacker News.
Hey HN, this is a small Haskell learning project that I wanted to share. It's just a website where you can see how many people write the exact same text as you (thought it was a fun idea). It's built using Scotty, SQLite, Redis and Caddy. Currently it's running in a small DigitalOcean droplet (1 Gb RAM). Using Haskell for web development (specifically with Scotty) was slightly easier than I thought, but still a relatively hard task compared to other languages. One of my main friction points was Haskell's multiple string-like types: String, Text (& lazy), ByteString (& lazy), and each library choosing to consume a different one amongst these. There is also a soft requirement to learn monad transformers (e.g. to understand what liftIO is doing) which made the initial development more difficult.
3 by sonnig | 0 comments on Hacker News.
Hey HN, this is a small Haskell learning project that I wanted to share. It's just a website where you can see how many people write the exact same text as you (thought it was a fun idea). It's built using Scotty, SQLite, Redis and Caddy. Currently it's running in a small DigitalOcean droplet (1 Gb RAM). Using Haskell for web development (specifically with Scotty) was slightly easier than I thought, but still a relatively hard task compared to other languages. One of my main friction points was Haskell's multiple string-like types: String, Text (& lazy), ByteString (& lazy), and each library choosing to consume a different one amongst these. There is also a soft requirement to learn monad transformers (e.g. to understand what liftIO is doing) which made the initial development more difficult.
Sunday, 18 January 2026
New top story on Hacker News: Show HN: Run LLMs in Docker for any language without prebuilding containers
Show HN: Run LLMs in Docker for any language without prebuilding containers
8 by mheap | 1 comments on Hacker News.
I've been looking for a way to run LLMs safely without needing to approve every command. There are plenty of projects out there that run the agent in docker, but they don't always contain the dependencies that I need. Then it struck me. I already define project dependencies with mise. What if we could build a container on the fly for any project by reading the mise config? I've been using agent-en-place for a couple of weeks now, and it's working great! I'd love to hear what y'all think
8 by mheap | 1 comments on Hacker News.
I've been looking for a way to run LLMs safely without needing to approve every command. There are plenty of projects out there that run the agent in docker, but they don't always contain the dependencies that I need. Then it struck me. I already define project dependencies with mise. What if we could build a container on the fly for any project by reading the mise config? I've been using agent-en-place for a couple of weeks now, and it's working great! I'd love to hear what y'all think
Subscribe to:
Comments (Atom)