People are silent about it because Tether pumps their bags, sadly.
271 karma · joined December 27, 2017
People are silent about it because Tether pumps their bags, sadly.
And "audit" not as in "spend millions on an auditing firm to do it for you", but audit as in "independently verify it yourself on your own computer".
The barriers described in the article are very real, but there is also real work being done to remove them.
I yes, I too rememeber the FirefoxOS. Good times.
No it has always been the same company, and we tried to tell you.
I'm not a fanboy for the sake of it, but you're being a little over your head here.
There never was a scaling issue.
BTC runs mostly on surplus hydroelectric power. This may change based on what's locally available and the local cost of oil gas and coal, but when renewables will become cheaper than fossil (which will never be soon enough) it will not make any sense to mine on fossils.
No, a model models, does not (and can not) reveal anything.
It's no i3, but it covers a lot of usecases when I'm not on my linux box.
The Morning Star example (which I read of just now) seems to have the leaderless thing as a cultural backdrop, and new employees receive training in it (by doing). OTOH, you can't just do away with managers in a structured organization and expect it to work, the culture is not there.
All of the busybox alises, actually.
Why not just put a mirror on your desk?
That's probably why people want to be vocal about it (not as much as said bro culture still)
Your attitude of "a tool I need doesn't exists, so I'll just go ahead and create it" blew my mind and changed me for the better.
I'm dedicating my next test framework to you. Thank you for everything.
"Motivation" is the "why?" of what you're starting. If you start a project and exhaust the "why", it's ok to stop there.
Is it curiosity? Is it want to learn something new? Is it want to check out a new technology? You could well answer these questions without actually finishing a project (it the final project itself wasn't the original "why").
If you want some real life "why"s, you could check out one of the many Covid-19 project aggregators. Here is an aggregator of such aggregators: https://covid19projects.now.sh/
You cannot imagine how I'd value having really dumb looking code in my life.
Yet here I am, swimming in a swap of cleverness that I can't refactor nor will ever be able to wrap my head around.
I envy you.
I'm halfway through, and I'm really impressed not only by the prof's preparation but methods. Very clear.
Expecially because the big picture is easily stated: Write the least amount of clean code while providing value.
(PS: code is liability)
What we like to call "software engineering" isn't actually engineering, and more like a craft than anything. Actual engineering in software is possible.
I take issue with calling our field software engineering. It's a buzzword.
Bullshit. Humans have been sending computers into space for decades, and while yes, some have had programming problems, most worked correctly, for a very specific definition of correctly.
Thing is, NASA (and Russian and Chinese and Indian and ...) space engineers have approached their challenges from the point of view of actual engineering, while modern "software engineering" is all about craftsmanship, and just a sprinkle of actual engineering to make ourselves feel good.