djb_hackernews

350TB of memory, and 50,000 cores, nice.

ARP caching seems to be a common issue in cloud environments. AWS recommends turning it off and does so itself in their Amazon Linux distro.

There are quite a few red flags in the story, nevermind the ICO.

- Pitching before building

- Delaying release for more development

- "Tremendous growth" but no one willing to put up $$

- What is forcing a series A? Are you out of runway?

- An investor taking the lazy approach to investing (requiring others invest first). This is so common and so lazy and not confidence inspiring.

As in you investigate why their employers couldn't retain their talent?

The way employers view "job hoppers" says a lot about the work place culture, speaking from experience on both sides and both philosophies. (One philosophy solely faulting the employee, the other philosophy recognizing the current state of the industry)

What do the people that use cloud instances that don't have local disks do? You definitely don't want swap to be on EBS...

It's not clear how this is different from what is currently possible. I'm not a route53 guru but can't you already a) create a subdomain microservice.mydomain.com b) create instances c) add the instances IP address to an A or AAAA record for the subdomain.

Is it that they didn't have APIs for these operations and now they do?

I know I'm missing something.

Hmm, I just found a comment using my same name (rare, but not unique) but an address for what looks to be an abandoned house in the next town over from where I grew up...

I've worked for 2 well known software companies and what you are describing is a Senior Engineer in both (5-10 years experience).

The place I am now starts fresh grads as Engineer I, then Engineer II, Senior Engineer, Principal Engineer, Architect and then Staff Engineer. Each promotion takes about 4-5 years so you aren't reaching Staff until about 20 years. A Staff Engineer is basically fully autonomous and is an IC that reports directly to the executives. They work on what they want and with who they want.

I understand this is different at Google and I guess Staff is the equivalent to a Google Fellow.

I think what dionidium was getting at was he only had about 20% of the story and filled in the rest in an uncharitable way. If dionidium is not the manager of that employee, dionidium does not deserve or require an excuse or explanation. If they are the manager then this complaint shows a lack of management skills and/or poor office culture.

"I'm feeling sleepy and will be in later" is an employee being upfront and direct that they will not be productive and do not want to be the source of waste in the office. This is an employee that should be rewarded and encouraged. An office culture where this type of message is ok should be encouraged.

What you don't want is a toxic culture where everything needs to be explained and justified to an office full of scorekeepers and clock watchers. The people that do care are the ones that shouldn't care and should probably be minding their own business.

In dionidium's scenario it is very possible that employee worked it out with their manager and the message was a courtesy message. It is very possible they are tired from putting in a late night the night before. It is very possible they are tired due to "truly unforeseen and unusual circumstances." Etc.

To me, dionidium is the problem in this scenario.

Why not just spin up fresh nodes and age out the old ones?

See: pets vs cattle

Docker doesn't imply not having config management. In fact for our infrastructure that was using puppet to build vms, we just run puppet as part of `docker build` instead. Still using config management and our prod, staging and dev environments run the same exact blobs.

Thank you for connecting the dots for me. The creator of Pulsar is Ron Pressler and the author of this proposal.

I skimmed the article but this seems heavily influenced by Quasar http://docs.paralleluniverse.co/quasar/ but doesn't make any mention of it.

I have some experience with it and I found it to be a very well designed and documented API. I hope to see it in the JVM someday.

The person behind it is pretty active online and does some other interesting things (the TLA+ subreddit), not sure if they are an hn reader but I hope they chime in here.

Not meant to be snarky at all. Though I do wish my comment wasn't the top voted one. People, please upvote the other on topic comments or have the mods bury it.

FWIW this is basically my path. I've done pretty much all of them to some degree and a few in earnest. In fact I'm working on my own language learning "tool" while I wait around for #10.

Language learning apps are step 5 in the ten step process of achieving programmer hubris nirvana.

1) I'm in college and I'm going to build an app to easily buy and sell books

2) Off campus housing is hard, I'm going to build an app to find roommates

3) Splitting bills with roommates is hard, I'm going to build an app for cost splitting

4) All my previous apps sucked because they weren't social, I'm going to build a social network app

5) I'm bored partying with my new friends, I'm going to level up and build an app to learn a new language

6) I'm lonely, I'm going to build a dating app to find a mate

7) I found a mate and the whole engagement/wedding industry is a fraud, I'm going to make an app to make it easier to navigate

8) My children are awesome, I'm going to build apps to manage their time/friends/eating/sleeping/learning

9) Technology is a waste of time, I'm going to spend my time on other hobbies and my family

10) I've been working 20 years in a boring industry and I see an opportunity to write boring software that solves boring problems that businesses will actually pay for. Jackpot.

Edit: As others pointed out, should have included: ToDo app, Blog App, and a travel app. Travel should probably be 5 with language at 6.

Doesn't this require you to trust Equifax to enforce and honor the freeze? I think the solution is "I don't want my report or any of my data in any sort of control or possession of Equifax". Where is that solution?

