clintonb

Product managers usually help the team by interfacing with the customer, not just the internal company.

The definition of "massive" differs. Not everyone has $125K laying around to pay the IRS for illiquid RSUs.

An 83(b) election is only useful if the value of the shares is low. The income tax is negligible and the capital gains tax is zero. The price of many RSUs was not low when they were granted, so the income tax bill would have still been higher than many could pay.

Edit: Also, RSUs are not eligible for 83(b) elections.

That's not a terrible idea. Ironically, my plan this evening was to investigate slowness in some actions for one of my projects.

Legalizing hacking seems like a large loophole that will backfire. Where is the line between white-hat and black-hat?

Was that the industry, or the government?

That ultimately hurts customers more than the data breach. Limiting access means less availability for customers. If all the customers leave, you’ve just contributed to a monopoly/oligopoly.

What does it mean for the industry to self-regulate? How do you define industry? Is it telecoms, or all tech companies?

Self-regulation has failed because the cost of a data breach remains relatively low compared to implementing security measures, at least on the surface.

Low latency credit card processing.

Stripe uses Ruby, but not Rails.

Plus-plus-bot does not impact reviews. It’s just a nice way to show gratitude publicly. Folks can use a feedback form to leave review-impacting feedback that is actually delivered to the manager.

We can use editors locally. I’ve used RubyMine for my entire tenure.

I find devboxes hold a few advantages over running Docker locally:

1. We can have multiple devboxes to aid switching between branches.

2. Services are more easily spun up and down as needed. If I’m only working on the API, I don’t have to waste local resources on the frontend.

3. Devboxes replicate more of the service networking (Consul) to aid debugging (versus using container networking).

Services are deployed from a monorepo. Deploys are only allowed for main branch commits that have passed CI. If the main branch is broken, nothing can be deployed beyond the last successful commit.

The job of a software engineer at Stripe is not solely code. The job is to deliver business value, and that requires communicating with others across and outside of the organization. I’ve been at Stripe for over five years. I would not have lasted five months if I just sat at my desk and coded all day.

Engineers at Stripe wear many hats, depending on the project. My best example is Paper Checks. I’ve been an engineer, project manager, sales support, designer, support personnel, docs writer, and even visited lockbox facilities. I learned and did a lot on the project, and loved it. None of that happens if engineers just sit and code. We don’t get all the information about the flow of data and paper, and we build a poor product.

The same goes for internal projects. I was a DRI for a complex rewrite of our system. I regularly worked with six other teams to ship that project. That project doesn’t happen without communication.

I found that Hugo requires a shift in asset organization in the sense that assets are collocated with posts. If your post has three images, those images are in the same directory as the post markdown.

Jekyll keeps assets separated. Your posts live in _posts. Your static assets live together in a different directory.

I briefly experimented with switching from Jekyll to Hugo, but had too much invested—custom plugins and reliance on existing Jekyll plugins—in the Jekyll ecosystem to make the switch worthwhile.

I had this “recall” issue with configuration tools (Salt) that I used a couple times a year. I wrote a README, to resolve the issue.

Define “local”. Outside of Massachusetts (MBTA), I don’t recall hearing much about public transit in New England. The commuter rail probably gets you close to New Hampshire. Not sure how far you get from there.

You maintain the value of openness within internal culture by being open with internal employees. Making the information public is a bonus for the public.

I suspect recruiters used LinkedIn to initiate the conversations. Keep in mind it takes two to tango. The employees opted to talk to the recruiters, go through interviews, and change jobs. The absence/presence of a "Who Works Here" page doesn't change the fact that recruiters will contact employees, and employees may change jobs.

Yep. I have found that some folks get too caught up on the salary number, and wait too late to discover their hourly wage is not as high as it could be since they are working far more than the standard 40 hours each week.

It’s definitely a trade off—work more hours to advance more quickly and make more money—but working 60 to 80 hours per week is cutting your effective hourly wage by 25 to 50 percent.

Those offerings are only for options holders. RSUs cannot be traded; otherwise, every RSU holder has to pay taxes.

I found this on r/fatfire. A poster there uses it to give their children a quick overview of personal finance.

https://pixeldrain.com/u/dsHN33xk

There is no shame in using the tools you like best, whether they be GUI or CLI.

I use the command line for everything but resolving merge conflicts. I really like the JetBrains UX for resolving them!

This post reads as unnecessary FUD. You aren’t forced to use the CLI. If you choose to use it, some workflows are simpler.

The only part of the commit response I care about is the URL to create/view a pull request. It’s pretty easy to ignore the rest.

Logz.io comes to mind: https://docs.logz.io/user-guide/accounts/account-region.html. I’m sure I’ve seen configuration for other services, but haven’t cared as much since usage was sufficiently low and latency-insensitive that the region didn’t matter.

One solution I’ve seen is to allow customer to choose the cloud and region so the managed service is as close as possible to the customer’s existing infrastructure.

Forcing a leader to resign over a bad bet that is not permanently damaging to the company will only make things worse. That leader still has value to the company, and is probably one of the best persons to learn from and fix their mistakes. If you fire a CEO, you throw the stock market into chaos and all of your other leaders become focused on trying to get the CEO job instead of doing their own jobs. You went from one problem to multiple problems.

How should the metaverse be visually portrayed? The VR headset/goggles immediately signal "new technology" to readers. The flat screen metaverse you've described just sounds like Second Life or a video game. It may be more accurate, but it doesn't necessarily capture people's attention.

Flawed game ownership model.

I own a 2013 MBP. I reached the limit of dual booting a while ago, but still wanted to play new games without buying a new computer.

I subscribed to PlayStation Now, and got to play Spider-man for $12 per month and the cost of a controller. I knew going in that, like Netflix, I didn’t own the content and it might disappear.

I had a similar experience with Amazon’s service, where I played Watchdogs Legion for a few weeks. I used the PS4 controller.

I’ve been subscribed to Nvidia GeForce for sometime. I pay $4 per month (yay for legacy pricing) to have a high end machine for my casual gaming. My game selection is limited, but I own what I play. If I choose to build/buy a gaming PC, I’ll have games.

Stadia was flawed because I had to buy a new controller that was locked to Stadia, but games that are locked to Stadia, and subscribe to Stadia. That’s a lot of commitment just to _try_ a service. The idea of locking my game purchases to a single service was never going to fly for me.

Stadia could have been more successful if they adopted the models of Nvidia or Amazon, and just rented a machine in the cloud. The special controller can help decrease latency, but isn’t required.

What’s the relevance of knowing a previous employee count? How does this information “complete” the story?