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.

i.TV - New York City, Provo, Utah or remote

Us:

[i.TV](http://i.tv) is a growing second screen startup focusing on social television. Stuff we make:

* [tvtag](https://itunes.apple.com/us/app/tvtag-formerly-getglue/id377...), an iOS app that helps people have conversations about live tv.

* [Nintendo TVii](http://www.nintendo.com/wiiu/built-in-software#/tvii), the TV app on the WiiU. It is a single-page app that runs on the WiiU browser.

* [Optik Smart Remote](http://www.telus.com/tv/apps/optik-smart-remote/), an iOS and Android app for [Telus](http://telus.com). Basically the Comcast of Canada.

We have other fun things, like racks of servers processing live television to create and store thumbnails, tools to create games and other content around tv shows, etc.

We are a small-ish team of 13 engineers spread between Utah and New York. We communicate over team chat and screen-sharing to make remote people feel welcome. Our workflow is based around trust and helping developers be productive, which means flexible hours, remote friendly, loose vacation policy, whatever equipment you want among other things.

We are also still small enough that we don’t have tons of organized hierarchy, and passionate people can have a large impact on product, company culture, engineering practices, etc. We do 20% time, send people to conferences, and have Thursday brown bags to share things we learn. We aren’t perfect, but we try to make it a great place to be a developer.

Right now our backend architecture is lots of node.js, some Golang and a smattering of Python. MongoDB is our main data store, and we use RabbitMQ as a messaging layer. Our clients are built with iOS, Android, Angular, Backbone, and React among other things.

You:

We are looking for people that fit two main roles, but if you don’t quite fit but are still interested we are too!

1. Browser Engineer

* You know and love the browser platform

* You can use HTML, CSS and JS to build great experiences

* You have worked with one of the trillion browser MV-whatever frameworks

* You have experience with the modern web dev workflow (build tools, modular js, css transpilers, etc)

* You enjoy keeping up with the firehose of new developments in the web.

* You are willing to be taught and teach others

2. Senior Android Developer

* You have built Android apps you are proud of

* You have in-depth knowledge of Android platform

* You have experience creating/using custom views

* You have experience making responsive UIs that fit all screen sizes

If any of our tech stack or problem domain interests you and you don’t fall neatly in to one of these roles, talk to us anyway. We are always open to good people.

Email jamison@i.tv to get in touch.

Site looks great and congrats on the release.

This announcement suffers from the common problem of assuming readers already know what Ghost is. A few paragraphs down you mention Markdown and Jack Kerouac so I assume Ghost is related to text editing, but a sentence or two at the very top that explains Ghost would make this much better.

Again, congrats on the launch.

I'm familiar with Vivint's history. They are in the midst of an attempted transition towards becoming a tech company, partially to escape the terrible reputation they developed when they were APX.

The populations of Chicago, SF and Seattle are 2.7 million, 800,000 and 620,000 respectively. Provo's is 115,000 while Orem's is 95,000. It seems weird to compare the shopping and food options of some of the larger cities in the United States with Provo. Size-wise, it makes more sense to compare to something like Boulder.

I am biased since I am a local, but Utah Valley is on the cusp of recognition as a tech hotbed. Just in our office park in the corner of Provo, we have

  1. http://www.ancestry.com/
  2. http://www.qualtrics.com/
  3. us, http://i.tv
  4. http://www.moneydesktop.com/
  5. http://www.vivint.com/en/, recently bought for $2 billion[0]

There are also a bunch of other smaller tech companies.

http://www.domo.com/ and the Adobe campus are also about 10 minutes away, and there are various tech companies scattered all the way up through Salt Lake.

http://www.ng-conf.org/ is coming to SLC next year, and the local tech meetups are active and widely attended. Combine the good tech scene with the extremely low cost of living and it is a great place to be.

  0: http://seekingalpha.com/article/878211-blackstone-buys-vivint-what-you-need-to-know

Another (js-specific) one is [0]JavaScript Jabber. Full disclosure: I am one of the co-hosts of the show, but we usually have much smarter people come on and talk.

0: http://javascriptjabber.com

CompuCast[0] is by some folks at the University of Edinburgh. They cover mostly academic research, but do a good job of making it accessible for people with a basic background in CS.

0: http://computersciencepodcast.com/

Dota 2 has fantastic matchmaking, so it avoids the problem of total newbies playing with experienced players. Because there are over 100 different heroes to choose from, sometimes you end up with people who are very experienced at the game but completely new to their heroes though, which can be frustrating for them.

I agree. The article is a reasonable discussion of the differences between the two frameworks from the perspective of an experienced Ember user, and does a decent job illustrating why Robin prefers Ember.

The title is argumentative and inflammatory. I think lots of people will read the title on Twitter and roll their eyes at the Ember attack-marketing machine when the article itself contains some valuable points.

That is true with coin flips because the probability of a next coin toss coming up heads or tails is independent[0] of any previous coin tosses. Assuming you aren't spinning between turns, the probabilities are not independent anymore.

0: http://en.wikipedia.org/wiki/Independence_(probability_theor...