After months and months of waiting for the devRant mousepad to become available again in their store ... it turns out it's going to be ducking expensive to get that item (shipping costs as much as the product itself... and it could take 6 more weeks to arrive!) Came on, 1-6 weeks ... the variance of the estimation is huge ... I have lost the motivation :(

Rust should support explicit variance declarations. Explicit declarations are like the main feature of the language, variance is a critically important part of a type's public interface, and &mut-s that are never reassigned and should thus inherit the referee's variance are extremely common. If the language can't recognize this, I should be able to declare it with a single unsafe rather than constantly casting to and from 'static.

!rant

So got into a small debate (actually a civil one, surprise surprise) about the final project for a class. Basically the final project involves a team of 3-4 coders making a website for an actual client that either they find or provided by the professor.
The exact point of conflict was that the work is pro bono. The student argued that the work should be paid since after all, real work, real client. My argument is that because the clients don’t exactly choose the designers (or have little to no knowledge of most of their work) there will be high variance in quality and contract work would cause more conflict if done in class.

So just wondering, what do people think about this? Logistical issues aside (earning money for technically school property/ownership and money for learning essentially)

Question for the electrically minded.

I have a laptop with a 19v input.

I have a portable UPC with 2 voltage options in the range of this, I can undervolt at 16v (the laptop battery voltage) which works with a small firmware correction to ignore a board sensor, the other option is to slightly overvolt to 19.5v which I assume the laptop could handle through its input regulation.

Can anyone confirm if a .5v variance at charger is within tolerance? It would be an overvolt of 2.5%

Any advice on how to deal with gatekeeping developers? How to deal with red tape?

I work with people that are resistant to code and process change. Continuous pedantic pushback on nearly anything; one raised a fuss over metrics not being satisfactory at a 5% threshold for alerting stating that 4.99% metrics variance wouldn't trigger an alert.

It's genuinely as though my coworkers are all scared of code based on the way they behave. They don't seem to code very often either.

I'm someone that codes quickly but I have to constantly write proposals for quite literally any change to the codebase. Even IF there were issues we could always rollback (and even then we have metrics, alerts, canary rollouts, feature flags, etc etc). As a quick aside, my pace isn't related to the pushback nor experience/skill level. Just affects my morale and mental heth to be blocked.

I can communicate effectively and I try to be as clear as possible in my proposals but this is absolutely driving me up the wall and killing my motivation.

This is a faang-level company and I would've expected better.

Any advice on how to best navigate this? Is this the norm???

I find myself thinking that lack of boredom related to
Unfulfilled relationship quality is what is killing the world
We require interaction as humans to spawn variance in our lives

No variance detected
Defaulting

BRAWNDO HAS WHAT PLANTS NEED GODDAMN IT !