Passive house thinking comes from an era of peak oil concerns, no solar, and no heat pumps. None of those conditions holds anymore. Further, passive houses are notorious for overheating and because they’re so airtight they require expensive mechanical ventilation and make-up air systems unless you want indoor air pollution problems.
People building houses today are much better served by spending their money on solar + battery + heat pumps than going passive.
To the level of a clinical diagnosis, yeah it seems quite likely to me that most people can’t discern autistic spectrum behaviour in their peers. I bet most people couldn't even accurately say what those behaviours would be.
Yes, to me this is a biggest feature of Typescript: A little goes a long way, while the advanced features make really cool things possible. I tend to think of there being two kinds of Typescript - Application Typescript (aka The Basics, `type`, `interface`, `Record`, unions etc...) and Library Typescript which is the stuff that eg Zod or Prisma does to give the Application Typescript users awesome features.
While I aspire to Library TS levels of skill, I am really only a bit past App TS myself.
On that note I've been meaning to the the Type-Level Typescript course [0]. Has anyone taken it?
Why would a manager who’s able to claim the credit of their reports in order to advance their own career then PIP the best ones? Wouldn’t they keep them around to keep claiming credit from?
I’m not doubting your story (I’ve never worked in India) I just don’t understand the incentive to fire a good worker in this scenario.
> The ugly glass UX, the weird floating controls, the always on display, blah blah
I'm on the "some like it" boat, to my surprise. I think the glass effect is eye-catching in a good way, and is much-less of a readability issue than I had expected. I often notice how cool it looks over my rotating background photos. I also love the always-on display because I don't have a watch.
For the AirGradient device I think the way to calibrate CO2 is to expose it to fresh air at some point, which has a known CO2 level. It’s supposed to auto-calibrate. But if you don’t do that regularly then the readings will drift (without anyway of telling they’re drifting). You also can’t tell when the sensor has calibrated.
IIUC VOC is way more complicated and hard to both calibrate and interpret. I’m not sure I have any faith in that value.
I do think a lot of people are going to be mislead by these monitors, the sensors and devices come with a bunch of caveats that aren’t clearly communicated.
For me what people should most care about is particulates, and at least as far as I know those sensors don’t come with the calibration issues of CO2 and VOC. That’s the sensor my AirGradient is set to alert on.
> The current norm seems to be two week sprints and all these things are done at the beginning and end of them.
Everywhere I've worked that did "agile" did it this way. The ending of a sprint is always the start of the next one; teams are always in a sprint. If that part of the process can't be changed or removed then one of the best things to do is decouple the sprint cadence from other events. Eg don't put demo, pointing, planning, and retro on the same day. Try to do pointing mid-sprint, if you know what's coming up, so that you're not cramming it in at the end. Don't release to staging/prod at sprint boundaries, do that mid-sprint. The worst is to clump all the meetings, distractions, and stresses together.