Interesting that usually GCP is one upping AWS on some metric but in this case it isn't touching the current largest compute/memory instance on EC2, the X1 family with up to 128 vCPUs and 4TB of memory. Though the blog does allude to them testing such types in a closed beta, it still is a game of catch up still.

You may be alluding to it, but Black Mirror has an episode that features the fallout of such a technology already. I believe it was in the first season.

I just read the preface and have to ask... is this heavy on marketing, cheerleading and kool-aid? First the author makes it sound like the Nakamoto paper was sent from the heavens and then this:

> I became obsessed and enthralled, spending 12 or more hours each day glued to a screen, reading, writing, coding, and learning as much as I could. I emerged from this state of fugue, more than 20 pounds lighter from lack of consistent meals, determined to dedicate myself to working on bitcoin.

To me, this seems a little dramatic for what should be a technical topic.

Right, a Honda Accord is a nice car to most people and could be interpreted as top of the market.

Now, if your post said for the right person, I had a budget to give them $150k in Austin, TX then we'd be getting somewhere. "top of the market rate" is just too ambiguous in most experiences.

> I had the budget to give them a top of the market rate. I didn't need the 10x developer just smart .Net developers.

As "just a smart developer" how I read this line:

"I don't need a Ferrari, a Porsche would do, and I'm willing to pay Honda Accord prices for one"

That might be an age thing. Once you have seniority in either field you gain a lot more free time if you want. Source: Am a software engineer, wife is a physician and we both have plenty of free time.

Right, I see that in the CA docs. This doesn't work with our business requirements since our workloads are spikey and we don't want to wait around for pods not being able to be scheduled to start more nodes.

A contrived example is imagine if for every gmail user that logs into gmail google spins up a pod for the user. No imagine if there wasn't any capacity to schedule a pod for a user that is logging in. That user would either be denied or have to wait for an instance to come up and then the pod to be scheduled. Not ideal.

Thanks, I have looked at this as well. There are a few issues:

- It only scales worker nodes

- It only scales nodes if a pod can't be scheduled. This is too late for us as are requirements are to scale when resource utilization crosses a threshold (ie reserved memory is over 70%).

- It still doesn't solve the baked AMI problem. I may be wrong about this but the AWS docs for CA are lacking. For instance, when does the ASG/launch config get created? Is that something it does or it needs to be done ahead of time? Which AMI does it use? etc.

We have, and as far as we could see it is a command line tool that needs to be run manually. This model doesn't work for us as we scale instances in and out by the dozens throughout the day. I could be missing something but anything that requires command line interaction isn't viable.

For instance, if we see that our worker cluster is has reached some consumed capacity threshold (CPU, memory, etc) then we need to add more worker nodes. The way we do this is via Auto Scaling Groups. Auto Scaling Groups work on launch configs that are essentially an AMI and instance user data. Getting an AMI that just has the Kubernetes stuff that can be started at will and told to join clusters at runtime has not been clear from the documentation I've read.

This is great. I have been looking at Kubernetes for sometime and have struggled with adapting it to our deployment model. A lot of the tools and tutorials want someone to sit and run commands in order to start controllers and worker nodes but that doesn't make sense in our automated environment. What we really want is a way to bake AMIs etc that have everything ready to go and when we do a deployment or scale out it is as simple as starting an instance. This collection of labs lays a lot of that out and I think this is something we can work with.

My guess is it wasn't much of a debate and in actuality they used something like Simulink to model the control system and then had that generate the C++ code for the target hardware. I doubt any car control system software is written by hand these days.

I've seen this prediction about Africa for the past 20 years. And it's probably even older than that. It's not a particularly bold one, in my opinion, but it is a flawed one.

Africa is not a country, it is a continent. Comparing it to India or China (whose economies haven't really paid off for foreign investors as much as you'd think) is a major flaw. China and India have an incredibly consistent society from corner to corner and well organized governments. Africa on the other hand is a few dozen sovereign countries, without a common culture or language between them. They are constantly at war with each other and within each other.

I think in order to extract the full economic potential of Africa you'll need to see unification at levels that put the EU to shame and at least a decade of trusted, non-corrupt, forward looking governance.

I think it'll happen, but not for a very, very long time. Until then, follow the Chinese govt investments in Africa and try to tag along.

That plan is from 2003. Not familiar with the area, how did it turn out?

It identified my thumb as one of a few possible mushrooms...

I was recently invited over a friends house to get together with a few others to discuss bitcoin and bitcoin opportunities. All mid 30s, non tech day jobs and people I would consider intelligent. They had no experience with equities, no experience with forex, and were heavily researching bitcoin mining systems. It seemed as if bitcoin just popped up on their radar and really had no understanding of bitcoin or other cryptocurrencies and I got the sense that they felt like they were getting in on the ground floor. Maybe?

+1 to the shoeshine boy indicator reference in this thread.