move-on-by

I must disagree. I normally clean my fans before switching spin directions. Our living room doesn’t get good circulation compared to the rest of the house and so the fan is on a low setting pretty much 24/7. I was thinking the same as you, it’s been moving like non stop since last time I switched directions, how much could have collected? A lot apparently. Once it stopped and I switched directions and turned it back on- dust went everywhere. I had to vacuum the entire room and couches. Learn from my mistake. Moving fan blades does not mean clean fan blades.

I never really thought much of any vacuum I’ve ever own until I got a shark one. It picks everything, to the point where you have to be extra careful you don’t vacuum over things you don’t want to be sucked up into the vacuum. It makes total sense, who needs such powerful suction when you can instead just put a roller on the floor to pick things up. Never going back to a suction-only vacuum.

I read Atlas Shrugged recently. I went in not knowing anything about the book or author. I liked it for maybe half way through and despised it by the end. Reading about the author after finishing the book, it had a lot of her personality in it.

Just one more data point but this is what I’m seeing too. The extreme ‘ruthless’ prioritization has stopped and devs (who want it) have breathing room to make the enhancements they’ve been wanting all along. Turns out what is good for AI is also good for regular old school SDLC. All you have to do is say it will make AI more effective.

> One caveat: my experience comes mainly from working on infrastructure and developer tools at large companies, on teams where engineers have a lot of bottom-up autonomy to influence their roadmaps. In a more top-down environment, there may simply be less room to work this way. This is a big caveat. I too, regularly find a fix problems that need to be solved. Very occasionally, something big blows up, and I already have a solution in progress. Those are curious, because it reinforces that I’m working on the right things, but also that I was too slow. Other times I fix things that never became a major issue. Is it because I fixed it in time? Or was it never going to be an issue? Anyways, I’m a staff engineer, so I guess I’ve been able to demonstrate my usefulness well enough, but it’s a constant struggle. The new product features and support for new partners is what gets all the glory. At the end of the day I suppose that it is right for the glory to go to them. It’s important for the business to gain new business and market advantages. I really enjoy ‘greasing the squeaky wheel’ and generally making things run as smooth as possible. Depending on your leadership, this might not be the type of ‘staff engineer’ they are looking for.

I can’t say I know much about kernels, but what you say rings true. It’s not unlike the micro service vs monolith argument. It depends on the use cases, but in a system where the micro services depend on each other, all you have is a distributed monolith. All the complexity and overhead, and none of the benefits. Keep dependencies close.

With any ORM, N+1 queries can be major performance problem. They can be a bit tricky to identify because individually the queries are fast, but when you execute N of them per request, it adds up. It’s worth looking at. You can write units tests that assert the number of actual SQL statements get executed for a given function. N+1 isn’t just a database issue either. I’ve seen N+1 at the cache level too with Redis. The cache layer supports ‘get_many’ and ‘set_many’. I haven’t stood up a ‘fresh’ Django app in ages, but some things I remember are worth looking at:

* compression middleware like gzip. There is a big scary warning on this, but modern Django has mitigations in place

* how your DB connections are managed and reuse them- I think Django even supports a DB connection pool these days

* serve static assets directly - skip hitting Django for anything that isn’t dynamic

This is just one of the many reasons I don't have the disposition to be in sales

I remember sitting in on a sales meeting early in my career. I kept quiet, but afterwards I complained to my manager that they were selling features that didn’t exist and conflicted with core concepts of the product. My manager told me that was how sales were made. I left the company not long after, I was already disgruntled prior to that discussion.

I’ve seen the same thing everywhere I go. I don’t have the disposition to be in sales, but I periodically daydream of making huge commissions by straight up bullshitting people. There seems to be no downside.

I don’t have great hearing, so I’m not sure I can really weigh in here (thanks punk concerts in my teens). I remember similar arguments around screens and 60Hz vs ‘the human eye’. I think a lot of people, myself included, can easily perceive the difference between 60Hz and something higher- given the right conditions. I would not be so quick to disregard claims of more sensitive hearing.

Ah yes, totally secure. I’m sure there will be no unforeseen problems or bypasses.

I’ve been very involved with the DNS blocking scene- and it’s extremely easy to circumvent. I always wonder if there are some principled nerds on the architecture side purposely designing things to be easily blocked with DNS blocking. Or perhaps the mercenary nerds are just that inept. Maybe a mix. I also don’t think the numbers of users with DNS blocking are large enough for the mercenary nerds to care about. However, the math for LoE to bypass DNS blocking has certainly changed recently.

I doubt the ‘average consumer’ is even using a password manager, let alone going to change their password because of something so common place as it being compromised.

It’s been a little over a week since ‘An update on GitHub availability’

> Our priorities are clear: availability first, then capacity, then new features.

Let’s see how long it takes them to turn this ship around.

My experience is not much different then what you listed, except I discussed programming with my math teacher. She said as long as I was the one who programmed it, and that I didn’t share the program with anyone else, the I could use it.

Looking back on that experience, I’m very grateful to her, but she also probably didn’t realize I was programming it to also show the individual ‘steps’ to get the solution instead of just the solution.