eestrada

Here are the generated docs. I tried to be thorough with these right from the beginning too.

https://rubydoc.info/gems/async_futures

https://rubydoc.info/gems/async_futures/index

That's pretty much true of HTMX too (which is what GP mentions using). I mention Hotwire Native (different from plain Hotwire) because it makes it easy to wrap a web app as a mobile app. Then you can replace performance critical parts with native views, but keep everything else working through the web app portion. This is easier to maintain, albeit with the downside that everything requires network round trips. Depending on you use case, that may be an acceptable tradeoff.

Can't vouch for it's effectiveness, but Hotwire Native might meet the needs for mobile paired with plain HTML. Despite the name, it doesn't seem that using Hotwire for the web UI is necessary to use Hotwire Native. I could be wrong about that though.

https://native.hotwired.dev/

Time to invest in a small Faraday bag to keep in the car.

There was a hidden benefit in the old way: it avoided people making effort for things that weren't important. It took effort to make signal cut through noise. When it was low effort, it was obvious it was just noise and could easily be ignored.

Now low effort noise can masquerade as high effort signal, drowning out the signal for things that actually matter.

Direct relationships of trust matter more than ever now. You can't just trust that if something looks high effort that it actually is. You need to know the person producing it and know how they approach work and how they treat you personally. Do they cut corners all the time or only for reasons they clearly communicate? Do they value high quality work? Do they respect your time?

I haven't had to deal with this in open source, but I have had to deal with coworkers posting slop for code reviews where I am the assigned reviewer.

I've noticed that slop code has certain tell tale markers (such as import statements being moved for no discernible reason). No sane human does things like this. I call this "the sixth finger of code." It's important to look for these signs as soon as possible.

Once one is spotted, you can generally stop reading; you are wasting your time since the code will be confusing and the code "creator" doesn't understand the code any better than you do. Any comments you post to correct the code will just be fed into an LLM to generate another round of slop.

In these situations, effort has not been saved by using an LLM; it has at best been shifted. Most likely it has been both shifted and inflated, and you bear the increased cost as the reviewer.

Although I'm not wild about the new `io` parameter popping up everywhere, I love the fact that it allows multiple implementations (thread based, fiber based, etc.) and avoids forcing the user to know and/or care about the implementation, much like the Allocator interface.

Overall, I think it's a win. Especially if there is a stdlib implementation that is a no overhead, bogstock, synchronous, blocking io implementation. It follows the "don't pay for things you don't use" attitude of the rest of zig.

The best anti malware on any version of windows has always been to not run windows.

