skysight-inc/HackerNews huggingface dataset:
> The separation of concerns inherent to microservices is such a great advantage

It is not. Not even close.

You have to manage separate onboarding processes, ensure the standards are completely up to date, ensure that training is extremely relevant and covers every single critical component of the system.

You have to maintain up to date documentation of integration state, data flow, testing capabilities, etc.

> You can bring an extra hand into the team without them having to have to understand other parts of the code to do their job.

That sounds awful.

> won't allow you for example to place each service under its own repo which would also provide you with the ability to limit code access

Let me guess, you are not paying for engineering talent? The notion of having distributed teams for most of the companies is so ridiculous it's not even funny.

What happens if a lead person on team X and Y quits? Are you going to retain a full-time person to manage your deployment process now?

What happens if your budget is cut in half and you need to fire half of the team? Do you expect other engineers to pick up something they have not touched for the duration of their stay without slowing down business?

> That requires a lot more up-front investment, but it's worth it over the long run

None of that is true.
Would have been awfully nice to have a reserved bit in hindsight. 7 bit ASCII was an amazing accident. (Maybe it wasn't, time to brush up on my history...)
> “You are thirty-five years old,” I said to myself. “More than half of your life has already been spent.

Well, the age of the document is showing.
I'll second this. If you're over accommodating with your partner, it's just as detrimental to your own mental health and the health of your relationship as it is with a shitty person. The danger here is that we tend to be more accommodating with people we like than those we don't and so we don't even realize we're doing it until it's too late.
Machrone's Law held from about 1985 through 2001:

"The computer you really want costs $5000."
swing and a miss on choosing new names without prior uses
I have Chrome 58. Wasn't working yesterday, works today.

Also, your page now says "Sorry your browser does not support WebAssembly" in Safari, yesterday it didn't.
Yeah. That's exactly what I was thinking as I read through the list of gotchas.

We've just started using mobx ourselves. There's still a weird contention between events and state that I'm yet develop patterns for but overall I'm really happy with it.
Maritime Ship Tech – Nautilus Labs – Post Seed-Stage Opportunity
We're hiring for two generalist & highly-technical software engineers to join the family in NYC to help shipowners burn less fuel and save money with data. https://angel.co/nautilus-labs-1 https://nautiluslabs.co/

Looking for interesting problems to solve out east? This is your opportunity. Let me know if you're interested.
One star bar: “sorry you feel that way”
I'm okay with scorning every one of them, actually.
It's ok to be accommodating as long as you have learned to be introspective. We all have demands of our own time and money. Introspective accommodating people are able to help others in a generous way while protecting the time and resources they need to help themselves. It's a difficult balance to achieve.

Through experience, I've come to believe that this holds true in long-term personal relationships, too. While many will tell you that compromise is the key to a successful marriage, I think that standing up for yourself and who you need to be usually is more important.

There's a needle on the gauge of life that experiences pressure to move from both directions. When you are too accommodating or compromise unequally, the needle moves towards you and establishes a new norm for expected behavior. Your job should be to push back just enough to keep the needle balanced at a point where you retain a full sense of self and the space within which to exercise it. That requires a strong sense of introspection and can take years of adult life to develop.
It's no more theft than allowing you to own the property under your house.
You can't sell a decent library to stakeholders.
"I want a future where someone can go to a junkyard and yank a motor from a Tesla Model H (you know, the one with the T-top) and plan to pop it into their Reatta EV knowing that the connections will fit."

There's no market for that capability in cars. Some heavy trucks do have it; you can buy some heavy trucks and put in a Cummins or Caterpillar Diesel engine. But for smaller cars, it's not worth the headaches.

Powertrain switches are not impossible. A routine student exercise in serious automotive schools is to put an engine and transmission from one car into another car, making the necessary parts. Stanford and Renovo put an electric powertrain into a DeLorean and made it capable of autonomous drifting.[1]

Even in PCs, there's no market for that. 80% of desktop PCs are never opened during their operating life, and the fraction for laptops is probably lower.

[1] https://www.youtube.com/watch?v=WNIDcT0Zdj4
Wait, you mean everyone cheats? I'm shocked I tell you, shocked!

When the VW story first broke and I learned you could readily control the trade-off between performance and emissions using software in the engine controller of a diesel engine, I knew that everyone would do that. They would rationalize it in what ever way they could "Oh the stomping on the accelerator indicates an emergency so we go with maximum performance rather than emission compliance, it's to save lives don't cha know?"
Drug counsellors overdose on fentanyl while supervising addicts
Faster/Better/Cheaper doesn't cut it anymore – for the on-demand economy
Look at the question the other way: from what at the time did not seem a COTS system from IBM, the lack of exclusive patents and sourcing rights allowed competitors to make those standards into deep facto COTS parts via market adoption of clones that also implemented them.
Well there are plenty of public not run by Microsoft benchmarks that show this same trend: https://www.techempower.com/benchmarks/#section=data-r14&hw=...
Yea, but look how many views they are getting. More views = more advertising money, even if they do get downvotes. Those downvotes aren't their target anyways.
Note that SELinux mitigates the issue with default configuration.
Earthquake artificial intelligence knows where damage is worst
Less Is More – Why the IPv6 Switch Is Missing
If you screw up your PC by tinkering with it, all you're doing is hurting yourself.

If you screw up your electric car by tinkering with it, you could easily kill people.
> there are no chances one can stick a HP cartridge into an Epson printer

This is true, but printers are among the most poorly standardized items of PC hardware. There is a very good chance that you can remove a motherboard, processor, RAM stick, hard drive, graphics card, power supply, fan, or case from one computer manufacturer and use it with another.

And while I agree that our economic system isn't helping in several ways, IBM PC standardization happened much closer in time to the red scare than anything EV related.
If you're advocating for the introduction of variable-length IP addresses then it would have been a nightmare - packet-switching is often done in hardware and that level of complexity would have only added trouble.
Psychology shows: mistake to base our self-worth on our profess. achievements
If you do that in the parent constructor it only really works for a single child and then you're better off not partially evaluating and instead having it pull props.bar at execution time
> In modern horses, the Y chromosomes in stallions are almost identical, reflecting the breeding technique of using a single stallion with desired characteristics to father many offspring.

Could that be true? I mean, could all modern domesticated stallions have "almost identical" Y chromosomes?

Edit: Perhaps over generalizing?

> ... Lippold based his findings on the results of a 2004 Swedish study that showed a particular DNA sequence in the Y chromosomes of 52 modern-day stallions representing 15 different breeds was absolutely identical.

> This doesn't mean modern stallions have no diversity of all, Lippold cautioned. The researchers only studied one part of the Y chromosome ...

http://www.thehorse.com/articles/28083/researchers-examine-a...
Why haven't you done it then?
His entire lecture series, which is available on his youtube channel, is absolutely fantastic and worth every minute. It is probably one of the most engaging and enlightening bodies of work I have experienced in any format.
Very little of this blog post is concerned about performance. We're talking about microservices running on different hosts, and IPC takes the form of a network socket, and typically HTTP.

We're also talking about very, very large scale systems, like hundreds of API endpoints, not ten, with multiple on-call rotations, each assigned their own section of the microservices surface, running in front of customers at all times, without the engineering effort to make sure things are close to perfect before exposing to customers.

What happens here is a combinatorial explosion. 1 faulty service can end up affecting it and its transitive dependencies, but operationally, it's hard to distinguish symptom from cause. Worse, a problem on one team may be cause by an unmonitored problem two teams across the network, increasing time to resolution, as each on-call is woken up to discover the root cause is another layer up the network.

More efficient RPC doesn't solve any of this.
Unfortunately my perception is that IPv6 deployment is stalled (due to inaction by ISPs). In my company we have recently dismantled some of our IPv6 infrastructure because it became apparent that ubiquitous v6 connectivity was not coming any time soon (e.g. we have locations served by Charter/Spectrum, and they have no IPv6 and no plan to deploy it). We've instead deployed a private IPv4 overlay network between our sites and assets using GRE tunnels.

Also somewhat exasperating that the "running out of IPv4 addresses" saga has played out across almost my entire career. I remember attending the CIDR meetings at the IETF in around 1992, for example. So one of the first technical problems I encountered in my career remains unsolved nearly 30 years later.
the trick is to finely calibrate your bullshit meter

Not really, the "trick" is actually contained within the wisdom of the last paragraph of the piece.
Ah apologies mate I was thinking of Mastodon when I wrote the original comment
Why Google Is Leading the Charge in Educational VR
HBO has renewed Silicon Valley for a fifth season
Being accommodating is not necessarily a black or white thing. For me, it depends. I generally consider myself to be a nice easy going person who tries to be accommodating as long as it doesn't hurt me or others. Notice the "me" in my last sentence. Yes, be selfish and then be accommodating. Now, I can be a real jerk if I come across one. Nothing wrong with that.
This question may be a bit too late, but I am curious.

I didn't get through at Google. However, I only asked for 3 weeks to prepare, and I have outside obligations (kids, coaching, that sort of thing). I can easily traverse a binary tree, print all permutations of a set, do DFS and BFS. But I'm not super sharp, especially at a whiteboard.

My review was "not bad, good analysis, but didn't make enough coding progress".

Maybe they were being nice. As I said in another comment, I'm not allowed to know what my scores or reviews were.

FTR, I was a math major, though I did take basic CS algorithms and data structures. So I have a background, but probably further to go than a typical CS major.

I know it will vary by individual, but how many hours, over what period of time, would you say counts as "enough practice" where you might start considering that you probably aren't going to be able to practice enough to do this. Could you ballpark it?

I'd prefer to avoid "unintelligent", but you know, a point at which you'd say, this probably isn't for you, might be time to get some new goals?
4 to 8 hour waits are fairly routine from what I've heard (Western Canada anyways). Not advocating privatization, just pointing out that the Canadian system is far from the utopia that many Canadians tend to suggest (when the topic is socialized medicare in an international forum.....when the topic is discussed within Canada, many people's opinions deteriorate significantly.)
The Best Interface Is No Interface
Long time ago I read the book "The Best Interface is No Interface" by Golden Krishna.

