jakemcc's profile picture. Software developer, technical leader, clojure expert, sailor, and rock climber.

Jake McCrary

@jakemcc

Software developer, technical leader, clojure expert, sailor, and rock climber.

I recently read Vernor Vinge's A Deepness in the Sky and it made me think about the AI tools many of us are interacting with. Thoughts here jakemccrary.com/blog/humans-as…


New test-refresh 0.26.0 now released. Stop running your Clojure tests by hand, let computers do it. Now it supports - Reloading but not running tests - Clearing terminal between test runs - Custom banners Details in the PR that added the features: github.com/jakemcc/test-r…


Jake McCrary reposted

"Please acknowledge" is the saddest email subject


Jake McCrary reposted

That is if you want high speed, you must build high quality systems. If you want high quality systems, you must build them quickly as a series of small changes. This is what the data says, and when you stop and think about this, the reasons are pretty clear. 11/17


Jake McCrary reposted

i trained an ai chatbot on my childhood journal entries - so that i could engage in real-time dialogue with my "inner child" some reflections below:


Jake McCrary reposted

Weekend reminder that SimCity's creators couldn't accurately reflect the scale of urban parking lots because if they did the game fell apart. theatlantic.com/technology/arc…

DavidZipper's tweet image. Weekend reminder that SimCity's creators couldn't accurately reflect the scale of urban parking lots because if they did the game fell apart.

theatlantic.com/technology/arc…

I wrote a barely technical article on using bookmarklets in your mobile browser. Learning about this earlier this year has made using a phone browser much nicer. jakemccrary.com/blog/2022/11/1…


As someone that reads papers sometimes, this is exciting whitehouse.gov/ostp/news-upda…


Jake McCrary reposted

whenever i have to debug a node.js app, my first thought is never, “i’m so glad they were able to write this quickly”


Jake McCrary reposted

What if we stopped saying "Technical Debt" and talked about the actual thing? Is it an escaped defect, infrastructure upgrade, shoddy code..? Builders don't have "structural debt", surgeons "surgical debt", or gardeners "botanical debt". #agile


Jake McCrary reposted

That about sums up what I know about pair programming. Also, the things you label as “weird” are the most strategically important.

Extreme Programming Explained by @KentBeck is basically the bible for teams that pair program. Its reputation is well-deserved. Even though helped popularize the idea of pairing, it actually only has two pages on the subject! You'll probably be surprised by what it says:



Jake McCrary reposted

GeePaw provides context for why TDD hasn't yet had the impact it could.

Extreme Programming Explained by @KentBeck is basically the bible for teams that pair program. Its reputation is well-deserved. Even though helped popularize the idea of pairing, it actually only has two pages on the subject! You'll probably be surprised by what it says:



Jake McCrary reposted

Reminder that computers exist only to serve us. Every time we wait for a computer, the computer is the one who is wrong.


Like listening to mellow tunes and watching someone play Magic? Catch my brother streaming over on twitch twitch.tv/mxmastr


New York followers, go do some trivia with my friend and 2x jeopardy champion @MattLMattL

I'm making my trivia host debut next week! If you're in NYC, grab some friends and come on down to Gowanus--the tentacles are not guaranteed, but the fun is!



Old coworker of mine was part of a small team that put out radiopaper.com . Pretty looking site and an interesting idea. Looking forward to giving it a shot radiopaper.com/JakeMcCrary


Jake McCrary reposted

every software engineer's dream is to get rich, buy that goat farm in the country, and then retire to the server room in the basement of the goat farm so they can actually finally write code


Jake McCrary reposted

In 1999, a little book by @KentBeck started explaining Extreme Programming (XP) to the masses. 23 years later, it's still true to every word. But we, the developers, chose to ignore half of its learnings. In this thread 🧵I'll fix that for you. 👇👇👇

ekapic's tweet image. In 1999, a little book by @KentBeck started explaining Extreme Programming (XP) to the masses.

23 years later, it's still true to every word.

But we, the developers, chose to ignore half of its learnings. 

In this thread 🧵I'll fix that for you. 👇👇👇

United States Trends

Loading...

Something went wrong.


Something went wrong.