Hah, I'd love something that small. Right now, we have dozens of Node.JS apps, each one needing over 500MBs of NPM libraries..
163 karma · joined February 21, 2011
meet.hn/city/45.6306954,-122.6744557/Vancouver
Interests:
AR/VR, Hardware, Mentorship, Open Source, Startups
---
Hah, I'd love something that small. Right now, we have dozens of Node.JS apps, each one needing over 500MBs of NPM libraries..
I think your segmentation is way to rough. There is a ton of space between the farm with a few hundred nodes to manage, and Nest with a few million nodes.
People are just learning best practices to manage a few thousand web servers. Managing a few thousand brickable devices with KBs of RAM is more challenging.
On the other hand, this is massively better to what normal corporate types call a "whitepaper" (usually just a glossy brochure that tells you nothing new.)
> Where are the experiments?
The experiments are in the markets. :) I.e. "here's a new coin, will it make money?"
Sure, it "could help". But let's say there are 2 identical sites. One site upgrades from DV to EV. The other site takes the same money and invests it in a Graphics Designer to make their home page look nicer.
Which one will sell more product? I'll put my money on the nicer-looking site every time.
1) People don't "give" you jobs, you earn them.
2) Swearing is unprofessional
> SQl
Hmm, ten years of SQL and you can't spell it correctly? Something is fishy there.
> Every single one of these interviews was somebody asking me some random shit
I admit a lot of interviews focus on the wrong stuff. But there is actually a LOT of leeway in interviews, where you can show your understanding of software engineering even in the presence of dumb questions. If those companies were actually dumb about hiring, then you probably didn't want to work for them anyway. Find some quality companies to interview for.
Non-profits are usually more pro-user than for-profits. https://en.wikipedia.org/wiki/Mozilla_Foundation
Have you ever seen someone talk to a PC from across the room? Is there any popular PC voice software that is "always on" and doesn't get itself into bad states? ("dragondictate.exe has stopped")
I personally have taken 100's of pictures of Windows dialog boxes on giant advertising/airport displays. If people who are paid big bucks to manage a display can't keep it running flawlessly, how will someone who has bad motor skills and bad eyesight?
I'm not saying Alexa is more useful than a PC. But I am saying that Alexa is zero maintenance, and a PC is not. It's the same reason Chromebooks outsell laptops -- it's not that they do more than laptops, but what they can do, chromebooks do "better".
So the real moral of the story is "Don't base your livelyhood on proprietary software because companies WILL go out of business and leave you in the lurch."
It really depends on what you want.
The Z80 is more "corporate". There were lots of embedded systems built with a Z80 at the heart. People used it to get a lot of stuff DONE.
6502 is more of a hackable computer. Because it was used in the Apple ][, there were lots of people trying lots of strange experiments. Some were incredibly good, years ahead of their time. There are games in 64K that were more fun than most bloated multi-GB games on consoles today.
This dichotomy exists to this day. (Search "Visual Z80" vs "Visual 6502" and compare the depth of understanding and/or passion.)
Rob Pike's talk on why 'Concurrency Is Not Parallelism'
The drugs we have are warped by the abilities of people to make money off them. In fact, we can point to many "dead ends" where companies marketed drugs that were more expensive and worse than existing treatments.
I've personally witnessed a company taking an ingestable pill and turning it into a nurse-administered injection, just so they could take advantage of reimbursement. Same drug, but the patient suffers just so they can make more money.
The total budget of the DHHS is irrelevant. Only money that goes to researching unprofitable drugs would counter the assertion of the OP.
Nobody calls the computer immutable/stateless. Immutable/stateless is an architecture pattern, implying that nothing important is stored or shared between calls.
It doesn't say that you can't cache info or write log files, etc.
> Just a bunch of buzzword nonsense
Well, what's the alternative that you propose? Should my HTTP requests leave lots of state-full files laying around? Is it easier to manage deployments when every box has different files laying around depending on how old it is?
Also, remember these techniques are for people "at scale". If you only have 1 or 2 boxes, these techniques may not be useful to you, so feel free to ignore them. I've got a 1000 boxes, and have seen first hand why it's a bad idea for each box to be able to be a unique snowflake.
Even if you have physical machines, you shouldn't put your production image on it to debug it -- you should put a debug image on it that allows SSH. If it's a hardware problem, it will be easy to find. If it's a software problem -- well, you have 1000 other boxes running that software, so you'll see it again. Just add better logging.
Your eye is really more like a flashlight in the dark. And it interprets things way to much (see optical illusions.)
It's easy to dismiss these problems, because you are rarely are in situations where the difference matters. This is no coincidence, since people rarely construct things that our eyes can't process. For example, fluorescent lights are actually turning ON and OFF constantly, but we just happen to not be able to see that. There really is no color purple, we just think it exists.
But it's quite easy to mess people up. See "rotating tunnel illusion", or the experiment where subjects fail to notice they are now giving directions to a different person, or the experiment where people fail to notice a guy in a gorilla suit (!) when given a simple task.
So the upshot is "vision is nothing like you think it is". Maybe we should have different words for the way a computers see things (a lot more reality based) vs the way humans see things (with all their foibles.) Ditto for Consciousness.
Yes, when you only have a couple of servers, that is not the sweet spot for K8s.
But few people stop at 2 servers. A few months in, someone asks for a staging environment, and/or QA environment. Someone eventually realizes that they need to regularly test their fail-over and backups. Someone hires a contractor, and wants to give them a copy of the setup that won't block anyone else. Someone realizes we can centralize the logs from all these environments... And so it goes.
Even with one server, sometimes you go to do an upgrade, and find your "one server" is actually a tightly coupled bunch of services. (Made-up example: I want to upgrade Varnish, but it requires a newer library that is incompatible with my WordPress version.) That one server could be a server for the Database, one to run the cron jobs, a few for the cache layer, etc. If you break up those into different boxes, you can scale them better -- Instead of one big beefy server, you can have each layer at it's own scale (one or more wimpy boxes, dynamically adjusted).
You don't do this to save money directly. But by simplifying things, you make it easier to maintain. That saves labor, plus prevents problems (and makes it easier to hire and train ops.)
When you have just a few servers, it looks manageable. As you grow, it gets a lot harder to manage. K8s helps.
To whom? I see many people who need a trivial amount of server logic. Right now, they can do one of 3 things:
- Use a random site who may or may not radically change their business model in the new few years. - Pay $5/month for a VPS, then get forcibly dragged up the learning curve of becoming a full-time sysadmin - Pay pennies for Lambda
Is there a reason to re-write your backend? No. Is there a reason to consider it on your next project? Possibly.
1) If Basic Income is doled out slowly (say every week or every day as a credit card), then it's nearly impossible for someone to die from starvation. Should we also take away their knives just in case they commit suicide some other way?
2) The idea you mention is not "Basic Income", it's something else. And the major problem with that "something else" is: Who gets to decide what level of shelter is "good enough for basic"? Who decides what quality of t-shirt is "good enough"? Who decides which level of Ramen is "good enough"?
Having the government (or even a company) decide what products millions of people should get is Communism. It's pretty obvious that everyone getting these products will be unhappy with them. (Some people will think they are too cheap, others will think they are too expensive. But few people will be "happy" about it.)
Basic Income is giving everyone some money and letting people spend their money as they wish, just like Capitalism. Companies are forced to read the market and adjust their products to answer new demands. If they don't, some other company gets the dollars. Heck, science tells us that even if people choose to buy the exact same products as in the above paragraph, the people who choose it will be happier because they got to choose.
Everyone will choose to make their own trade-offs. In fact, some people will choose "cheap everything" in order to save up money. With their saved money, they can purchase "Luxury" items. So all companies benefit, not just the low-end.
For example, someone can choose to eat cheaper ramen in order to afford an XBox (people already do it today!). If many people start making that same trade-off, the market can respond and start chasing these dollars. Maybe Microsoft decides to make a low-end XBox. Maybe some competitor does. Maybe some rich people buy the new low-end XBox because they like its attributes better. Everyone with money is free to choose. There is no walled garden between the haves and have-nots.
No offense, but the idea in your book sounds a lot closer to "prison" than Basic Income.