Now what if this robotic lawnmower killed someone ?
And what if many lawnmowers started killing/injuring people ?
And what if this a known behavior detected during QA, but the robots are sold anyway with a disclosure ?
910 karma · joined January 18, 2014
And what if many lawnmowers started killing/injuring people ?
And what if this a known behavior detected during QA, but the robots are sold anyway with a disclosure ?
And consider your state of mind after the tech came over 6 times in a week, each time claiming to have fixed your HVAC but it keeps breaking.
When it is 40C max by day and 22C min by night, for example, the outside is still cooler than the inside at night. So ventilating will have a real impact.
With this you might reach 25-26C inside in the morning and 29C by the end of the afternoon. It is hot but generally OK with fans, depending on humidity.
Then you can turn the AC on during daytime on top of that, which makes more sense than relying only on it.
I know I will need an AC one of those years but for now this is fine for home working.
That is true. I heard that many times...
> during a strong heatwave there is no adaptation possible, AC is needed.
At some point, yes, obviously. But in many cases I see people installing an AC without actually trying anything else. And then it is an energy orgy: AC set to 16C with sunlight hitting straight to the middle of the room...
True that it is not so humid here in the French alps.
But to be clear: do get an AC if you need to. Please dont rely only on your AC though. Turning on the AC (eg just pressing a button, really) is so easy we tend to forget about the rest... and end up burning even more fuel.
That's pretty nice actually!
I am in a brand new rooftop apartment, so pretty exposed to heat. I can keep 28-29C indoors when it's 38C outdoors. That's hot but workable with a ceiling fan.
At night we open all windows and have a ceiling fan above the bed. We've got about 24C indoor in the morning, with nightime outdoor temperature at about 21C.
Obviously I keep physical activity to early morning and late night.
But since modern buildings usually have huge windows, we're letting in about 1kw of heat from sunlight per square meter of window. That's 6kw for a 3x2m bay window, or about the equivalent of 6 electric heaters at full power.
Block that heat ouside of your house with all kind of shade you can get: trees, blinds, adjustable shades, rolling shutters...
Also, close every openings during the day, vent at night.
Please bring some shade and save energy.
Edit: also, without wind there is a hot and humid bubble around our own body. Fans help a lot with that by bringing fresh dry air right onto the sweat so it can evaporate.
Have an AC if you need to. But please dont have only an AC. Shading and fans pay for themselve in energy savings.
Edit: you can still use an AC or dehumidifier on top of it. You will consume less energy with shades.
Letting the sun in is like letting your heaters on. You would not turn on both heaters and aircon in summer, would you?
We can update building regulations so that new building are better.
We can plant trees. It brings shade in summer but lets sun through in winter.
We can stop taking the plane.
I mean, there really are tons of things to do!
It'd be better to block the sun before it hits the window though, so that the window itself does not get hot and heat the inside.
Edit: people generally use emergency blankets, fyi. You can stick them to the glass with water.
That is not correct. Heat, wind and humidity all contribute.
In a dry air with no wind, your body creates a "hot and humid" bubble around it if you are not moving. A fan helps.
Humid but neither cold nor hot air may not feel great, but not that bad.
Hot and humid air with no wind, now that's bad.
Edit: I know because I added shades and fans.
That's why.
Edit: Also, as some other comment said, thermodynamics tell us that it would take an inordinate amount of energy to bring carbon back to safe levels. More than what we get from burning oil. It's about entropy and all that. So there's that.
Before you do that, do the cost effective thing: shadow and wind. Then you can add an aircon iff thats not enough.
For shadow, reftrofitting adjustable sunshade is pretty effective. Sunlight brings about 1kw per square meter of window. That like having your heater at full power when its already hot.
For wind: fans, preferably ceiling fans. Lowers perceived temperature by about 3.5 °C.
Correct. And we'd be "out of business" too as a country if we decided alone to fix emissions. Other economies would have passed ours because burning oil is so damn useful.
Thing is, I don't feel we are changing much in this respect. Now the best idea we come up with is burning more fuel for aircon...
Seems pretty short-sighted to me.
Edit: I dont quite buy that argument, in case it was not clear.
Edit2: oh, is it specifically about incremental compile time? In which case I understand that tests can be run piece-wise quick indeed.
Most bugs aren't type issues until you make them be type issues by expressing some business invariant in types.
Refactoring makes an exception not being caught the same way as before ? Type issue. Mixing up some ids ? Type issue. Etc.
Now that can also be emulated with extensive tests. But isn't that a concern for OP as well ?
That changes the default from "anyone can do anything" to "gotta ask parents". Defaults matter at scale. It adds friction.
A good analyst makes a hand-crafted, custom report in a day. A programmer makes a factory that makes thousands of reports per second for a thousand clients.
I am yet to find a factory at HomeGoods.
Now the kind of factories we make might change, but isn't it the fun part?
As a leader, pushing for rapid change cannot really be nuanced lest the push dissipates into the organization's entropy.
In practice, I found it difficult for coworkers to read and understand so I dropped the idea.
Another limitation I found is that it breaks down when you start using inheritance. For example:
```
class _A: pass
A = NewType("A", _A)
class _B(_A): pass
B = NewType("B", _B)
def foo(a: A) -> None: pass
b = B(_B())
foo(b) # Mypy is not happy: Argument 1 to "foo" has incompatible type "B"; expected "A"
foo(A(b)) # Mypy is OK
```
I wish you were right but, IMHE, it requires a lot of communication once teams grow and many team member do not fully understand the consequences of what they do. It is nice to have something that helps when reviewing code.
> If you have members that users probably shouldn't touch, you prepend them with an underscore
Well, this is precisely what TFA does. It prepends the constructor with an underscore.