putnambr

From your link, a specific PAH called benzopyrene _may_ cause cancer in low amounts. It's a pretty extraordinary claim to say that we should be concerned about carcinogens from cooking with cast iron, which has been used long before our current high rates of cancer. I could see that being an argument against certain oils, but contrast that with the corresponding increase in cancer rates after the proliferation of teflon and PFAS in cookware/durable goods/clothing/lubcrication.

Did you skip over "In almost all applications of superconductors, they don't use high-temperature ones for one simple reason: Material properties."

They're saying that LHC does not use a ceramic, and therefore high-temperature, superconductor; instead they use metallic (cooled) superconductors because they can be molded.

Four hours of knowledge work a day is a lot?

Maybe I'm uniquely on a path to burnout, but I put in at least 6 hours of what I would call hard knowledge work per day as a SWE. Throw on 1-3 hours of collaboration and an hour of truly useless meetings and I'm at a 45+ hr week.

Factor in commute time, via bike so counts towards exercise minutes, and I'm working 50 hr weeks + 24/7 15 minute SLA on-call once every other month.

It's unfathomable to me that this isn't the average experience, and that anyone would get paid more than $120k doing any less.

I've got a side project still on Svelte 3, I feel this. I got the implementation into a good state a few months ago and haven't needed to touch it, soon it will be two major versions behind. No regrets, no other framework was as easy to work with for a primarily SSR app.

I was feeling this with Quarkus too, but they finally set one of their recent versions as LTS. Setting an LTS and migration guides between LTSs is a practice I'd like to see more in front-end tech.

This reminds me in a way of Java Cards / JCOP. It would be cool to see more people hack around on embedded systems, I'm all for stuff like this lowering the bar for entry. Cool!

> never clean it with soap.

This is a myth. I was struggling with getting a good non-stick-ability on my Lodge, until someone pointed out the 'patina' is really just burnt carbon and does nothing for non-stick. The non-stick seasoning comes from polymerized oils, which aren't affected by lye-free soaps. I haven't had any sticking issues since I've started washing my pan with soap after a messy meal and leaving a microscopic film of Crisco on after drying.

Or stainless steel, or BPA-free plastic, or plant-fiber cellulose plastic, or silicone, or...

How is it crazy? Jetbrains' IDEs provide more than enough value as it is. I don't want to pay for features like their collaborative coding or AI assistant that I won't use.

Would you rather them roll out cost-plus pricing or roll up the cost of new features into higher base prices?

I've only ever had this issue when using third-party syntax or bracket highlighters. Maven indexing, code analysis is blazingly fast.

Avoid resellers / 'cheap' registrars like NameCheap, GoDaddy. DNS propagation, domain 'locking', etc. is so much easier to manage and faster using registrars who care about their business. Hover comes to mind, recently I've transferred everything to CloudFlare.

Sure - the *Client would be a class or library intended for import/use by consumers of a resource exposed by a service. The exposed API should be viewed as usable independently, but it can sometimes be useful to add a layer of abstraction via a Client to would hold any logic required for interacting with a specific API.

Say you have an API that lets you bulk fetch an Item (`getItems(Collection<UUID> itemIds, int pageNumber, int pageSize)`), but the API enforces pagination and also requires authentication. A Client could require instantiation with whatever is required for authentication (`ic = new ItemClient(authToken)`), and provide a method to retrieve a huge list of Items without worrying about pagination (`ic.getItems(itemIds)`).

I assume titanium is better than stainless as far as leaching goes? With a quick search I could find titanium pots (actual titanium, not coated) up to 5L. I have a few on hand for backpacking, but I've never thought of using them for routine cooking... but this thread has got me thinking. I use cast iron for most purposes, but not for sauces or soups.

I can't imagine a stock pot size would be cheap.

Not OP, but I'd imagine the extra handling is the concern here, as far as water bottles go. You do want to refresh water in water jugs routinely as 'preservatives' like chlorine dissipate.

The better wording of 'stop reusing bottled water bottles' to avoid plastics would be 'use glass or metal water bottles'.

Soaps that don't include detergents are safe for cast iron, too. Many people confuse carbon and crud buildup for 'seasoning'. The seasoning you want is a micrometer-scale carbonized oil on the surface of the steel, and possible some excess carbon buildup to fill in any surface pores. A mild soap won't affect this, at all.

You can definitely damage a pan leaving it wet, so of course make sure to heat it up on the stove after washing and drying to cook off any remnants of water. I'll usually put on a very thin layer of Crisco if I've used soap.

PFAS have been phased out of use? Where? You have to hunt for PFAS-free ski or bike lubrication, it's in your contact lenses, and on all of your non-stick pans.

Fluorinated water has its own health risks, but everyone should absolutely be using either a fluoride toothpaste or fluoride rinse.

Is there any risk to the Quarkus project from Red Hat's involvement? It's been my go-to for Java webservices, but Red Hat's track record is making me consider something like Helidon.

My theory is that some middleware applications have policies to scale to zero or one based on traffic patterns, when scaled down due to lack of traffic things start breaking.

This is hearsay, but folks in Colorado tend to complain about federal air quality guidelines prohibiting controlled burns during the times of the year that it makes sense to do a controlled burn. During the winter, air quality guidelines dictate you can't exceed a certain amount of wood smoke in an area for example. NEPA studies might be another.

Definitely. We actually own three, the intent of the newer one is to replace the other two eventually.

