lkois

You left out the extra grid power needed to move these things. Which negates some of the gaz guzzling benefit, if more people move up to heavier vehicles. Which they are, apparently half of the pre-orders have come from people who never owned a truck before.

It's interesting to note that these more "environmental" EVs are resuscitating Hummer, which was already killed off for being a gas guzzler

Calibre is good for library management, but for simply adding the odd book I've found it surprisingly easy to simply direct download a .mobi from any easily googled website and email the file to my kindle email address.

This obviously feels very sketchy, not only because you might be including Amazon in some very transparent piracy, but because it works TOO well. By which I mean, these files aren't simply added to your device, but to your Amazon library; these are then readily available OTA to all devices you own and any you add later.

>Stranger things is more like nostalgia for early 2000s 80s nostalgia.

Vaporwave music and all the visual design around it embraces this pretty hard. If a clip isn't literally set to 80s commercials it's at least full of VHS distortion effects.

Half the comments on any video seem to be teenagers talking about nostalgia for a time they never experienced

My phone (Huawei) has a charging animation with rising bubbles (flowing from the cable into the phone). The speed of the bubbles reflects the charge speed. If I use the original charger (and cable) it says "fast charging", the animation is very quick, and it shows the battery level rapidly rising in 0.01% increments. It's pretty neat.

Except that if it's not on that fast charger, the only speed indicator is the damn bubbles, so I gotta watch for a few seconds and guess if it's faster or slower than other bubble animations I've seen in the past. Every other charger in the house has been a mystery for the last 2 years.

I've recently picked up a couple of 65w GAN chargers which seem nicely compact and powerful enough to be the only chargers I use for everything from now on and never think about this nonsense again.

I had some of that too though, that's kinda the idea. I found carby foods were most consistently weight adding, while meaty and fatty not so much.

I recall all you can eat bbqs actually resulting in weight loss the following day. But if I had a bowl of rice with them, I'd have the weight gain I feared. Moderate portions of Indian takeaway curries with Naan could keep my weight up for a few days.

That's not something I'd expect from pure calorie counting, nor do I understand what's actually going on or if it's good or bad etc. But it seemed useful to be aware of

The real takeaway about mass loss via carbon dioxide is that you're changing how the engine works, and you're unlikely to notice it.

Get a digital scale, weigh every morning after toilet. I find there is a very quick and variable response to the previous days food, which can be quite motivating. Seeing it up or down half a kilo each day is very noticeable, and informative about what works and what doesn't.

Eat less dense calories, try to move around a little bit, all there is to it. My general rule is: -2 small meals = weight loss -1 regular/big + 1 small = maintain -2 big = weight gain

Once you stop trying to bloat yourself all the time, it starts to feel nuts how frequently you did

Sure but modern stools are designed to break to make you buy another, so you'll save money in the long run. They don't make them like that anymore. You'll be able to pass it down to your grandkids one day.

Haha yea I did. Though he even acknowledged that if he wasn't quitting, I'd have had a grumpy coworker instead of any training.

He was quite diligent about taking regular and appropriate breaks. Partly in response to having worked through too many lunches prior.

Brain sag still occurred though.

It was just me and the more experienced guy, and we finished what he was working on. The other guy was busy with other things, and never had a similar induction of his own. When I started to work with him after those 2 weeks, it was very apparent that I had caught up, and likely surpassed his ability with the system.

And given the highly unintuitive nature of that system and the rushed training, there was plenty of room left for insight and input without requiring the same initial period of confusion and frustration that caused him and the other devs to have such a negative and lasting view of the system.

And more generally, I'm not sure why you feel the need to poke holes and find potential negatives in what was a positive training experience. Especially when what you've said could apply to any kind of training, and disregards the situation as described.

I recently took a junior role working on a decades old legacy codebase, in which all developers and almost everyone who had touched the code had quit in the previous year. The week I joined, the most experienced remaining developer put in his 2 weeks notice, after a 9 month tenure. The next most experienced had only been there a month or two.

