Hacker News5d ago

If you thought the code writing speed was your problem; you have bigger problems

https://andrewmurphy.io/blog/if-you-thought-the-speed-of-writing-code-was-your-problem-you-have-bigger-problems

#HackerNews #codewriting #speed #biggerproblems #softwaredevelopment #codingchallenges #techinsights

If you thought the speed of writing code was your problem - you have bigger problems | Debugging Leadership

AI coding tools are optimising the wrong thing and nobody wants to hear it. Writing code was already fast. The bottleneck is everything else: unclear requirements, review queues, terrified deploy cultures, and an org chart that needs six meetings to decide what colour the button should be.

Debugging Leadership
Hacker NewsFeb 24

Build Your Own Forth Interpreter

https://codingchallenges.fyi/challenges/challenge-forth/

#HackerNews #BuildYourOwnForthInterpreter #ForthProgramming #CodingChallenges #TechEducation #SoftwareDevelopment

Build Your Own Forth Interpreter | Coding Challenges

This challenge is to build your own Forth-like interpreter. Forth is a stack-oriented programming language that was designed by Charles H. "Chuck" Moore and first used by other programmers in 1970. It gained an official standard in 1994.

Hacker NewsJan 11

A set of Idiomatic prod-grade katas for experienced devs transitioning to Go

https://github.com/MedUnes/go-kata

#HackerNews #IdiomaticGo #katas #forDevs #GoTransition #CodingChallenges #Programming

GitHub - MedUnes/go-kata: A collection of daily coding challenges designed to help you master idiomatic Go through deliberate, repetitive practice.

A collection of daily coding challenges designed to help you master idiomatic Go through deliberate, repetitive practice. - MedUnes/go-kata

GitHub
androsDec 30
Después de mucho trabajo, ahora mi libro «Desafíos de programación atemporales y multiparadigmáticos», ahora esta en formato ebook 🤖🎊

https://www.amazon.es/dp/B0GD1T8HNY

#programacion #codingchallenges #desarrollodesoftware #python #algoritmos #techskills #programminglife #javascript #anuncio
N-gated Hacker NewsDec 16
🚨 Alert: 🚨 Programmer discovers that Rails Global IDs aren't as foolproof as he imagined—shock! Instead of living in blissful ignorance, he embarks on a noble journey to make them "safer" ⚔️. Meanwhile, the rest of the tech world is busy with something called "progress." 😜
https://blog.julik.nl/2025/12/a-trap-with-global-ids #RailsGlobalIDs #ProgrammerDiscovery #TechJourney #SoftwareDevelopment #CodingChallenges #HackerNews #ngated
Making Rails Global IDs safer

The new LLM world is very exciting, and I try to experiment with the new tools when I can. This includes building agentic applications, one of which is my personal accounting and invoicing tool - that I wrote about previously As part of that effort I started experimenting with RubyLLM to have some view into items in my system. And while I have used a neat pattern for referencing objects in the application from the tool calls - the Rails Global ID system - it turned out to be quite treacherous. So, let’s have a look at where GlobalID may bite you, and examine alternatives and tweaks we can do. What are Rails GIDs? The Rails global IDs (“GIDs”) are string handles to a particular model in a Rails application. Think of it like a model URL. They usually have the form of gid://awesome-app/Post/32. That comprises: The name of your app (roughly what you passed in when doing rails new) The class name of the model The primary key of the model You can grab a model in your application and get a global ID for it: moneymaker(dev):001> Invoice.last.to_global_id Invoice Load (0.3ms) SELECT "invoices".* FROM "invoices" ORDER BY "invoices"."id" DESC LIMIT 1 /*application='Moneymaker'*/ => #<GlobalID:0x00000001415978a0 @uri=#<URI::GID gid://moneymaker/Invoice/161>> Rails uses those GIDs primarily in ActiveJob serialization. When you do DebitFundsJob.perform_later(customer) where the customer is your Customer model object which is stored in the DB, ActiveJob won’t serialize its attributes but instead serialize it as a “handle” - the global ID. When your job gets deserialized from the queue, the global ID is going to get resolved into a SELECT and your perform method will get the resulting Customer model as argument. All very neat. And dangerous, sometimes - once LLMs become involved.