I wanted to start the discussion on how do we see Augmented Reality being part of our day-to-day...

We see these ridiculous headsets like Microsoft Hololens and I wonder if you're going to wake up and put one of those to walk around your home.

It sounds counterintuitive to add a layer of interface thinking that the future will be interface-less.

Question is: Do you see yourself wearing those helmets in your home?
Where are you from? That'll heavily change the answer to your question. For instance, it's trivial for a French person under 35 to get a visa to Canada, but might be harder for other nationalities.
Juiced Boards: Authentic Electric Longboards
The funny thing is that when I think about this, it always comes down to government regulations; when big corporations (whose interest is always to maximize profits at any cost) are allowed to get inside your pocket, your kitchen, and whatnot, and spend billions in learning how to influence our brain's reward systems without little limitations, I am not surprised they achieve so much success, after all, we are limited by our biology, we like it or not.
Not that far off:
https://en.wikipedia.org/wiki/Life_expectancy#/media/File:Li...
On a related note is "reasonable". In English this word is routinely abused. I consider it a huge red flag.

"4+4=11"

"No, 4+4=8"

"Oh, c'mon, Joe, don't be difficult."

"4 and 4 is 8, 11 isn't correct.

"Be reasonable here. OK, let's compromise on 9.5, OK?"
Berlin Germany,
Toronto Canada,
plus some of the Scandinavian capitals like Copenhagen Denmark and Stockholm Sweden.
The problem with "everyone cheats" is that we don't have proof of that. We're seeing proof that multiple companies have cheated so far... hopefully the punishments are equivalent.
The company I worked at did a 2 week long hackathon. Another developer and I built a Ruby gem that creates service objects which integrate nicely into the Rail ecosystem. It was a bunch of fun and over time it ended up becoming a big part of our codebase. We open sourced it and it's done pretty well (https://github.com/orgsync/active_interaction). In fact, I was at a conference and met a guy who's company was using it. It was really cool to run into someone benefiting from my work.
First Science Results from NASA’s Juno Mission
Your router has a firewall, external computers can't just send packets to the internal addresses. NAT is not a firewall.
Sounds like you've got a good grasp on learning terms and acronyms already. Glad to see that the Wikipedia article helped ;)
Woman survives manchester bombing thanks to her i phone
I can relate... I'm not sure it helps, but what you're going through is not uncommon for startup founders.

I know someone who just came out of a job where he was hired to take over most of the day-to-day for a founder in a similar situation. It might be useful to discuss the situation and see what recommendations he has. Feel free to connect via Linkedin and I can put you in touch.
That could happen, but I judge it more likely they'd just live as software instead of physically instantiating into something you'd see on a SF TV show.

And even as software, I predict that new colonists would likely arrive by communications laser, well after the local infrastructure has been built. Why bother coming over during the boring building phase?
It is, but people also admire other jobs and assume they are incapable of doing them.

Regardless, the OP wasn't wishing to own a construction company or manage a grocery store. He was wishing to do individual contributor work in a field that uses his body more. It is not arrogant to want that. OP may find after some months that they are ready to go back to tech, and it seems that would be a good outcome since the burnout would have abated.
I know this is just a metaphorical doctor, but i don't think there are any doctor's who aren't busy
> This makes it hard for people to later upgrade from HTTP to HTTPS, because it breaks all of those references.

While someone else pointed out the rest of the URL could conceivably point to different content, in practice, it seems like most deployments have a 1:1 correspondence and will redirect from http://(.) to https://(.) when SSL is deployed so this is not so critical for the http(s) case imho..
This is the case for ipv6 on mobile data by default. Would using a usb modem result in getting affected by smb exploits or something of the sort?
I compare founding Facebook to be the equivalent of founding Marlboro - highly addictive, bad for your health and provides no social value.

