Can someone with knowledge comment if charging a battery this way will significantly decrease its longevity? I remember reading that charging with a low current is advisable to preserve battery health.

According to the article: Its latest refrigerant cooling system helps deliver a 35 percent gain in high-temperature lifespan, ensuring that megawatt charging won’t degrade the battery.

Recharging is at some level an issue with current delivery, not just the chemistry. EV batteries are massive arrays of individual cells, so a lot of recharging problems is having the wiring to deliver the current to the batteries optimally.

Then, some chemistries/designs have better cycle endurance, some can probably recharge faster at given depletion levels. When charging an almost totally discharged battery, there's lots of "slots" for the incoming charge to fill, but as it fills up, it will inevitably take more time to locate a "slot" to occupy.

Solid state and semi-solid state may be at play here, since a solid state battery is theoretically more durable as well.

Or, to your point, it is a marketing stunt that doesn't care about cycle endurance. How would we tell? Battery reporting is still horrendous at delineating the tradeoffs/limitations per https://news.ycombinator.com/item?id=28025930 but hoping that mainstream media don't "gee whiz" science and technology reporting is simply not going to happen, especially in the clickbait era.

A good rule of thumbs with most battery chemistries is that they tend to not like both extremes. This is true for temperature, charge capacity, slightly less true for charging current as very low current tend not to degrade the battery.

Try consulting. Once your reach Senior Consultant level it's pretty much the end of the path for ICs.

So that brings a question. Let's say you're consultant (and the only senior consultants where I work are salesmen), and you're 42. How do you advance while remaining technical? I don't mind very occasional sales efforts, but not constantly.

I imagine it would be sufficient to show that he had to spend time or money analyzing the security impact of the event.

If a company pays peanuts it can have a job opening for much longer than 3 months.

They are not awful if you use right tools. Welcome to the world of Spark, Apache Drill, Trino/Presto, etc.

paywalled

I know it doesn’t solve the problem for everyone, but many public libraries offer free access to Consumer Reports.

Testing products costs a lot of money.

Especially expensive physical products that you want to review without bias.

The guy is a chair at the Women's Flat Track Roller Derby Association and previously worked at a cannabis company. Interesting career change.

Software's software ;)

Is it because of cognitive load? I briefly looked at your project, and I'm still not convinced that your solution is easier to comprehend than

function onLoginClick() { validateFields(); networkLogin(); updateUI(); }

I think you are absolutely correct. In this simple example, it's not easier to comprehend. Especially for someone who already understands how composing software out of function calls works.

My goal with that example was to point out how there are implicit dependencies between validateFields() and networkLogin() and updateUI(). They need to be called in the correct order to make the program work. Our library makes those dependencies explicit and calls things for you. It's not a big deal when we have a 3 function program. But when we have dozens or hundreds of interdependent instances of state, those implicit dependencies become a real struggle to navigate.

Now we're convinced our library works well. We use it every day. But it's also very reasonable for you to be skeptical. As you say, there's cognitive load. As a potential user, you would need to spend your time to read the docs, try a few out ideas, and understand the tradeoffs. That's a lot of work.

I'm glad you took a look at the project, though. The fact that we've failed to make a case for it is certainly on us. Which gets back to my original point. I don't know how to sell a solution to complexity.

Sedentary lifestyle?

Possibly. But my personal unsubstantiated pet theory is nicotine and alcohol.

Consumption of both of those dropped right as the obesity epidemic picked up.

Nicotine is a known appetite suppressant. Alcoholics are known to have terrifically clean arteries (at the cost of liver disease).

It would be great to add location and role filters.

Thanks for the suggestion! It's on my todo list. For now, you at least can sort jobs by similarity to a selected job. It's the middle icon to the left of each entry (maybe not the most intuitive way how to do it, though).

wow, that is both very neat and hard to find