I read this pdf years and years ago.. I wish that I could say I followed it. It's rather brilliant in its simplicity, and honesty.
The math can't be argued with. Eat X, expend < x and M++.
I'd agree that running a server is easy.
I built one for my company once. It ran on a standard PC (early 2000's).
But for some reason it never worked from my house. (Rogers ISP in Canada)
It took me hours and hours to find out my ISP didn't allow me to run a server. BellCanada ISP did, so the server worked on my co-workers system perfectly.
To be allowed to run the server I would have had to pay an extra 200$ a month, and be classed a business address.
It's not just that the tech is hard, the ISP's don't want it. So they gate keep.
But that's just it.. One would have to stand up a server that hosted the 200gb, so their Iphone users could consume the data. Or they'd go through a central server.
Amen. I don't even get why most companies have Dev-ops. For the price of one Dev-ops you can get the most expensive plan on many providers. Running the most expensive Heroku plan (with a concierge service) is cheeper than an employee, and office space, and medical insurance, and ....
And that's just the one provider I know.
I want to type git push master, and that's the end of my involvement in standing things up.
This is sort of true.
In the case of the watch, if you read the blockchain for the serial-number on the Rolex, you could engrave that too? The storage medium of the data wouldn't make a difference.
The same could be said for the NFC chip. Those are copied all the time. Just purchase a blank and overwrite it with an original.
Not a chance on that mate.. No way on Arch. Most of my neighbours can't change their wifi password. Heaps of the 20 somethings can't even run "ls" in a terminal.
I found it interesting that the content of the NFT is held by a company that can remove it at will. To me this flies in the face of freedom and will land us in the Youtube paradigm. Where walking past a restaurant playing music gets your video ownership ripped from you.
That feels very bubble like. What I set up will be what I see, and I will only see things I've sort of pre-approved before. The concierges will be in charge of what I see. That scares the heck out of me.
Oh.. and don't forget when bug reports get closed because the dev's say "this has received no action".
I see this on github all the time. The team finds an old bug report and closes it because it was reported months or years earlier. I mean nothing was fixed, but the reporter isn't super responsive.
Why on earth would you melt down? Been a dev for over 20 years and sure some days are a bit hard, but meltdown?
Best guess, you own the code, you own the product, and people keep breaking it.
I work for a great company, and we have a prime directive.
~"We believe that our coworkers have done the best they could, given the knowledge they had at the time and the situation."
So suggestion:
Give your team more credit.
Quit working where you work.
I think this leads to silos.
MicroServices written in different lang's mean Java Dev X can't maintain Python service Y.. Not in an efficient way.
What's worse, Java Dev can't move to Team Y without upskilling not only on the service, but also the lang, so they get pidgin holed. She also can't move because she's the only Java dev left.
In rails this would be an activejob (part of the mono), and spinning up workers would be trivial.
The "workers" would pull off a redis queue, and you could add different jobs to the queue easy-peasy.
I am 100% not interested in ops. Deploying is handled by other way more qualified than I.
I never expect a JS expert to build elixir, I don't expect an elixir expert to write bash, and I don't expect a bash expert to know about switches and cabling.
I don't understand where you draw the line..
Should the designer who also crafts the css do ops too?
I think high quality comes from specialists. Sharp knives in the hands of pro's
I find with microservices, they are a fake separation of concerns. When I have to work on something, and it covers two or three services, I'm actually working on a mono app.
I've found smaller "service" classes that do one job meet the same need. One or two public methods "perform" and "valid" seem to work perfectly.
I love the lang.. TBH though performance has never been something I see as a fault in the language.
I've almost always found (for my apps) that it's data access that's the hold up. Like if I map the issues, n+1 or bad indexing have almost always taken the lions share of slower code bits.
It irks me when people sight the lang or ruby as having bad memory or being slow. I've seen a tweak of the indexing cut response time to 25%. I even managed a 10x gain off of one index adjustment.
Typically I lean to rake tasks (rails dev).. these have spec and go through PR process just like everything else.
In worst case we jump on directly.. But each rails instruction or db instruction is logged against the dev who did it (In slack chat that anyone can see, in real time)
Off topic?
I just read an article about Sesame Street, and followed it up with an article about tornados, followed by a video of "Planes I see from my front yard." I'm not sure what topic HN really falls under.
This feels like that 100% beef thing that McDonalds was rumoured to have done. (Urban legend)
We Fact Checked (tm)
I think they should be held to account, if they're slapping that label on things.
I think when I edit services/jobs in rails I get some solid use of VIm, but I find navigating through files to be tedious. In rails I have to do this all the time, and short of installing plugins to make it more "many file friendly", I can't get past that limit.
On a side.. a few times I've told the recruiters that I'm not interested in the role, because they offered HackerRank tests..
Most of the time they come back and ask me to come in and chat instead.