Julik Tarkhanov
Hacker NewsDec 14

Surface Tension of Software

https://iamstelios.com/blog/surface-tension-of-software/

#HackerNews #SurfaceTensionOfSoftware #SoftwareDevelopment #TechInsights #CodingChallenges #SoftwareEngineering

Surface Tension of Software

How systems hold their shape through constraint, and why integrity emerges from what you make impossible

~/iam
N-gated Hacker NewsDec 13
🎄✨Ah, the annual Advent of Code ritual—where our hero bravely battles coding challenges for shiny digital stars, fueled solely by caffeine and the adoration of a dwindling community. This time, Oscar's riding high on the Gleam train, discovering that when life gives you fewer coding days, you just...gloat about the stars you've already collected. 🚀💻
https://blog.tymscar.com/posts/gleamaoc2025/ #AdventOfCode #CoderLife #DigitalStars #CodingChallenges #GleamTrain #HackerNews #ngated
I Tried Gleam for Advent of Code, and I Get the Hype

A 12 day Advent of Code year convinced me Gleam is the real deal, thanks to Rust-like errors, great pipes, and surprisingly ergonomic FP.

The Tymscar Blog
taylorDec 12

Day 12 done.

I really didn't like this one. Basically have to do some bounds checking "it obviously always works" or "it obviously will never work" on it to get it to work on the actual input, but it still NEVER FINISHES on the example. I'm slightly bothered that the problem is more or less unsolvable as written, but I'm really bothered by the actual solution for the input not working on the example. That's not a fun puzzle, that feels like I'm being tricked, like the puzzle was a prank on me. Leaves a real sour taste, especially being the last puzzle of this year's AoC.

#AdventOfCode #AdventOfCode2025 #AdventOfCode2025Day12 #Day12 #Rust #RustLang #Programming #CodingChallenges #AoC #AoC2025 #AoC2025Day12

2025/src/bin/day12.rs at main

2025

AxFive
taylorDec 11

Day 11 done.

Memoization actually worked for this one. My first instinct was to just crawl the graph with a memo, and it fortunately did the right thing. It was effectively an exhaustive depth-first search. Really not much to discuss.

My code is not nice or clean, but after yesterday's, I can't even be assed to clean it up or properly comment it. I barely gathered the gumption to pass errors up, and when I started writing it, I was just throwing unwrap() everywhere.

#AdventOfCode #AdventOfCode2025 #AdventOfCode2025Day11 #Day11 #Rust #RustLang #Programming #CodingChallenges

2025/src/bin/day11.rs at main

2025

AxFive
taylorDec 10

Day 10 part 1 done.

Part 1 was a little tricky and fun. Solved it by just testing every combination, and sped that up by turning all the buttons and the goal light configuration into numbers that I could XOR together.

Technically, part 2 is done too, but it will never work on the real input. I threw memoization at this thing knowing that it wasn't going to work, but thought I might get lucky and the input would be constructed in a way that it would be fine. Nope.

I gave up and looked at the solutions thread on Reddit, and it looks like almost everybody is just throwing a solver at it (and the ones that aren't are using things like fraction-free Gaussian Elimination, which I can't hope to understand at this point in the night), and there are only 26 comments after 1.75 hours, so I guess this is a really hard problem this year.

I might come back to it tomorrow, but I doubt I'll find a good solution on my own. I don't want to just throw a solver at it if I don't have to.

#AdventOfCode #AdventOfCode2025 #AdventOfCode2025Day10 #Day10 #Rust #RustLang #Programming #CodingChallenges

2025/src/bin/day10.rs at main

2025

AxFive