We then spent every day of the next 2 weeks on near 8 hour videocalls developing some remaining features on his plate. It was an extremely effective knowledge transfer process. I learned plenty about this bizarre program and it's nonsensical logic, able to figure out future problems, and ended up as one of the main bits of glue keeping it all from collapsing. I also found it very rewarding to work that closely with a more senior developer, got a bunch of more general advice, had some interesting tangential discussions, and made a friend. Also got plenty of advice to leave the shitty company and it's terrible software asap.

I dunno if I'd want pair programming day to day, but it was a great experience at the time, and made my entry to the role much smoother than anyone elses.

The irony is, this guy hated the needless difficulties of the job, but was so happy about quitting that he made my onboarding pretty great, and so I didn't feel his level of frustration while continuing on in it.

Turn off tabs? You don't switch between files regularly?

vscode is great for working on remote machines. i work across a few and theres almost no difference between working on a local vscode workspace and a remote one, as long as the connection is good. easy to set up, and theres no syncing or anything either like pycharm seemed to do. you work directly on the remote machine, same as ssh+vim through a terminal

and as a more general tip, that came as a result of coordinating between multiple dev/test/prod machines: use different workspace colour themes to quickly know where you are, and maybe change the default to something terrible.

my main dev machines stay nice and comfy to look at, test isnt too bad either but a very different colour. but prod uses my new default, a horrible bright red, making it impossible to forget im not in a designated safe space

thank you for ctrl+d. i felt like id forgotten how to cycle through searches

middle mouse button also for multi-cursor. good for getting to the ends of lines with different lengths, then ctrl+arrow back through them

International standards for reference connectors for medical devices. Basically, if you make syringes or IV lines with a screw fitting, the dimensions of that fitting need to be within some range so it'll make a secure connection to something else. Those are made out of plastic, all materials and dimensions are well defined for their usage and mass production, and have a decent tolerance to them.

But to check THAT tolerance, you have these metal screws that they need to securely attach or be unable to attach to. And since the metal fittings will be used for batch testing entire production runs of life or death parts for years to come, they go a little overboard with specifications.

I'm not sure if it really needed to be THAT precise, but that's just what it was

But that assumes X is not an unknown, which is kinda the point. "X-like" is an easy pill to swallow for people who want to reduce risk, since they already know X.

If you just want to poke a stick at some lesser known Y, it's harder to appeal to those who want to understand potential returns on their investment.

And it seems that there was a time that predictability, and even returns, was less of a priority. I can't recall the podcast (maybe Planet Money) but they mentioned Vannevar Bush pushing for the government to act as a patron for sciences, and to take on risk that private investors would avoid. Like, spend up to find a new X, then let the private sector step in and develop the X-likes.

I listened to a podcast a while back that discussed why the US shifting towards this approach (after a period of less constrained funding post WW2) has lead to worse returns on research investment.

The basic premise boiled down to: Scientists already want to work on valuable things, they just have different priorities. Understanding unknowns is motivation enough for them. But this makes the impact of their work also unknown, and scary to people who see that motivation as wasteful.

Making them justify ahead of time why their work will be useful, to satisfy the risk tolerance of financiers, means that they need to reduce that unknown before they even start, and potential impact with it.

Oof, I used to work with one of the few workshops in the world that could produce small batches of parts down to 0.0001mm or something a bit ridiculous.

Their pricing and supply times factored in a pretty significant failure rate, and we were basically asking them for highly precise screws and nuts for a couple thousand each.

As a former mechanical engineer, the forgiveness is an amazing feature of software development. Not only can you easily correct mistakes, but you can deliberately run head first into them over and over, essentially brute forcing a working solution, without pausing to be precise. Especially with interpreted languages.

I'm not sure if this command will work? Well I may as well just try it anyway. Something broke? I'll throw in a breakpoint and try out a bunch of dummy variables and alternative methods until the errors stop.

