Recent submissions

Comment · 4 months ago
I built an agent harness that doesn’t actually code. I’ve been wanting something that can teach me as I go. Enter codetutor.

https://github.com/jaketothepast/codetutor

It’s an eMacs package that starts from a spec and will help you iterate on it if you want, and works from a core set of docs about a project plus active specs.

It also will keep a treesitter based representation of your codebase to help you form the architecture. It has no write tools, it will read a diff of your code on save to help. It also can be prompted openly.

It’s a pair programmer, but the other way around versus traditional agent harnesses. You’re the coder, the AI watches

Comment · 1 year ago
I’m here for it :) love the Clojure approach to symbiosis. Parens consume all the things!
Comment · 1 year ago
Its knowledge mainly, my company is covering tuition and I’ve always had a desire to understand computing “all the way down.” If the outcome would be that I’m still working similar jobs, I’d be alright with that. I commented on a different parent about what coursework I’m considering, maybe that would help me break into something lower level and not just be another backend job?
Comment · 1 year ago
Super valuable advice. The program I’m considering has VLSI design, chip architecture, and FPGA work all at the graduate level. I don’t know if the school has fabs but it’s seemingly well known and well funded so maybe?

As a part of this degree I’ve also selected coursework that is more related to CS. I’m looking at a compilers class, OS class, and neural networks as well.

With a focus on FPGA do you think that’s broadly applicable and evenly distributed geographically? I am prepared to move for certain industries, like working in space technology

Comment · 1 year ago
This is exactly where I’m at with my CS career. I am tired of abstraction. I want to be able to strip it away and work at the lowest levels of the stack. I’ve worked in embedded real-time environments before and found working with the system constraints to be highly rewarding. Yes there are tools that can write and test code for us now, but it’s also true that someone still has to build the low level high performance stuff.

What opportunity do you see in the realm of atoms?

Comment · 2 years ago
This was an amazing read, and frankly inspiring with regard to your final thoughts. I’ve yet to build anything substantial on the side but still searching for that idea
Comment · 2 years ago
now I’m convinced that a certain senior engineer at a very well known tech company had this as an instruction manual. I’ve experienced each of these multiple times from the same person!

On my own though, I’m certainly guilty of the 100 round trips. I tend to mentally group nits and not spell out every one that I find

Comment · 2 years ago
Comment · 2 years ago
Comment · 2 years ago
Hello fellow tri-cities resident. I probably know you :)

Can't say I disagree with much. Though my interactions with Niswonger Children's Hopsital have been great. Ballad itself? not so much.

Comment · 2 years ago
It may be time to finally learn it. I've standardized on Python, Clojure and C# of all languages (Julia for fun) but Rust may help me dive deeper into systems level problems.
Comment · 2 years ago
You're right. I think my biggest problem is that I always assume these crazy OSS projects were written because the author has always been this programming genius, when in reality they were just following their interests. For example, I caught myself with the proxy thinking about production scale. Who cares about production?? I just need to get going and build a single-threaded proxy that gets the job done. No need to worry about complexity, it's just for me.

Hard to remember that at times though.

Comment · 2 years ago
I loved this article, this is exactly what programmers in my community complain most about with regard to lisp.

The greatest strengths for me are the scoping and how lisp enables interactive development. For one, I don't even see parens anymore when writing code. They've become automatic where I'm able to parse structure at least better than I have in the past. With a REPL, (I specifically use Clojure), development has become fun again. A typical debugging process is attaching to my actual program, and calling functions seeing what happens.

I love the flow of defining functions in my code, `def`-ing some test data, and calling those functions. I'll use `cider-inspect` to see if the data structure looks correct and iterate.

Everyone should at least try a lisp. Iterative, interactive development is so fun and powerful.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton