golondon

Man, just let it go. More you try to block Epic or any other, more you are pushing people away from yourself.

Be Apple, innovate, give us second iPhone moment so you wouldn't worry so much about revenue drop in services. Or make payment via Apple so good, your customers would go for it even with price difference. Just stop stupid, monopolistic tactics.

Do I still need to worry about vacuum and bloat or does Neon intelligently handle these?

Just for the tradition, I would like to leave a comment: "I don't see how this will work. There is nothing here you can't do with Postgres schemas"

Whatever you are most productive with.

10x = It takes 10 people to clear the mess they left behind. In my 15 years of career, all people I have seen who were referred as 10x were the people who took terrible shortcuts to deliver whatevs they try to deliver and when it comes to building on top of that thing everyone who touched that hot mess had a miserable life.

It increasingly feels like the decisions taken and the work done at Shopify API / Libraries / CLIs / Docs etc are done for promos, rather than thinking about DevEx of people who try to build reliable product on their platform.

I notice this pattern of shoving nodejs / js, especially react through people's throat for the apps developed on the platform. Polaris, Session tokens and all the boilerplate apps the CLI generates are great examples of that.

I would rather having Polaris as CSS framework + some JS bits in vanilla-JS, Auth + Session tokens as just as a small JS library. But instead I am forced to use React. I know Polaris is also available as CSS only but that's almost impossible to use as it's not designed for human use really. Or Bridge exists as a library but for many cases it's just way too bloated and documentation for non-react version of those things are not so good.

I think the SRE role in Google is the best implementation of the role. They have 2 tracks called SRE-SWE and SRE-Systems Engineer and actually both are expected to write software majority of their time, only difference from normal SWE is where you focus I guess.

However, your life as SRE after Google if you don't take an SWE role can be very different to what you experience at Google. The reality is in majority of the companies system administration teams labelled as SRE as hiring tactic and code base quality, the type of things you develop, amount of project vs toil varies massively towards negative.

Seriously, what's the difference from the last time this is shared at HN?

Postgres has index concurrently which is better or few other instant things which MySQL 8 also has but you still need to be careful.

But some things like adding a column with default value is still hard.

https://www.braintreepayments.com/blog/safe-operations-for-h... this article has a good guideline on this.

No, especially on large tables with billions of records. They make online schema changes impossible. More details: https://github.com/github/gh-ost/issues/331#issuecomment-266...

Whether Leetcode is necessary can be discussed but this person doesn't add anything to the discussion. Almost disconnected 7 paragraphs of text and the conclusion is FAANG and S & P 500 needs to find a way to assess without Leetcode.

It clearly works for them so they continue doing it and able to grow their eng organisations to thousands of engineers. Any other solution to this problem wouldn't be without its trade offs. If he really wants to contribute to tech industry he is more than welcome to found his own company and hire the way he wants, instead of saying "I don't like this FAANG find a new way!".

I am sorry for the experience, I hope she beats it quickly.

I feel like the secret agenda in the UK is making NHS so bad, people would beg to have some sort of health service, costs a fortune like US but at least cuts the pain.

So, although I understand where you are coming from and the naive belief that they want to improve the service, I think for the politicians it’s not the case. They also don’t have courage to come out and say we want to make NHS private, as it would cost quite a loads of votes.

This is how I am able to explain the service quality, stupid phone calla you need to make and totally inefficient management.

Which Uni you had the masters from? Would you suggest them?

thanks

I skimmed through it but still didn't see any part describing how is the local dev env is? Let's say that you work on a service that does something for ad serving, how do you write code for that and test it?

I understand unit tests and e2e tests are used but what I'm referring is just simple opening web browser, navigating to the localhost:3000/foo/bar/something and seeing if it's ok, I found this as much faster feedback loop while writing code in addition to the tests. Can anyone from Google share that?

The problem I see is especially in small / mid level companies' contexts, directly trying to jump to DDD usually ends up with a really weird, half-assed implementation. On top of that, it's usually hard to get people up to speed with this kind of architecture. If you're new in the domain, changes take longer as well. You can't go back to the white board every time, re-model your domain and do big changes to it every week.