Old cars are a Prius for interstate trips, and an early 2000s Outback for camping/interstate trips where we need to bring more things with. Prius got severely damaged in our parking lot and I used the insurance payout to help with a down payment on a Crosstrek, which will eventually replace the Outback as well.

I feel bad for taking up the (free) parking space, but the cost of ownership of the Outback when infrequently used is something like a $40 insurance premium every six months. That's another benefit of not driving much -- low mileage and safe driver insurance discounts.

In theory, yes, and a lot of lower income people do put that into practice and live in my same apartment complex. These people also usually own cars. The nearest grocery store is about a mile away, and the nearly bus stop is about the same distance. I occassionally bike to the store and have a bike trailer for groceries, but I have felt like I'm risking my life when carefully biking a trailer-full of groceries across the six lane 'street'.

Apart from Uber or hitching a ride from a friend, there's no good transportation option to our airport but I get your point. I think in most cases, given the option between a walkable (to work and restaurants) neighborhood and no car (and no good public transit), and suburbia with a car, most people would choose suburbia. Ease of getting groceries, ease of access to recreation, etc. What's really missing is the transit investment.

Rancher is going the way of dust? Most dev organizations I'm familiar with either use terraform + EKS + helm + pipeline, or replace a lot of that complexity with Fleet.

Uhh, no. Fed just needs to relax regulations around air quality, especially when the thing they're saying no to will improve air quality in the long run. I recreate on our federal lands and can't imagine the same access in state or private hands. State ownership inevitably leads to valuing extraction activities over recreation activities, if not just selling it to the highest bidder (Wilkes Brothers) directly.

I've purposefully chosen, and paid the higher rent for, an apartment that's on the greenbelt in my city and close to work so that I can use my car less. As a couple we still own two cars but really only use them to transport our dog to trailheads. The exercise pays dividends, and at just over two miles from work it takes maybe three minutes longer getting to work than driving to a parking garage.

I feel fortunate to make enough money to easily afford the rent, but it's insane that in most places you need a high paying job to escape needing a car. Refugee and low-income housing here is clustered around major streets like six-lane one-way transport corridors. Unless they work downtown or close to a stop on one of the few bus lines that run frequently and reliably, they need cars. Usually the cheapest they can afford, which likely means they need to spend money they don't have to get them passing emissions tests at registration time, deal with breakdowns, high insurance premiums, etc.

It doesn't help that most of the planned transit improvements seemingly are focused on greenification of buses rather than just getting more buses on the road to expand routes, make lines frequent enough to use for commuting, etc.

My city did pass some new zoning codes which heavily cut back on parking requirements, I'm excited to see how that (slowly) pans out. I expect more high-capacity parking structures to go up, fewer surface lots. People might need to walk further or explore other last-mile options, I have hope that will turn people's eyes towards non-vehicle transportation improvements.

Without prescribed burns it's only a matter of time until we experience another 'Big Blow Up' - https://en.wikipedia.org/wiki/Great_Fire_of_1910

It's not Colorado's land to burn, though. Most of the issue is fuels load on federally-managed land.

Really? You think someone who spends all day building systems with software will have an easy time studying and gaining a CDL, learning about soil quality, drainage, fertilization, crop strategies, financing agreements (lease to own agreements, commodities futures, even forex), working with hired labor and managing contractors, engine repair and small scale fabrication? I think the farmer would undoubtedly get bored of being cooped up inside all day at a computer, but they wouldn't have a hard time understanding how to create a system from small moving pieces that they can direct.

Paying attention to the design paradigms is truly the interesting aspect. The way you write code in a language isn't fixed or proscribed. You see evolution of languages/frameworks, influence between them, repeats of what one tech has tried and failed (sometimes the new tech tries again and succeeds). The great thing is you can take those learnings back to the language you're using! If you mess around with some Angular or RxJS front-end stuff, you can take that style to the back-end if you want. If you've seen benefit from strong typing on the back-end, you can add TypeScript to a front-end project. Rust and Kotlin have even influenced Java core libraries for the better.

By paying attention to the designs it's easier to figure out what's marketing-driven hype as well. For example, do I really need to jump onto the next serverless platform, or are they just repackaging and upselling AWS Compute resources? Can I accomplish the same thing as the latest edge computing platform by using service workers and a free CDN? Is Firebase Hosting basically a second interface for GCP Cloud Run?

Been doing this for a few years. If I have an `Item` class, it's going into its own package. Along with `ItemService` (business logic), `ItemResource` (endpoint), `ItemDao` (persistence interface), etc. If `Widget` has a dependency on `Item`, then `WidgetService can either import `ItemClient` or roll its own.

Makes it super easy to split out microservices when the monolith gets big. Just keep from injecting one Service class into another, rely on the Resource or Client instead.

I think it's fair to point out that you should be referencing road bikes then when you say bikes are not practical. Advancements in tubeless technology, suspension, MTB groupsets with dinner plate low gears, derailleur clutches, and hubs/rims designed to take a beating while supporting wide tires can definitely make a bike more efficient than walking on most terrain.

- Fat bikes are more efficient than snowshoeing or breaking trail on XC skis.

- CX bikes are more efficient than walking in mud.

- Fatter tire gravel bikes are more efficient than hiking through sand.

- A bike with a 51T cog and 28T ring will be more efficient than hiking up steep grades until balance at low speed becomes an issue.