jergason

From reading the readme, it looks like superseded decisions are not added to context.

> Next session, the relevant lines are added to Claude's context.

At least that's how I interpret it? If it is adding superseded decisions, that does seem bad.

Most businesses are totally fine if they have a few hours of downtime. More uptime is better, but treating an outage like a disaster or an e-commerce site like a power plant is more about software engineer egos than business or customer needs.

If AWS is down, most businesses on AWS are also down, and it’s mostly fine for those businesses.

Shortcut | Senior Product Manager | Remote (US time zones) | Full Time | https://shortcut.com

Shortcut builds project management tools for modern software teams.

We’re looking for a Senior Product Manager who is excited to work on building tools for how product and engineering idea/plan/build/ship software.

Bonus points if you have used Jira before and are excited at the prospect of taking some of their market share!

More information at https://boards.greenhouse.io/shortcut/jobs/6454623002.

Agreed, this was delightful to read! I really appreciated how the author was open about naivety and blind spots. It made the contrast more apparent when they learned things. I'd love to read more by this person.

The OP explicitly mentions Chesterton’s Fence.

I wrote about this a few years ago too! https://link.medium.com/UUBEJ4ZOSZ

Why’s Poignant Guide To Ruby is also in this vein, though a bit weirder.

Why would HR IT have worse software developers than other industries?

He also helped write yarn, an alternative client to the official npm one.

FWIW the comment you're calling out here is four years old: https://github.com/npm/npm/blame/d3095ff20b8ea01e7fbf93a4a69..., before npm inc was formed.

The correctMkdir change seems more recent, but not really related to that specific comment.

Dangit, Cloud to Butt Plus strikes again.

Yours.co | Lead Software Developer | ONSITE Utah http://yours.co

Yours.co is looking for a software developer to build and lead a small team of two or three other developers in building their platform for offline backup of cloud storage.

You will be the head of software development at Yours.co and one of the first full-time software hires. You’ll have the opportunity to build a team, establish a process, pick a tech stack, and help settle the age old question of whether to use tabs, spaces, or extra semi colons to indent lines. This is a chance to create the culture you want and grow as a developer and person.

Because the team is relatively small, this role will involve lots of coding with some management sprinkled on top. Your main job is to build great software through your own efforts and the efforts of your team.

We are not looking for a rock star ninja unicorn sorceress code-crushing 100x developer-god. Real human beings only please.

This is an on-site position in American Fork, UT.

See more info and apply at https://yoursco.workable.com/jobs/431152.

What makes Elm + Phoenix so good together? I use Elm professionally and love it, but a back end is a back end. Is the love just "I really like Phoenix?" The way people talk about it makes it sound like it is uniquely suited to Elm, which I don't understand.

This is exactly the Same as Elm, without the type system to help you out.

You can usually edit the titles of your own bookmarks.

I've played with pocketsphinx.js a fair amount, but this looks WAAAAAAAAAY easier to set up and consume. Nice work.

https://www.npmjs.org/package/jsxhint is a drop-in replacement for jshint that supports jsx syntax.

This is the most honest comparisons of frameworks I have ever seen. It is really impressive to see Alex, who is on the Ember core team, speak about the strengths of React without straw-man arguments.

I'm working on a personal project, and I find myself struggling with some of the same problems.

1. No constraints. Since it is just me in my free time, no one can tell me what to do, but no one gives me feedback on what not to do. 2. No definition of success or failure. Am I creating a product that I want to exist, trying to polish my skills on the side, learn a new tech stack, or just goof around? Since I can just claim that it's a hobby project when it isn't going well (whatever "going well means"), I don't have anything holding me to a standard, since I haven't established it yet.

Any ideas on how to avoid aimless fiddling around on personal/hobby projects?

Glen gave an incredible presentation at Mountain West JS about his adventures doing cool things with gifs. He ended up with bpm syncing between gifs and music. You should definitely check out the talk when the videos get posted on Confreaks.