I bring up raw milk because it is minimally processed (I don't even consume it personally). I used it as an example because it shows how much plastic is embedded in the food chain and ecosystem by looking at one of the least processed items on the list.

The most disturbing is "Raw Cow Milk from Farm in Glass". It still is loaded with plastic, even though it is one of the least processed things on the list.

My only question is was the cow milked by hand or by machine? The tubing in a milking machine almost certainly contains plastic.

https://www.plasticlist.org/product/29

I use it on my own docs to remove extraneous details. I often write too many words in early drafts and LLMs summarize my writing faster than I can (although I don't know if they do it better than I would/could).

Then the next version of my doc becomes the summarization, and I only flesh out details where the summarization went too far and removed critical details.

And that increase in LLM usage has resulted in an enormous increase of code duplications and code churn in said open source projects. Any benefit from new features implemented by LLMs is being offset by the tech debt caused by duplication and the maintenance burden of constantly reverting bad code (i.e. churn).

https://arc.dev/talent-blog/impact-of-ai-on-code/

In light of this, employee referrals and in person interviews should become increasingly important.

Sadly, most corporate executives will learn the wrong lessons from this and instead use this as an opportunity to push RTO even more.

I mostly like Vim because it is available everywhere and in the terminal. In its default configuration it isn't the most powerful IDE, but it is vastly more powerful that any other default experience in any other text editor (IMO). It also makes it trivially easy to shell out to external tools for modifying the text, so even for a set up that isn't heavily riced you can still do a ton.

Even when I'm forced to use another IDE for work, I try to find Vim keybindings ASAP. I like that I can learn Vim motions and actions once and use them in nearly every IDE.

My understanding is that TIOBE is primarily based on number of search engine results. Other results like number of active (a commit within the last 6-12 months) open source repos or number of new repos in a given language are other metrics worth considering. The project you linked seems to be one like this.

A high search rate doesn't necessarily mean high rate of real world usage. Correlating across multiple metrics would be a better way to measure popularity.

Although popularity itself may still be a weak signal depending on your purposes.

I miss the old internet. I'm pretty sure anyone old enough to have experienced it misses it.

I had one job at a pinball company where my coworkers and I didn't get paid for a couple months. I quickly found work elsewhere. Thankfulfully my backpay did eventually come, but I wasn't going to stick around to see if they would be good to their word again the next time funds dried up. I heard this was a recurring problem even before I was hired on.

Later some of my coworkers sent an article to me mentioning that the owner was under investigation by the SEC for (allegedly) embezzling funds from investors. I think I figured out where everyone's paychecks were going.

I tried AI code completion via Amazon Q. I quickly turned it off; half the suggestions were noise that took more time to review than actually writing it myself.

The one good use I have found is using it to tighten up my writing in design documents. I tend to use too many words to describe things. I use an LLM as a type of prose compressor on my documents. I need to re-read it afterward and make minor corrections, but it still saves me time since summarising my own writing takes much more time and energy.

That is the only net win I've had with LLMs so far.

I tried graveyards and swing shifts in my twenties. I only did it for a year, but it wrecked my sleep schedule for years afterward; I struggled with insomnia because of it. Not sure there is any age where this works.

Some people can handle it better than others. I'll never do it again though.

Good point. That sounds about right.

I think paid oncall could work if oncall is voluntary. The more oncall sucks, the less likely team members are to volunteer because the pay isn't worth it, then the company/team needs to pay more as an incentive to get people to volunteer for oncall. Eventually the price is so high that it becomes cheaper to just build the system correctly and stop shoehorning features in with no regard for stability.

If oncall burden is light, then everyone volunteers because it is an easy way to make a bit of money.

However, it is a huge systemic change to move towards a voluntary model. Not sure how feasible this really is.

Not a dishwasher story, but related. We bought a whirlpool washer and dryer set and hated them. The set was one of the few name brand models without WiFi "features" added on. But they were still terrible.

The one highlight is that we learned about the brand Speed Queen from the sales person at Lowe's. She talked them up as being the best, but they aren't sold at any big box store. Speed Queen is only sold through mom and pop shops.

When we dug in and did some research, we found that Speed Queen has the best consumer ratings by a wide margin.

They still produce a fixed drum model for the washer, like the type that whirlpool and maytag used to make decades ago. We put up with the whirlpool for a couple of years, but when we moved we got rid of them and bought a fixed drum style Speed Queen (look for the models marketed as "classic clean"). Best consumer appliance I've ever owned. I expect it to last at least another 20 years.

It is mentioned in the article, but then quickly dismissed: people seeking income via creating new businesses after being laid off during the lockdowns.

I think there is a secondary effect here. Many people remember how many jobs were deemed "non-essential" and how many people were laid off. Building your own business is one way to insulate oneself from this.

I think some amount of continued momentum is people preparing for the next time government overeach interferes with their ability to feed and house themselves and their families.

I neither approve nor disapprove of this message.

My (poor) understanding of quaternions is they are like a vector with a rotation angle around the axis of the vector. This is probably incorrect on many levels. But it was a simple enough explanation that it made sense to my brain why this would work better than simple SRT transform parameters for avoiding gimbal lock. It's been several years since I needed to deal with 3D transformations of any sort, so I'm a bit rusty on all this.

In the USA, corporations just do stock splits or run a corporate vote to issue more shares. Also many large tech companies use stock as total compensation for employees, so the "selling" of stock can be indirect as a form of revenue. Instead of paying employees cash, they pay in stock, which frees up more cash for other things. Thus they don't need to have as high of true revenue margins to pay employees well. Big corporations understand that a lot of paper value is fungible one way or another.

I apologize for not being clear in my comment. None of my musing was meant to allude to public policy or law. It was about what an individual (or group of individuals) could choose to do with a corporation to avoid perverse incentives in the future. I'm not really interested in directly enforcing anything.

To make a play on an old programming joke:

Once there was an individual who noticed there was a problem with society. He said to himself "I'll use the State to change things!" Now there were two problems.

Specular higlights are view dependent and the specular higlights seem to react properly when tumbling the virtual camera. It seems reasonable that it would be possible to do a reverse calculation to determine the location and intensity of light sources in a scanned scene. Once those are determined, they can be extracted from the scene and made global light objects in a scene in a DCC app or game engine. More than likely it would just be baked as one big IBL dome light.

I could be wrong about all of that though.

> Epic is privately held, Valve is too, Unity is not and we ended up here. I think that says a lot.

I've been thinking a lot about private versus public companies. Most of my favorite products come out of privately held companies. There is something about the incentives for publicly traded companies that encourages them to make poor choices. I think it is because there are effectively two forms of revenue: selling products/services and selling stock. And those two things often conflict with eachother to the detriment of the customer. However, with a privately held company, the loyalty is primarily to the customer. Thus the products are better because they need to be to keep the company afloat.

I don't think that means that public companies shouldn't exist, but I wonder how an individual can structure their publicly traded company to avoid having the company misalign its incentives with those of the actual paying customer.

My current theory is to focus more on revenue sharing instead of stock price. For example, dividend stocks. I don't think it completely solves the problem, but it at least moves things in the right direction.

I remember hearing from my mother about how her grandmother (my great grandmother) got her chinaset. It was during the great depression, and some flour companies held long running promotions where a piece of China would be placed inside the bag of flour. If you ended up with too many pieces of one type (for example tea cups), you could trade with your neigbors to equal out your set. It was a way of buying/owning something nice when you barely had money to pay for the food itself. I'm not sure how apocryphal this story is though. Could the China really have survived transport that way? Maybe the purchaser redeemed the China piece another way.

They would also use the bag the flour came in as material to make underwear. Literally nothing was wasted. That is probably also why this stuff got passed down to our generation: they couldn't bear to part with anything.