skysight-inc/HackerNews huggingface dataset:
Shopify | Production Engineer | Toronto, Ottawa, Montreal - Canada | https://www.shopify.ca

Shopify is the world’s fastest growing commerce platform, with no plans to slow down. We’re on a mission to scale our platform while simultaneously improving performance, reliability, and resiliency. To do this, we need the help of dedicated, methodical, and versatile developers!

The Service Communication team at Shopify is responsible for defining, coordinating and monitoring all service-to-service network communication at Shopify. As part of the larger Service Patterns group, we work with all Shopifolk to create and maintain a high-reliability network of services that make up the distributed application.

Only a few short years ago we had 20 services running all of Shopify and now we have well over 600. We expect that number to increase over the next few years as we add new features and scale our current service to more customers. Creating a resilient platform for service-to-service communication will give us the ability to move fast and not break things.

If you're into infrastructure & operations (call it Production Engineer, DevOps, whatever) this can be an awesome role.
We're currently on Kubernetes with Google Kubernetes Engine (GKE) and are exploring Istio as our service mesh (with Envoy Proxy as our sidecar). We're also building out client libraries in Ruby, Go and Python.

Apply here:
https://www.shopify.com/careers/production-engineer-scalabil...

- Michael Kipper
This is a well-discussed topic (roughly twice a month on HN, to my experience) so I don't think there's a point in going again over all the reasons for Mars colonization. But making humans better at humaning isn't the reason anyone is advocating. Like you observed, it would be dumb. The reasons range from dreams of exploration, through science, raising morale, creating a backup to mitigate impact of planetary-scale disasters, technology spinoff, to pushing humanity out into the void - where we should have been present for decades now.
> Current cellphones represent a fourth generation, known as 4G, and 5G phones are expected to debut around 2020. They employ much higher frequencies, and these radio waves are far less successful at penetrating the bodies of humans and rats, scientists say.

I'm confused by this statement. 4G uses even lower frequencies than 900 MHz, and this range up to 1900MHz will continue to be used for decades more, 5G or not.

As for 5G itself, as I mentioned in another comment, there's also the issue of carriers needing to install many more towers, which I believe are cancer-causing for anyone living in the immediate area due to the power they radiate.

I also imagine the 5G towers will use much more power than say 3G or 4G powers because if 5G wireless tech can't pass easily through objects, then you bet the carriers are going to "maximize" the distance. How? Through more power. So I doubt 5G will be much safer overall. In fact, I'm willing to bet it will be significantly less safe than previous wireless technologies.

So to ensure companies like Qualcomm and U.S. carriers don't get away with causing millions to die "because we found out too late", like this NYT article seems to be implying about the previous tech, we should already start enforcing laws or starting lawsuits against them and make them pay out billions, if evidence is indeed found (whether through more studies, or through discovery of what the company employees knew about these issues) that their tech was harmful to humans.
What makes you think it doesn't scale?
Common Package Specification
BetterUp | Software Engineer (Full-Stack, Front-End, Machine Learning) | Remote | Full-time | https://www.betterup.co/

BetterUp is a coaching platform that brings personalized professional coaching to employees at all levels. We help managers lead better, teams perform better, and employees thrive personally and inspire professionally. Our mission is to help people everywhere pursue their lives with greater clarity, purpose, and passion, so our product was developed by a team of leading behavioral scientists, researchers, and technologists. We're already transforming the way companies approach talent development at high-performing organizations like LinkedIn, Salesforce, Capital One, Deloitte, and Logitech among many others.

We are an agile development shop that lives and breathes lean startup principles, continuous deployment, and have built culture of engineering quality where each team member is empowered to have an impact on our mission of building a platform for transformational behavior change. Our stack is primarily Ruby on Rails, Ember.js, Gitflow, AWS, and Docker and our principles and practices include:

- Comprehensive test coverage (> 95%)
- Maintaining up to date dependencies (minor dependencies upgraded within 1 week of release, major dependencies 1 month)
- Continuous Deployment (ship early, ship often)
- Performance as a feature (< 250ms 95th percentile API response time)
- "Just in time" Architecture (invest in architecture in lockstep with product initiatives)

We provide amazing benefits (unlimited vacation, volunteer days), but if you ask the team they’ll tell you that the greatest benefit we offer employees is an incredibly meaningful mission and transformative work.

View all roles and apply here: https://boards.greenhouse.io/betterup
1upHealth - Healthcare API Platform | Boston | Full-time | https://1up.health

We just closed on funding and are looking for a CTO, Software Engineers, Sales Engineers, Marketing, Sales and other healthcare experts.
We build Healthcare APIs for app developers making products for patients and providers. We are live with EHR connections to 230 health systems across the US. Over 100 app developers are already using our platform. Our stack is mostly Node, and we are building against FHIR, HL7, & CCDA standards. Please email hello@1up.health
Companies should not be going around offering bonuses to employees for ideas of things to patent. This is a flaw in the system.

If you don't have the know-how to implement something, can you really call yourself the inventor of that thing?

Inventors should be able to create prototypes, and if they're small-time maybe they can form a startup and gain investments.
I wonder if a fix to many "too big to fail" and "winner takes all" market and public/private power imbalance issues, isn't simply this: mandatory split up beyond a certain size.
Sourcegraph (https://sourcegraph.com) | Software Engineer | San Francisco, CA or REMOTE

Sourcegraph is building a better, smarter foundation for software development. Our code search allows you to instantly search across all of your company's private code to find what you are looking for (definitions, examples, error messages, etc.), and our browser extensions give you IDE-like code intelligence (e.g. hover tooltips, go to definition, find references, and more) while you are looking at code in your browser, on Sourcegraph, or on your code host. Software developers at big/recognizable companies around the world already love and use our product on a daily basis.

We are a small team of mostly engineers who love to code. If you are passionate about making the world better through software, come join us!

Stack: Go, TypeScript, GraphQL, Docker + Kubernetes

Code: https://github.com/sourcegraph/sourcegraph
Product roadmap: https://docs.sourcegraph.com/dev/roadmap
Master plan: https://sourcegraph.com/plan
Jobs page: https://github.com/sourcegraph/careers/
I particularly like "...strengths that did not raise animal body temperatures excessively." No sense microwaving the rats to death. For a 70kg person, that exposure (using the rat scale, 105 - 420 watts) for your entire life. Vs a cell phone which has an effective radiated power ERP of about 1 watt[1]. So somewhere between 1% and .25% of the power.

Cell phone signals fall off with the square of the distance so the bulk of the power of a cellphones RF energy that you are exposed to comes from the handset.

[1] "Meanwhile, the total power emitted from the cell phone itself ranges from 0.75 to 1 watt. According to the FCC (Federal Communications Commission), this is an acceptably safe amount of power for a cell phone since their cut-off or specific absorption rate  is only 1.6 watts per kilogram (W/kg). As a result, the power radiated from a cell phone is considered as non-ionizing as opposed to ionizing." --
https://hypertextbook.com/facts/2006/EbruBek.shtml
I believe there is also an etiquette that tells to put a knife down with the cutting side facing inwards towards your plate (ie: not towards your enemy sitting next to you). As otherwise it might be seen as a hostile gesture/provocation.
That makes sense too - as I see it depends a lot on how big the team is that an engineering manager works with, as well as if the team is a product or a platform team, among other factors.
> gross overgeneralization

Yeah I know that's why I put it in quotes. But that's how they're commonly perceived in media and academic institutions.
When you aren't invalidating tokens your app server can serve all static but restricted content without checking with the DB.
The solution does claim to be better along some axes; your statement would seem to imply that you can't work towards a solution to any problem until all of them are solved. That seems like a recipe for never improving anything, no?

It would be like complaining about an agricultural innovation that's projected to reduce starvation, because it doesn't also cure diabetes. I wouldn't want such progress to "just stop" because they're leaving a given problem unsolved.
I'm glad to see Quark picking up where Electrino left off, I'm very interested in those projects. However both of them are not production ready or even close to production. Plus now you're dealing with the same issues you get on web where you're coding for multiple browsers. However, if you're going to be using electron or similar then you're already used to that
Cerego | Engineering | San Francisco | Onsite | Full-time | https://www.cerego.com/

We are an educational technology company changing the way people learn. We are looking for:

Senior Full Stack Engineer
| Senior iOS Engineer
| Infrastructure Engineer
| Android Engineer

Tech stack: native iOS and Android, AngularJS, Ruby on Rails, AWS

Apply online at https://cerego.workable.com/
As for 1) I literally meant pre-IPO. Companies that are not publicly traded. Even very very large ones(e.g. Uber) tend to issue options instead of RSUs. When you get hired, the value of those options is a big 0 - that's where they set the strike price. You can't really compare options to RSUs. You can't assume the stock will go up 50% in value or anything in particular. So they are hard to value as anything other than 0 (I'd love to hear other ways you think about it)

