Graphite and stacked diffs are awesome! I really miss Phabricator from my time at Uber, and I've been sad ever since that nobody had built a superior developer experience based on the same concepts.
Location: San Francisco, New York City, Los Angeles, or Washington D.C.
Remote: Yes
Willing to relocate: Yes
Technologies: Python, Rust, JavaScript, TypeScript, C, Go, Java, SQL, Terraform, TensorFlow, Amazon Web Services (AWS), Docker.
Résumé/CV: https://www.linkedin.com/in/jamesmishra/
Email: j@jamesmishra.com
I am LOOKING FOR A NEW JOB as a backend / full-stack software engineer.
I have 10 years of experience. I've founded 2 startups and worked at places like Uber and the US Government.
My top open source projects:
- https://babycat.io , a Rust library for decoding and manipulating audio files--with bindings for C, Python, and WebAssembly.
- https://provose.com , a new way to manage your Amazon Web Services infrastructure. You describe the containers, databases, and filesystems that you want to deploy, and Provose automatically calculates the necessary security and networking configuration. Built with HashiCorp Terraform.
Most certainly.
Depending on the type of world we're in, it might also have freed people to pursue more fulfilling calls.
On the flipside, it might have removed multiple jobs for people who may have had entirely satisfactory lives.
It might have been a important plant and the damages done when it breaks down and the surrounding society discovers they both cannot do without it nor rebuild/recover from it may be far worse than the "cost" of running it at a higher degree of manual operation.
> Depending on the type of world we're in, it might also have freed people to pursue more fulfilling calls. On the flipside, it might have removed multiple jobs for people who may have had entirely satisfactory lives.
I feel like the fetishization of the "job" is detrimental to society and individuals. I've been in a situation where I could really quickly develop automation that would replace a team of 15 people hammering on spreadsheets all day. The project was canned because we didn't want to put 15 people out of work. The way I see it, there were some distinct outcomes for possible decisions:
1: The automation project is canned. Nothing changes.
2: I get the automation done, 15 people are out of jobs. They have to seek new employment, or otherwise find out what to do with their lives. They are displaced in an unpleasant way, and the lives of many of them may be heavily damaged for at least the short term. The company saves over a million dollars a year.
3: I get the automation done, the company re-tasks the workers to other parts of the company. They aren't out of jobs, but they have to adjust and re-train and learn new things. Some are happy, most are annoyed, but nobody is seriously hurt. Some people are unable to adjust and maybe eventually get let go.
4: The automation is done, and the company continues paying the employees who now are being paid to do nothing at all. They can relax, or work on hobbies, or whatever they like.
The interesting part for me is that 2 has the greatest advantage for the company, 3 is a good compromise, 4 is the best scenario for the employees without even harming the company more than the cost of my time (which isn't really all that expensive in the big term; less than a day's pay for all the employees together), and 1 is the worst case scenario for everybody, but they chose 1 because the "job" is sacred. 1 and 4 are nearly the same from the perspective of the company, so rather than improving anything, they choose to be inefficient, wasteful welfare.
People want welfare to exist, but they don't like the idea of "freeloaders", so they force people to do useless, Sisyphean work. It's extraordinarily wasteful.
Maybe life could be better for everybody if losing your job couldn't completely destroy your life. We could automate things and improve things faster without having to hold back progress because "people could lose their jobs", we could dismantle destructive industries that currently are kept afloat because "Hey, that's 80 thousand jobs!" People could leave jobs that they feel are ethically wrong, rather than being trapped into doing something they think is evil because they need to feed their families.
>4: The automation is done, and the company continues paying the employees who now are being paid to do nothing at all. They can relax, or work on hobbies, or whatever they like.
I'm not sure this is a great outcome. It soft-locks them into their current position without any great motivation to better themselves. It also creates resentment in those around them. When the company does eventually let them go, only the most forward-thinking will still have useful job skills and can find another job.
Sure, they could quit or request a different job, but how many people can recognize those mental problems coming ahead of time and avoid it? Most people are going to be fat and happy and do nothing to get ahead. I don't even blame them. It'd be incredibly tempting for me, too. In fact, since I've been at this company so long and basically stopped growing, I kind of already have fallen into that trap. It's a pretty comfy trap since I like my work and I get paid pretty well for it. It's just not forward-looking at all.
Tangential: It looks to me like you've got some impostor syndrome creeping up on you. IMO you should do some game modding or addon development. It's a piece of cake, you'll look like a genius to your gaming buddies, and you'll have fun in the process
I mean this is the idea of Universal Basic Income, but with that also comes it's own set of problems.
[1] Who, then, programs and builds the next generation of automation... innovation would have to continue. These people would still go in for the grind, I guess it would be for more money but at some point would the tiered tax rates make it worth it?
[2] This would only be for certain sectors of jobs. Waitstaff is still going to exist, and a whole realm of the service industry. This would just lead to an exploited workforce, or striated (more striated) population filled in by immigrant labor and other "invisible" labor groups.
[3] Our dependence on machine infrastructure becomes ultimately vulnerable to attack from foreign intelligence and private actors and we are far from able to defend against it.
EDIT:
for the record, I have argued for UBI and am not against it in the past. I am still for it but not on a huge scale. The UBI that I have argued for would be a $1000/month UBI. This would be a replacement/supplement for SSI, disability, childcare tax credit, school supplies, food stamps, etc. It is not enough to live on but a support system for emergencies and savings.
A big problem is that most people don't know how to handle that kind of freedom. The social world most people exist in won't accept it. I don't know your life but I think a lot of people who suggest things like your [4] imagine a sort of extended vacation, and maybe for three or six months or so, it can be. For the long or indefinite term a better analogy would be prison.
Company B does the automation project. They can offer their services for a million dollars a year less than Company A. Company A is eventually outcompeted.
"From time to time, I consider shielding my website with Cloudflare's services. I resist the temptation, because I strongly suspect that, despite Cloudflare's current good intentions, in the long-run, this is playing into the hands of the corporate-controlled web. Relying on commercial web services limits the freedom we have as personal website owners. Once they have us relying on them, we are forced to play by their rules, and at that point the battle is over. We may not have realized it yet, but we have been captured. Unless we manage to free ourselves, in a short time, we will be working for the enemy. [...]"
Just right within the last few days Cloudflare's DDoS protection has started blocking older and/or niche browsers, so all I can say about them is #*'@~?!§%$§#@!!
While that may very well be true, it's also wildly impractical. I would imagine the outcome of that stance will be the skeleton meme "still waiting and google still DDoSes my site."
If anything, locks are hard so if you can do parallel code that doesn't require it (essentially embarrasingly parallel or the like), it's better. It doesn't fit all use cases though.
Honestly, if things are slower, not really mission critical for speed, but are easier to reason about, it's probably worth it to keep it simple and even sequential.
