I don't think we're gravitating towards complexity. It's much simpler:
1. We add more functionality to the base of what exists (e.g. HTML). More and more individual features. (e.g. selecting things in the DOM, animations, effects, interactions, tracking state)
2. At some point someone takes all the patterns in the latest wave of functionality and writes a library for them. Library is widely lauded or adopted (see jquery, React).
3. We think of new features building on top what is now the new norm, it's now table stakes. Rinse and repeat.
This is a common pattern in engineering, for example writing new entries to a DB, then at some point going back and compacting.
> I'll never understand why tech companies choose some of the locations
That's because you've chosen not to read about it. Location is one of the most important things they think about for data centers and there are plenty of articles on the subject.
“We set out looking for a place where we could expand into gigawatts pretty quickly, and really get moving within that community on a large plot of land very quickly,” said Rachel Peterson, vice president of data centers for Meta. “We looked at finding very, very large contiguous plots of land that had access to the infrastructure that we need, the energy that we needed, and could move very, very quickly for us.”
To answer the question you're implying, surrounding temperature is pretty minor, the cooling required is orders of magnitude higher, so power access is more important; You'll frequently find them located near sources of energy.
Meta has defacto infinite money, they don't have to look for places where operation is cheap, but where they can be above the law as much as possible for doing whatever they want.
git log is probably good enough for 90% of folks :)
The main reason I wanted to build this is that git log doesn't give me context from GitHub PRs/issues/milestones or CI events. When I'm diving into a new codebase, I like to see who's been working on what, and what ongoing problems/initiatives are propelling that development.
I've only got GH issues up (not milestones or CI events yet), but I think this is a good start!
I feel like this is another case of throwing AI in a non-AI-required problem. Khan Academy itself just hired people to make its videos at a very reasonable wage. Why would you need to add AI into the equation? If you wanted to, you could build a platform of basic video / whiteboard content creators at a very reasonable price point.
> Humans could always write things down, but only the printing press changed the world.
No, humans couldn't always write things down (there was a whole lot of time that humanity existed and written language didn't), and writing things down changed the world quite a bit long before the printing press.
The reason why there's always a million reinventings of the todo wheel is because at its core, notes are just databases. A TODO form of note is about as flexible as Redis, and so the use-cases are many, from quick writes/reads (i.e. jotting down TODOs) to sortedset (i.e. priority list TODOs) to full task management (i.e. more data in the value), and everything inbetween.
In the same way we build around Redis for whatever tasks we need, you see engineers build around the concept of the note, complaining every other solution isn't exactly what they're using it for, and they're right, because on the other end is another engineer building for their niche use pattern.
By unpacking the use cases and slicing the right niches there might be a better notes app product somewhere, but I think it takes a very strong product person, not an engineer, to figure that out.
Yes, I’m beginning to get tired of these advert-blog posts, particularly those that don’t significantly advance the narrative beyond what’s already been discussed.
1. We add more functionality to the base of what exists (e.g. HTML). More and more individual features. (e.g. selecting things in the DOM, animations, effects, interactions, tracking state)
2. At some point someone takes all the patterns in the latest wave of functionality and writes a library for them. Library is widely lauded or adopted (see jquery, React).
3. We think of new features building on top what is now the new norm, it's now table stakes. Rinse and repeat.
This is a common pattern in engineering, for example writing new entries to a DB, then at some point going back and compacting.
reply