Transparency is good. I'm not exactly against this information. I mostly wish it were available in a way that applies to the rest of us.

Also, I wish it didn't make me feel bad. Call it mindset but salary discussions tend to.
Nerves around the brain, rather than the brain itself.

https://en.wikipedia.org/wiki/Headache#Pathophysiology
Yeah I think I made my point kind of stupidly.

Email is just "there" at this stage. Your emails appear in your inbox and you're not really constrained by a provider.

I was taking aim more at the comparison with twitter and facebook which require constant engagement.

With email you just get it the way you want it, on your terms mostly.
> “If you put a drop of love into Twitter it seems to decay but if you put in a drop of hatred you feel it actually propagates much more strongly. And you wonder: ‘Well is that because of the way that Twitter as a medium has been built?’”

No, it's human nature. Stop blaming companies for the imperfections of the human race. If you put us into large groups, we will inevitably gossip, bicker, argue, and kill each other. We've been doing it literally since we were banging rocks and sticks together.

The delusion that technology feeds us, and it is especially potent in America, is that there is some higher power leading us all to be terrible people online, and that technology should be able to fix the problem.

But technology can't fix the problem. We are the problem. We also evolve incredibly slowly, and we're competing against technology that evolves in a matter of decades. We are too inflexible as a species to be compatible with the social effects of technology.
I'm not saying it's the only evidence required but just that it counts > 0. I don't think that should be particularly controversial.

Particularly when you get many people saying the same thing independently, in a social context rather different to that of Salem in 1693.
Interesting. I will try to think that way. BTW I’m quite self-disciplined pretty much every other way and I never thought much about it, but I think that’s how I normally am. If it’s not food or caffeine...
There is not much to say, it seems a no-frill business that stays afloat doing grunt work, just like the majority of b2b IT ventures out there. Managers are probably having their perspectives a bit skewed by recent fashionable fields, something they will not be able to sustain economically.
There is no agile, no source control, no meetings

If you stop there, it really doesn't sound so bad... Is there a way to present this as an opportunity for reasonably experienced introverts to "own" something without too many interruptions? Or is there enough incidental stuff that it doesn't work like that in practice?

(The "no source control" would probably bug me a bit, but presumably not much stopping someone running their own?)
They only seem to support SMS 2 factor, yippee...almost worse than just have a really good password.
Common | Senior Software Engineer, Senior Frontend Engineer, Engineering Manager | New York City, NY | Full-time | Onsite

Common is a technology-driven property manager building a better shared housing experience. More Americans than ever are living with roommates. We keep the good parts of shared housing while removing the annoyances. Being a Common member means never having to worry about cleaning, moving furniture, or splitting the bills. Common members know their neighbors, meet new people, and save money. We currently operate coliving and traditional apartments in New York City, Chicago, San Francisco, Seattle, Washington, D.C., and have new cities opening soon.

On the tech side we are on a mission to create software that delights our members through community and access to services that enrich the living experience. In additional to the technology we provide our members, we are also building technology to scale property management, operations, and logistics for our internal stakeholders. Our digital product charter is to build software to support the next 100,000 members living in Common.

Common was founded by General Assembly co-founder Brad Hargreaves and has raised over $65MM in venture funding.

I'm hiring for multiple positions and would love to chat if you are interested in our mission:

Senior Software Engineer: https://boards.greenhouse.io/common/jobs/4114701002

Senior Frontend Engineer: https://boards.greenhouse.io/common/jobs/4114729002

Engineering Manager: https://boards.greenhouse.io/common/jobs/4114710002

All Open roles: https://boards.greenhouse.io/common
Don't microwaves work by literally boiling the water in food, from the inside out?
Citymapper | Software engineers | Full-time, ONSITE, VISA (for senior engineers), London

Python / Go backend engineer https://citymapper.workable.com/jobs/6531

Senior Web engineer (full-stack / React) https://citymapper.workable.com/jobs/629000

Site Reliability Engineer https://citymapper.workable.com/jobs/13967

and other positions - check out citymapper.com/jobs
-

We are looking to hire great engineers - Check out our blog at https://engineering.citymapper.com to get a better idea of what we are doing.

