its like using the army to watch over kids crossing the road to school
Many other source control systems with far simpler systems
this whole branch and pr into merge process didn't exist 10 years ago like it does now. It started from open source and low trust - but nobody stopped to ask what problem it solves.
If somebody needs to check your code as part of a formal process - rather than some arbitrary invitation you issue in special cases - you shouldn't of been hired with the job of writing code.
Kids wont listen to you
kids don't care how much you have thought about something
the way you are has more to do with who you are not what you think and the way they will be is more like what you are
Your kids spend most of their time with people who are not you
control and choice is an illusion that follows a chain of high pressure, highly emotional situations.
Get a dog - learn to train it. Having kids is like that - except its cleverer than you, doesn't want to make you happy all the time and wages psychological warfare to figure out how to get what it wants at all times. Or at least the fun kids that will make you wish you had a plan in retrospect will.
When you have a second kid you will do things differently - you will be wrong then too.
good luck
your kids wont like what you do - they are not you and they will value different things to you.
Help them discover that and support that - unless they don't want to. they wont.
Amazes me that so many people dont understand that if all things are dependant upon your business logic or on your domain then this is natural. Its natural hex architecture
I actually do not think your code should throw exceptions. It is really just an Either / result and then if something does blow its because you havent anticipated it via wrapping something in an either or result ... and so it should blow and the callers of your library should be submitting a defect..
now a fairphone uses 2W during use, a dual-socket server 100W in idle (!). Assuming emissions scale with weight, I'd say for a typical server, this is very different.
Still, I agree with you: design for efficiency and then mend and use efficiently.
> We stress that this estimate carries some uncertainty but gives us a reasonable idea of the impact of ICT. Across studies, roughly 23% of ICT's [information and communication technologies] total footprint is from embodied emissions, yet the share of embodied emissions for user devices specifically is ca. 50%. This is because, unlike networks and data centers, user devices are only used for parts of the day and use less electricity, but are exchanged often, especially in the case of smartphones.
"embodied emissions" being emissions generated from manufacturing.
older blog discussing data from older devices and electronics:
For a rough first pass, I would just look at monetary cost.
I was going to dispute OP's comment. Thinking of my old Athlon server that used around $20 of electricity per month, cost about $600 new IIRC (mobo+CPU+RAM), and ran for more than a decade ($2400). But there has been a concerted effort to lower device power consumption, and my current 5700G server (two generations later) uses only around $5/mo of electricity.
You need to stop and ask yourself if this kind of comment adds any value to the discussion. It's not even offering a good reason for OP to make a change to their language; it's pure nagging.
I would expect wikipedias to be more accurate than teachers.
I am a software engineer who spends his life showing people the origional sources of information to help them unpick collective repeated misunderstandings. That takes me, with more experience that my team combined to do that.
teachers have experience of teaching - not possessing knowledge or the practises of sifting, applying and validating their hypothesis aroudn the veracity of information.
Most curriculums are out of date in ways that don't matter all that much. But i still rekon wikipedia is still more up to date than them.
this whole branch and pr into merge process didn't exist 10 years ago like it does now. It started from open source and low trust - but nobody stopped to ask what problem it solves.
If somebody needs to check your code as part of a formal process - rather than some arbitrary invitation you issue in special cases - you shouldn't of been hired with the job of writing code.