In the end of agree with OP.
If you use QML, Qt uses the browser engine to execute the scripted part of QML/QtQuick. (Or at least it used to when I worked on this one particular project).

That's the core of the discussion here.
To me, it looks like he's stretching the skin on either side of the injection site, not touching the needle. In high school, I participated in a program where I spent a summer in South America giving immunizations. Especially for the subcutaneous needles, which are tiny, touching the areas around the injection site made the shots less painful for children. For kids that were especially fearful, I found that pinching the skin at the injection site, then pressing hard when using the alcohol pad to clean and then quickly giving the shot made the area basically numb enough that the child never felt the needle.
Would argue that you have a tools/service team. The fact that you failed to mention changing what devs and sysadmins consider when "focusing 100%" on their role indicates that what you are talking about isn't the concept of DevOps in the article.

Saying you have a DevOps team is like saying you have Lean team, a Theory of Constraints team, or a Just-in-time manufacturing team. DevOps doesn't say that devs shouldn't write code any more then Theory of Constraints says a guy that paints car hoods should be building brake pads. It is about the fact that they should work together to ensure the organization as a whole meets the goals. Not as isolated units that only prioritize their own goals.

I've seen the same flak about Agile and scrum roles for the same reason. People think they can buy the DevOps/Agile/whatever. Only difference with DevOps is rest is that it is getting more noise.
I wouldn't have bought a VW before the scandal, either. Everyone I know who has owned one has had tons of problems with them. They spend a lot of time at the dealer for warranty service.

