Mongoose

Not knowing what Chatto is, the headline is giving "zendaya is meechee"

Not to be a curmudgeon, but why are they spending time on this? As an enthusiastic Raycast user, I would prefer to see them focus on making Raycast better, not finding new ways to jump on the AI bandwagon.

I think this is less about the projects themselves and more about distribution channels like HN and ProductHunt being dead. When the zone is flooded by vibecoded apps of all kinds, the "build it and they will come" era of getting your thing on a popular website's homepage is over.

But other distribution strategies exist. You just have to be smarter about finding and getting in front of your core audience.

Quick, someone build a "documentation for agent teams" thing and call it Clawnfluence

Agent orchestration seems to be the new hot problem to be solved in the ecosystem. See also Steve Yegge's most recent posts [1]. Curious to see what tools emerge as the winners of the Cambrian explosion we're probably about to see.

[1] https://steve-yegge.medium.com/the-future-of-coding-agents-e...

I always liken it to using Uber in ~2012. It was fun to get around major metro areas for dirt cheap. But then prices rose dramatically over the next decade+ as the company was forced to wean itself off of VC subsidies.

I'd say Obsidian (just over five years old, since its first release), which is ironic because it's basically just a UI on top of text files.

Had me until claiming that InfluxDB was the first mainstream TSDB in 2013. OpenTSDB (2010)? Graphite (2008)? RRDtool (1999)?

Maybe Influx took off in a way these prior projects didn't, but people have been storing time series data for decades.

The conference has to be called Dreamyforce

Outside of electricity fundamentals, this book is a great intro on how the grid works: https://www.amazon.com/Electric-System-Nonelectrical-Profess...

Or a shorter alternative: https://www.ucsusa.org/resources/how-electricity-grid-works

Highly recommend A History of Modern Computing [1]. Starting with the ENIAC in the '40s through the successive generations of computing technology in the 20th century, it gives a fantastic overview of the field's history.

Sadly, now that I look into it, it looks like it's out of print. There are a few copies available on Amazon, so act now!

[1] https://mitpress.mit.edu/books/history-modern-computing

DNS and BIND, 5th Edition

I think this is a good question, but that it falls prey to the same conceit that befalls those who claim they could "build Twitter in a weekend". A picture-perfect sketch of a system can illustrate one's knowledge of patterns and off-the-shelf solutions, but it won't cover the things that get in the way of a team building their way towards product/market fit.

You could lead with this question and then jump in with hypothetical roadblocks to see how the candidate reacts.

Ex:

- "A network of microservices _would_ be a clean way to implement this. How would you foresee the operational burden of this impacting a small team?" - "Imagine that you build this and it works well, but the product it powers ends up not resonating with customers. The team now wants to pivot to X. What changes would you make to the system to address this new problem space?"

A former colleague of mine wrote a great article on this topic which summarized how the infrastructure group at Twitter thought/thinks about code review: http://glen.nu/ramblings/oncodereview.php

nothing

Is the redirect loop affecting your personal website the government's fault too?

https://twitter.com/search?q=%40ptshih&src=typd&mode=realtim...

I've come across tools that claim to expose and measure potential technical debt, such as techdebt.org or SQALE (http://www.sqale.org/details). I'd be skeptical of any software that claims to provide an automated mechanism for paying down debt. The consequences of debt are too varied and subtle to be generalizable.

UI nit: You should add placeholder text for the signup text input. The fact that it's intended to field email addresses may not be obvious to everyone.

Why is a YC- and angel-funded startup doing the Kickstarter dance?

http://www.wattvision.com/info/about

FWIW, al3x wrote the forward to that book in addition to the one that old_sound mentioned.

Zipkin -> Harpoon -> whale-killing

http://www.joeydevilla.com/wordpress/wp-content/uploads/2012...

Agreed. Was disheartened to read that the machine's primary use in the coming years will be to build JSF planes instead of infrastructure for new light rail networks.

I got in. Can't wait!

I'm curious how this will work with Play 2.0, which will be sbt-based.

Any links to example pages? They offer little-to-no info about what the pages actually look like. Why would I use this instead of GitHub?

Upvote if you spent at least a couple seconds trying to unhighlight the Feynman text.

Papalote.

http://www.yelp.com/biz/papalote-mexican-grill-san-francisco

I recently graduated with a CS degree and turned down an offer from Google in favor of one from Twitter, mainly on the grounds of it being a smaller company (for now). Google is still at the top of my list of BigCo's that I'd consider joining, as they have an incredible range of solid projects. However, my desire for a greater opportunity of individual contribution would prevent me from working there for the time being.

EDIT: Not to mention that Twitter (and many other software companies) is crawling with ex-Googlers, so the caliber of engineer coworkers will be roughly equal.

+1 for Being Geek. It's essentially a well-laid out rehash of Rands' blog posts over the years but I've found it good reading, even with the enormous amount of typos. I'm in the same situation as the OP, so the strategic career advice is much more relevant now than when I read it in the past.