m1keil

> I learned a ton from my DE. Like, really, a ton. Before that, I had been writing on various blogs for about a decade, but writing online is all about being direct because most people don’t have time. With a book, it’s different. People made a deliberate decision to buy your book. Now, it’s your job to bring them somewhere valuable. And if that takes time (meaning more words), so be it.

I have a hard time with this point. It feels to me like a lot of books have A LOT of unecassery padding all over the place.

The example of taking 28 words and turning it to 120 is pretty good at showing this. The first paragraph is totally pointless - we are reading a book about 100 most common mistakes, obviously this mistake is very common, how did this increased the value?

Then we have another line that explaining what happens in the code, which is totally useless because the code is super trivial.

Then the code, with more explanations on the side as if the previous line was not clear.

And only after that we get to the crux of the issue.

I understand that book publishers feel they need to justify the price of a book by reaching the 300p mark in some or other way, but in my way this only makes the book worse.

ctrl+r with fzf and zoxide for quick dir jumping is all I need in the shell nowadays.

Hey on a personal note, dealing with you and your team on Nomad's GitHub issue tracker was always a good experience. I hope nomad still has a future under IBM's roof.

That's pretty useful. I think yt itself is experimenting with similar feature as I see some videos have AI summaries in the official app.

If you are at the point of having to deal with individual servers and have a very fast-paced development (startup), or have to deal with very burstable traffic spikes (say e-commerce), cloud is probably your friend.

But sometimes you just need more compute and you are the type of organization that buys compute by the floor space and power consumption...

Regardless of the nuances of each situation, I think jsiepkes's comment meant to say that in the data center you can buy pretty killer hardware that will be totally overkill for the moment and won't require you to count active timeseries in order to not pay $300k a month for your metrics, and at the same time will last you for the next couple of years.

Also, for most companies, the next point of inflection will never come and this server will probably last them for a very, very long time.

I'm sharing my point of view as someone who works at an organization that took money as the only consideration and managed to grow over the years to now having to start taking both time and money into consideration because taking only money into consideration proves to be too expensive.

Maybe I'm misreading what you mean, but I don't understand why it's not solving problems. Lack of capactiy solved buy buying more hardware or replacing existing hardware with more powerful hardware. In the datacenter you need to have capacity planning pretty early on, while in the cloud you can get by until reaching very large cloud bill.

I also don't think that every organisation that needs file storage must build a storage solution that should compete the reliabiltiy and features of S3. Most of the times you can get by just fine at fraction of the cost.

FinOps isn't even new (my definition of new is "once you have an O'Reilly book on the topic it is not new anymore").

You can't spend more fast, but you can always spend more.

What levels of observability did you have for costs of data transfer and how did you do it?

So next time someone says "in cloud you don't need anyone to manage it for you" you can link them this article.

So Sudo password for example seem to be up there.

I started using python at around 2.6/2.7, and while it was easy to install python on windows, anything that involved non pure python was a nightmare.

Back in these days you had no wheels and I think it was at least a partial reason for why conda was a thing.

I don't know if it's higher quality, but kinesis recently released the mWave https://kinesis-ergo.com/shop/mwave/

Ghostty supports it (like many other terminals) - it is called shell integration and it is supposed to be enabled by default, just like in Terminal.app.

I really like to copy on select in the terminal. Terminal.app used to have a hack available to add this feature in, but since SIP days, it is no longer possible.

So what happens if you leave tomorrow? Will your team be able to pick up where you left off?

I'm not making an argument against the cloud here. Not saying you should move out. The reason why I call out cloud infrastructure specifically is because of how easy it is to let the costs get away from you in the cloud. This is a common thread in every company that uses the cloud. There is a huge amount of waste. And this company's story isn't different.

By the way, 8 DevOps engineers with $150k/year cloud bill deserves to be highlighted here. This is a very high amount of staff dedicated to a relatively small infrastructure setup in an industry that keeps saying "cloud will manage that for you."

I agree with you. I'm not advocating for hyper cost optimization at an early stage startup. You probably don't need k8s to get your mvp out of the door either.

How to save 1M off your cloud infra? Start from a 2M bill.

That's how I see most of these projects. You create a massively expensive infra because webscale, then 3 years down the road you (or someone else) gets to rebuild it 10x cheaper. You get to write two blog posts, one for using $tech and one for migrating off $tech. A line in the cv and a promotion.

But kudos for them for managing to stop the snowball and actually reverting course. Most places wouldn't dare because of sunken costs.

This is all really cool, but I just want soft wrap to be fixed

Interesting. When I read "A as b", I read it as "A (represented) as B".

Software as a service. Infrastructure as code. Diagram as code.

Also https://github.com/newmarcel/KeepingYouAwake

Can you give a ballpark figure of what scale you have in mind?

No, what you are describing is diagram to code ^_^

Maybe somebody knows: is it possible to exit Vimium's insert mode with any key other than ESC? Exiting full screen video on YouTube requires ESC as well.

I think the reason is clear - they suspect that there might be still devices in circulation that didn't go off and can risk a flight.

This is similar to the spontaneous igniting Samsung devices story from few years ago.

In a way, VSC is the same model like Android. You can use it without its corporate backer, but severely limit its functionality in the process.

so we should stop making blog posts about anything that is hard/custom/outside of the blessed path?

Came here to say that I really like the content on your YouTube channel.

All this effort, metrics, measuring impact, performance reviews, blah blah blah. You want to make sure your engineers paid top dollar? Tell them to go interview in other places. If you truely value them - beat whatever they were offered by X%.