We need great engineers who are up to the challenge of making cities usable. Our multimodal transport app helps people to get from A to B and we are also running mobility services in London (https://citymapper.com/smartride) We are also looking for site reliability engineers to help us scale our services to millions of users.

I am Marius (head of backend engineering) and you can contact me directly at marius@citymapper.com (no recruiters!) if you have any questions. Otherwise please apply through our website: https://citymapper.com/jobs
I suppose it is possible that many people find a system with some inefficiency to be practically nicer, easier, and more functional than one with absolutely perfect utilization, allocation, and efficiency.

efficiency in a systems problem is almost never easy, and it requires everyone who participates to put forth their fullest effort. It is telling to me that when people are unconstrained by space/cost/time, they don't tend to create extremely efficient situations, but in fact prefer those that intentionally less so.
Location: Toronto, Canada

Remote: Ambivalent

Willing to relocate: Yes

Technologies: C, shell, Rust, Python, networking, others

Résumé/CV: https://alxu.ca/resume.pdf

Email: see resume
We're currently using it and it's got some pros/cons, though the cons are a little scary. Jepsen did an evaluation of Dgraph[0] shortly after we started using it and I can confirm seeing a lot of what was noted. Dgraph is _fast_, but there are problems with the underlying data store (their own DB called Badger). Some of those issues have been remedied, but many still exist.

As a graph database, it has some non-typical tradeoffs. You can't easily discern incoming edges and there's no true node deletion. There's a pretty narrow happy-path where the DB works as advertised/expected, but it's just a fairly young DB from an understaffed startup. Probably worth waiting a year or two for the kinks to be ironed out.

[0] https://jepsen.io/analyses/dgraph-1-0-2
Rewiring Plankton. And Reality
How else are you supposed to get to your money?
Battlefy | Engineering | Vancouver, Canada | Full-Time | Remote

Battlefy is the leading esports technology platform that serves world-class companies like Amazon Game Studios, Riot Games, Blizzard Entertainment, Nintendo, Coca Cola, Red Bull, Alienware, Mancity, and many more. We power their esports infrastructure (managing tournaments, prizing, teams, real-time stats, seeding and brackets, content creation, and communications).

We're looking for motivated engineers that have a passion for esports and gaming. React/Angular/NodeJS/MongoDB/Postgres.

Apply here: https://battlefy.workable.com/j/81C755C92B
The clip they show him working on is the short that's shown in the Ghibli Museum!

I absolutely love almost everything from Miyazaki, but I wonder what's it like to work with/for him. This short trailer makes it seem he's probably a difficult man... like all great authors, I guess.
Guess Glassdoor is doing it's job.
Much obliged. It’s a surprisingly alien concept for me with food, yet not elsewhere in my life. Odd, come to think of it.
Depends on where you live, I suppose. Large cities I've lived in have all allowed commercial spaces at ground level, but there are a ton of regulations as to what you can do in them.

Doing nothing but knocking down a wall and putting up a sign is a sure way to get shut down by the city, along with some likely hefty fines.

Edit: another barrier is building insurance; if a building is all residential, and someone wants to convert ground level space to commercial use, the insurance company has to re-assess the risk and premiums they charge due to the increase in people coming through, if nothing else.
The "battle-tested" argument is becoming less and less obvious. As for being error-prone, I've seen a lot of people set up their session cookies incorrectly/insecurely when using traditional session tokens (and framework-provided authentication libraries), so I'd guess the two approaches are about on equal ground in the "error-prone" department.
On Cryptocurrency Communities
I always make sure I can still compile and execute the code. If I can't, I get someone to update the README files so that I can. That also helps me make sure new members can be onboarded.

I also do off-critical-path features and bug fixes. That said, I did write a fair bit of the code base before taking a more managerial role, and I contribute to discussions about what will make the thing faster.
When I was growing up in Oregon the biggest forestry controversy was a halt to logging in national forests to conserve habitat for the endangered Northern Spotted Owl. Outside of the Portland area, it seemed like most news outlets and people were against this intervention. I kind of went along with adult sentiment and thought that the federal government shouldn't destroy our state's logging jobs with their meddling.

As an adult, I have a completely different perspective. Loggers had been cutting down old-growth trees faster than they grow back for generations. If they'd been managing the forests sustainably all along nobody would have forced them to do things differently. Blaming environmentalists and government for the end of old growth logging is like blaming the gas gauge for your empty fuel tank. The underlying resource was depleted and the logging community plan was, apparently, to ensure it ran out completely before changing.

https://en.wikipedia.org/wiki/Northern_spotted_owl#Controver...
Also note that there are risks of microwave radiation apart from cancer: https://www.sciencedirect.com/science/article/pii/S089106181...
Oh, right, my carrier doesn't support that for my device yet, so I forgot about it. Does it turn the radio all the way off? I guess it would, since WiFi will just supplant all the cell radio's functions.
This question goes deep. You should check out James C. Scott stuff if you really want to broaden this. Your parallels of communities as governments/states/taxes/loans are invalid, IMO. I've ripped audios of a bunch of presentations by him on the topic, do this and see if you'll still frame things the same way, I think not.
Mixed use is precisely what zoning regulations are pushing for these days. If there were no zoning laws developers would only build whatever makes them the most money (from what I gather this may be mini-storage in all honesty).
Edit: also elder care. I see developers do all sorts of less than honest things to win the approval to make an elder care facility.
Maybe the rejection letters provided more details as to why they thought his argument was invalid which isn't captured in the article. If they did not, it seems to me that the reviewers didn't offer specific criticisms which would have been more useful.

I find these questions and paradoxes that illuminate the limits of logical reasoning quite fascinating.
If you break up the big platforms today, you'd need to do it again in 5 years.

Big platforms exist because centralization is convenient for users. If they disappeared new ones would be created, for the same reason the original ones were created in the first place.

I have yet to see a proposal for a federated platform that appeals to average people outside of the HN/open source community. And even if you could solve that problem for social media, how would you come up with a federated replacement for something like Google search or Amazon shopping that is anywhere near as good?
We have an EM who took on grunt work (but critical) so the team could focus on tasks on the charter of the team. Personally I really appreciated that because otherwise the team would have had to spend a few sprints doing the grunt work. His rationale was "You guys are doing great work and your momentum is great. I don't want this stuff to slow you guys down. I'll take it on" +100 for that attitude.
I mean I'm not saying give ultimate judicial authority to any accuser. Just that we should be able to respect our peers' opinions as being worth something more than "not at all". Granted, I should have perhaps made that clearer rather than slipping into rhetoric.
You owe them nothing. Keep your good advice to yourself. You will not get anything from them in return.