> Not only is it breaking the law, but you could also jeopardise your insurance!
> Changing powerpoints or light switches might seem simple, but unless you are trained and qualified, there are lots of risks you just won’t know about. Never attempt to do your own electrical work – you could kill or injure yourself or your family, or start a fire. Always use a licensed electrician.
I think we can all agree that Australia is taking it waaaaay too far, and requiring a licenced electrician to change your own light switches is just dumb, and it has nothing to do with safety but making sure that electricians have a steady source of bread doing work that anyone should be able to do with a screwdriver.
Unless Australia has a much lower rate of home electrical accidents than rest of the world, I refuse to believe that this is a good thing.
Sorry, a bit offtopic but that partiular thing really grinds my gears, especially since it covers any cabling that goes inside your wall, so even just running an HDMI cable inside your wall requires a certified electrician to sign off on it.
I mean, when I moved into my house in the US there were ground wires in the outlet boxes, but none of them were actually hooked onto the outlets. I'd agree Australia's restrictions are too far, but "DIY all you like with things that could kill the next person" has its issues too.
Unless there's mandatory, regular and thorough inspections of licensed work, making said work require licensing isn't actually going to increase quality. I've seen absolutely terrible, dodgy and unsafe stuff left behind by trained, licensed & well-paid professionals that only "worked" due to a combination of luck & safety margins.
I can no longer edit, but I've learned my comment is somewhat misleading.
Home insurance policies (in the US) often cover negligence including faulty electrical work. If it's in your contract, they will pay.
Insurance companies will then do their job, which is to find someone liable and send them the bill (subrogation). If you did the work, you're the responsible party.
TL;DR: Burning your house down is probably covered by insurance, but that doesn't mean you're not liable.
Hack programming language (Facebook's php++). They are called coeffects and can range from "this is pure with no side effect" to "this can modify local members" to "this has I/O".
Monkeypatching, dll injection, Jar Classpath - Huge sources of pain. It Is how it's done but in certain contexts any benefit is immediately outweighed as the bugs start accumulating.
Right, in certain contexts (I would even say most contexts) it can be a problem. However, it's not obvious to me that this—a well-defined interface for injecting plugins that's specified by a library that functions as low-level infrastructure—is one of those contexts.
It needs to be scoped to the dep so conflicting deps have independent dependencies.
If foo 1.1 takes a dep on Bar 1.2, and baz 2.3 takes a dep on Bar 1.4, both Bar contexts are tested with their respective libraries but forcing Bar to a particular global version can have problems and both versions of Bar are needed to have tested behavior.
Examples mentioned and OP change the global behavior vs proper dependency management.
There’s something about having two independent Bluetooth headphones that makes them much more than twice as likely to get lost. And I suspect that part of it is having both ears blocked and thus needing to take one out much more frequently.
Also there are a disproportionate number of tech people who have ADHD, and multiple small objects do not just have a high probability of getting lost, they have a virtual guarantee of doing so. Multiple times before they are lost forever.
One big realization I had how sophisticated the ancient world is, the Antithikara Mechanism. Device built by ancient greeks in 200BC using thousands of years of astronomical learning to build the first KNOWN Analog Computer and devices of similar sophistication are not seen until the late middle ages / early renaissance.
Some ancient societies were quite skilled and sophisticated in certain areas. But as far as we can determine they didn't have the scientific method as we understand it today.
That must also be some weird definition of work. Otherwise this doesn’t even leave time for meals, personal hygiene or for communicating with your s.o, let alone any kind of rest.
Not everyone has a s.o. In addition you can work remotely, order everything in, and nothing truly terrible happens skipping a week of hygiene.
I think I frequently have days like that if I add my side projects as work on top of actual work. I wouldn't want to spend that time on actual work as of now though.
I usually don't eat for the first 12 hours and then at some point eat everything I have for the day all at once. Kind of intermittent fasting, but not intentionally or for those reasons.
I.e. if I am excited about a particular side project I would do that.
So really depends on whether the work is exciting enough. If it is, this would be easy. It is rare if you are working for someone else or specifically a large company though.
If it is truly interesting work then you wake up focus completely in it and all of sudden it is end of day. In that case it is a little bit like an addiction where you just always have to build this one thing more, delaying eating, sleep, etc.
For usual work I would maybe only consider it if I was paid 4x the usual hourly rate for it.
Edit: oh you must mean household chores, I was thinking about the App. That your wife was so pissed off she decided to cover the monitor your Slack was open on.
There's different styles to it, depending on where you live, how your life is, and it means to "live your life" for you. E.g. you could have certain periods where you work really, really hard, and then you take a longer break, month, 3 months, 6 months, etc. Or you could work really hard to try and get an early state of financial independence. At that point living life becomes very easy, because you know you can just quit to do whatever you want, you are not dependent on anyone else so much less stress. Otherwise job market, your company state, leadership etc will be unnecessary stressors.
I completely agree but I will say that as somebody who intellectually understands that principle, overwork and burnout are still insanely common and arguably even rewarded in some work cultures / tech in general, and I screw this up a lot.
Even people who understand this rule / philosophy end up violating it if they're not careful.
... and with that I think I'm probably going to sign off for the day. It's late.
Agreed. I’ve put in days where I did nothing but work because the project was fun and also due in a week or very soon. Food really doesn’t take that long especially if you order in or pick up close by. Doing this consistently though would surely lead to burnout. Unless, of course, you just consistently love the project you’re working on. Even then, you need a break.
Don’t really understand the deniers here. I’ve also worked through weeks of literally waking up and building software until time to go to bed, 7 days a week. It is definitely possible, but it destroys you mentally. It was never the expectation that it would be the norm, so my wife was supportive.
For him work constitutes for the most part just being at the bodega. I worked from home for about 5 years. I was at home nearly all the time, and did concentrated work 8-9 hours a day. Can I claim I actually worked 16 hours a day just because I was at home and there were deep learning training runs running in my garage? Of course not. When I say "work" I specifically mean _doing_ something, not just being there.
My father works partly 18h a day for several weeks only with breaks for fast eating and 3h sleeping. It's not like that he enjoys it much. But as a self-employed you have to work that much if you want to keep your customers (delivery date is in the quote, so you have to deliver).
He has done that for the last 40 years haha since I know him never had been different.