With classical MVC + Transaction Scripts you can go quite a long way, as boring as it is it can scale up to 500 people working on it. When the time comes, you will have waay more knowledge to your domain and would be able to go with this kind of approach while going towards service oriented architecture or while implementing those boundaries within your monolith like Shopify does.

Otherwise you just waste your time for the things that don't give any benefit to you in short / mid term at all. On the long term nowadays it's really rare people stay at job that long or if that time comes your company will have enough money to throw money into the problem.

Hi, looks really great! Thanks for this great piece of tech!

I have a question regarding the migrations, in the website you say it's safe to run them with automated flow, we know it uses Postgres under the hood and we know that sometimes migrations on large datasets can cause downtime in the database clusters. How do you handle them? I guess since you don't have a backing "users" table for a "User" model adding / removing fields is not actually happening the same way it happens in a normal relational database, thus it's not a blocking or resource consuming operation for you?

Yeah, I was talking for the perm roles. If you go to the contractor route, 600, 650 is quite doable. For higher as you said, it's networking, how people see you and what kind of projects you delivered. Depending on the person, it can be something even harder than the leetcode grind. But overall, I would agree.

Speaking for London, if you would like to have £180K+ FAANG or Hedge Funds / Trading is your only option and unfortunately they ask leetcode questions. Some of them go crazy and ask hard, some like Facebook ask easy / mid but want you to be quickly come up with the answer.

There are eng offices of soon to be IPO'd startups such as Stripe or Intercom in London, those don't ask something you don't do in your day to day job, however comp at this stage would be base + maybe bonus + stock options. You can never know when that stock option will turn into something, so in a way it's even worse than lottery, at least in lottery you know the date to check if you get rich or not.

There have been few IPOs from London startups like Deliveroo, but I would say they perform pretty badly and things are not going well for people who relied on the return from there.

So, I would say Yes to this. Unfortunately.

I had pretty similar story when I was at Apple, as an SRE. I haven't been in the company for long time, so just before he was making prep for putting me on PIP, handed my resignation, with a salary and title bump.

Sometimes you just join to a company thinking "It's X at the end of the day, how bad it could be?", from the first hand experience I can say it can be absolutely terrible. So if you directly interview with the team you're going to work with, like you do in Apple, and if you didn't feel like you would enjoy working with the people you saw in the loop, trust that feeling. It possibly tells you the truth.

I guess with 8 something years at Meta, if the RSUs were not spent stupidly, considering the stock appreciation and the refreshers, it would be safe to say this person's net worth is at least $2M.

Thanks for the answer!

Great work!

The part I don't understand is how do you find the motivation to write such time taking things? Outside work? At work? I guess you don't know whether this would be profitable or not, how do you stay motivated?

is this the latest pivot? are we going to see another completely different business in 3 months?

It's for the SRE roles. The continuous change of frameworks, languages etc happens in SWE world as well but I guess the difference is when you're making those changes you have necessary support around you. Your team / group has product manager so you know what feature needs to be there, your team lead negotiates those so you don't need much convincing all the time, your product marketing manager keeps rest of the company in the loop. In the SRE world, you pretty much need to all of those, while doing fire fighting. So the problem is not the change itself, but how it's done and amount of effort it requires I guess.

I experienced this in 2 FAANG SRE orgs, might be the case we had not properly thought SRE org.

Ok, so only Apple can have sub-app-market in their apps inside iOS?

Is there anyone using it in a schemaless way as in you provide a SaaS service and your customers can send you JSON with various different fields? As far as I remember Sentry uses it this way and people leverage arrays for such things?

Ok, but most of the time you would like to test that change on a copy or almost up to date replica, to see measure things like how long it does take. If you were copying the data, with things like PII filtering, to the branch development database and allow folks to test it there it would be even more amazing. Great start tho!

Aren't schema changes are actually a big problem when there is a huge amount of data in the table. Adding a column / index to a table that has 500M rows in it is usually the pita. This is definitely something on the right direction, but would love to see this supporting this with the data itself.

Thanks!