Owners of most other brands don't have to put up with that kind of stuff. Even my friends with pre-bailout low-end GM and Ford cars haven't had as many problems.
Hagens Berman’s automotive legal team has dedicated substantial resources to uncovering cheating devices used by automakers. The firm has become a trailblazer in this highly specialized realm, outpacing federal and state agencies in unmasking fraud in emissions reporting.

This is hilarious - this is the firm that made tons of money off the VW case, now they are going after the money and cutting out the middleman (EPA)
Good call out, great. To speak more directly to that particular section, I focus on saying you can't decouple people or systems socially without decoupling them technically.

Trying to upgrade from Netty 3 -> Netty 4 (like Twitter Finagle had to do) in less than a big bang? Say hello to remarkable levels of pain and suffering one has to do, probably shading one's own Netty and pointing other dependent libraries at that shaded version. No matter how much decoupling you try to build into APIs within your monolith, trying to get the thing to build and ship together forces a co-interactivity of teams, coheres everyone to common technical underpinnings and which exposes all folk involved to any of the technical risk attempted by any one team. Decoupling may allow some modularity, some ability to replace X with Y, but it's will always have to be done within a common framing, a common framing that as the project grows will become immensely harder to un-stick and push forward, will be much more resistant to experimentation & great leaps forward.

Any software project has so much diversity and risk budget associated with it: a willingness to innovate technically that depletes with use. Even if you "decouple" you monolith, if everyone has to build and ship together you are going to forever be bound into deep interdependencies. Trying to update a logging framework or trying out a Reactive Functional Programming is going to encounter vastly more resistance when you're working on the same sandcastle as perhaps hundreds of other devs, dozens of other teams. And if it is low resistance? Well then you're in more trouble- your monolith grows boundlessly, with everyone being exposed to the rapidly growing risk and diversity that other teams experiment with.

Isolation, containerization, is a good defense. I think Conway would approve. Apologies, paragraphs above are a bit thought soupy- havent the time to edit.
Don't need to steal them, can just copy them.
It looks like you're just talking about a good, old-fashioned, well-built operations team.

In DevOps there is no "I can't run npm" unless the new guy is building his first personal env.
In DevOps ERRNO scrolling down the screen means your kit is broken and you need to rebuild it to a known, working state, yourself (and crap like that certainly wouldn't be making it into production).
In DevOps the entire organization is on board. Everyone has a role even if it's just feedback or a ring-ring fielding phone jockey and they'll know why and they'll know it's an important contribution because every lost piece of information affects delivery and quality.

If you're automating, integrating, designing, orchestrating, trouble-shooting or just about any other ing-ing you can think of than you're an engineer and you can front that with whatever you like be it systems, integration, quality-assurance, software, application, automation, monitoring, cloud, reliability, hardware, database, support, etc. etc. and even devops, if you like.

The difference is whether the organization you're doing all of your "engineering" for has accepted and/or is applying the DevOps "method".

I've perused some "DevOps Engineer" postings and a good amount of them look like garbage idolization of this or that toolset combined with looking for someone they can beat on until their infrastructure works like they think they'd like it to.

DevOps ain't infrastructure and it certainly isn't ace dev guy running the prod kit and no, it's not about "enabling" developers either. It's an operation comprising the entire cycle of delivery with expectations and requirements from all members.

Given the case of some new startup and they're on the hunt and poised to ramp then what they're really looking for is a savvy engineer (or 12) that can ing-ing all. day. long.

Sadly, because of business overlays and buzz-wordery and agile styles and .. certain software stacks, a more than fair share of time gets sucked right out of the actual developing and operating parts, especially if there's any palatable resistance to acceptance but, alas, it really is just another thing fronting ing.
You do realize every other auto manufacturer is doing the exact same thing? VW has one of the biggest R&D divisions in the industry. If they couldn't do it, nobody else could either.
We only use 32 bits of each 48 bit ipv4 address. The problem isn't exhaustion, it's using DNS to do service location rather than IP.