And while it's a common complaint that compile times force some extra care, with hardware that extra care needs to happen outside the medium itself, mucking around with CAD software and such, before sending designs off to workshops. It'd be like if the solution to avoiding compile errors was very carefully handwriting code on paper

Yea it's crazy. My dad has a classic Gameboy that his great grandfather purchased during the first world war. That Gameboy saw a couple more wars after that too, including 5 years up my grandads ass in a POW camp, and 2 more inside another soldier who brought it back for us.

Can confirm it tastes bad.

I also don't quite understand the leap to controversy, which seems to rest on the assumption that this person does not have a pile of leaves for a head.

So porting between ML frameworks was my job for a while, and the short answer is Yes, common layers can be quite simple to describe and reproduce in different frameworks. eg "Conv2D(2,3)" is enough info, in code or text, to describe a 2d convolution layer with 2 outputs and a shape of 3x3.

The longer answer is that the rest of the Conv2D configuration can then be easily overlooked, unless changed from the defaults. And those can be different across frameworks and potentially break things, even they even exist in your preferred framework. You can always create custom layers though, if needed.

But many papers also seem to do a bad job describing the actual structure of their own ML network. They can be vague, confusing, or simply inaccurate. And that can be because they are a general concept with flexible details, or because they struggle to put their model into clear words and diagrams. Or simply because they know the code is going to do the lifting.

I've had the same thing with Pocket Casts and new podcasts.

It's a bit jarring to listen to podcasts full of Americans and Brits and and hear ads for some Australian bank or something

As an Aussie male, I agree?

There are some parents like the parent comment, who claim that having a child is some essential ingredient for learning empathy.

To me, all that says is that they lacked empathy before having a child, and continue to lack empathy for anyone but their child. And they're so shocked by their new experience of empathy for this person they've created, that they unempathetically claim that others must also create a person to experience the same shocking feeling of caring about more than just themselves.

I've found the perfect notebooks for me are A5 spiral bound dot grids. Fairly compact size, unintrusive binding. The dot grid forces less structure than lined, but isn't the wild west of blank.

A few months ago I also looked into a bunch of note taking methods, even bought a similar A5, spiral bound, pre-formatted organizer and thought it'd be perfect for organizing my days. It remains unused except for a couple of lines where I began to note the days tasks, then crossed them out and tried to start again the next day.

But a dot grid purchased around the same time is filling up very quickly with odd chicken scratchings of work notes. The only hint of structure are dates scrawled wherever I happened to be starting from that day. Any very important things get circled or marked with an asterisk

I'm surprised Ethernet over Power doesn't seem to get more attention. It's basically Ethernet cabling without running any new wires. It was the only thing that fixed wifi availability throughout our townhouse.

I'd be interested to know how a wifi mesh performs in comparison, but I can't see how it could be nearly as good, without being much more conspicuous.

Pixel 5 does. I tried with one recently and noted it only does mirroring, unlike Samsung and Huawei which launch some pseudo desktop OS when plugged in.

I worked in a couple of Japanese tech offices. Contracts and salary included prepaid overtime, to get around the government saying ALL overtime should be paid. But they must have also allowed up to 40 hours per month to be considered "reasonable", so that number was in the contract, and I'd only get overtime if I went over it. Felt like a shitty loophole to agree to, but luckily both companies were super cool and overtime was uncommon, but happened sometimes. So it felt like they'd just put it in as a convenience, like saying "there might be some overtime, but let's not deal with paperwork unless it gets out of hand". And the "40 hours" was paid regardless.

It would definitely be a convenient loophole for companies to continue shitty practices, so I think I just lucked out with the places I worked at.

You can set up your phone (or DSLR) as a webcam in a pinch, no need to purchase new hardware.

I recently upgraded to a gaming laptop with no camera at all, and for a moment thought my remote working life would be burdened by expensive and clunky extra hardware to avoid seeming ineptly suited to working from home. Instead it's only burdened by awkward phone placement, but the image quality is much better than before.