447 karma · joined August 9, 2018
The regime is getting crazier and they eventually might start cleansing folks who said something online. Or their relatives. You just never know.
I’m really curious how it is going to play out. I’m a bit concerned that our salaries will be slashed, especially if engs from other countries enter the wfh market
Here is one: there is a database written in Java and you need to implement more features. There is 10000000 lines of code in the companies source and new code should be the same. I can go on and on.
Personal advice - if you want growth, drop preferences. When FAANG interviews nobody even asking what is your preferred language as nobody cares.
I’m talking about picking a tool that does the job according to the requirements (speed, memory, debuggability), not based on what some YouTuber said.
We are engineers and paid for results. It help with carrier to embrace it.
I really don’t care what language I’m using if it it doing the job. I use Java, Java Script, Go, Python, Scala when appropriate.
AOP sucks because it is paaaain to debug, proxies are magic. There is Dagger that solve some stuff
So, less magic is better. I will take Java codebase over Scala or Python every time, unless it is a toy script which is 100 lines
IMO, if you want to get a descent job in a large company working on backend systems, you want to learn: Java, C/C++ or recently Go. You will be able to build pretty much anything, from a micro service to self driving car.
If you want to stick to startups, you can do well with anything else till it growth, experienced engineers are hired and rewrite it in one of those languages.
First couple months there were hard. My PRs were teared apart with tons of nits, I had troubles communicating as I was embarrassed.
Dev process was also very slow with a lot of back and forth. I felt I was doing something boring + doing it so slowly I stopped caring.
It was miserable and I quit after a year. Looking back, I glad I did. The company did teach me something, but I also wasn’t compatible with their slow moving culture. Did some very interesting work after I moved on and my carrier skyrocketed.
Department either uses or loses the budget, so, there was a push to make sure nothing is left.
Fun fact, that when I’m looking for a job I will be arguing like you.
Now, being on the other side (hiring folks for a startup), I would argue that some of flags are a bit misleading. Examples: “Undue pressure to accept an offer letter” - interviews are not free, companies are investing eng time into evaluating each candidate and once they find great one, they really want them to join. They also do not want to be part of a bidding war, so it is natural to impose limits (some folks do go overboard). Recency bias also tells us that if you sit on the offer for a long time and continue interviewing, chances of you accepting the first one are going down. And something I learned only recently - offer stage is also part of the interview, it shows how 2 sides will be working together in the future.
“ Not enough clarity about your role” - normal for growing startups. I tell the candidates - here is what we do, pick something you like and run with it. Of course it is biased towards entrepreneurial types who thrive in uncertainty, but that is the state of many startups.
Mostly agree with other examples. One fun thought, they had 60 interviews. Assume some were 1 hour phone screens and some 1 + 5 hours virtual on sites. If we do 50:50, the industry spent 30 + 30 * 6 = 210 hours of eng time + debriefs, outreaches, negotiations, ... I think statistically, it is not in the interests of companies to participate in such marathons as ROI will be low.
CloudSql is a misleading name and a bad product.
Ok, here are some: if you resize your instance you will get a downtime.
There is no support for CDC.
You pay for multi master but failover is painfully slow
If you launch more than one using terraform all except one will fail and will stuck in an unrecoverable state
They broke something last week so our proxies lost connectivity
Whoever thought it is a good idea for complex configs (kubernetes) was wrong
Maybe less aggressive rollout strategy?
If everything is free market, why do we need government?
I know the answer, do you?
Especially is you compare it to other industry giants (hello stack ranking and sports team mentality.)