He just told me to rewrite it “without awk or sed” and i was like lol k, 15 minutes later, done.

“Really?”

Hahaha this guy chewed me out two weeks ago so this is super satisfying

Full disclosure because who cares - I was making about $180k at mega-corp w/bonus, 401k matching, pension, etc. But I've been saying $150k + equity is in the ballpark. Most of the startups I've talked to are potentially willing to go that high. But they seem to want superman for that and I don't quite check all their boxes.

I do have a netflix tech screen phone interview next week. We'll see how that goes. I'm not expecting anything.

I just received a rejection notice after stage 2 interview with a company (initial phone screen -> talk with hiring manager). This is for a UI Developer role. The hiring manager asked me about deployments and aws which imo fall way out of the purview of a UI developer role and something I haven't had to deal with yet.

Part of rejection email

I'm pretty sure this is referring to the lack of exp in aws/deployments. I don't think some people understand what roles they are even hiring for sometimes.

$180k and can't write find_first_repeat in O(n)? Jelly.

If you go too low on salary then potential companies will think you’d bolt at first opportunity to make more. Doesn’t seem like seem like developer shortage is that acute at the present time. Could be wrong though. Getting lots of inquires but so are a lot of developers.

is this something that front end react devs do often? is it something that requires anything other than googling the algorithm?

I wasn't trying to say you should ask for less money. I was trying to say that you should only interview at places with enough scale (or VC) that they won't bat an eye at 10-20k difference. Unless of course you really don't want to work for large corp.

Get salary expectations communicated before you go in..

No. Speaking of which does anyone use the memoize-one npm library/have seen significant good preformance results from using it? Longshot I know but somehow server side pagination in my app is in bad shape i.e. "hey I want to get this thing, oh here's your 30k rows UI, gl with that".

I'm not a front-end dev, but are you suggesting that front-devs never write algorithms or write anything nontrivial?

a) Can’t write it in a few minutes the next day after a 7 month road trip where your brain is 100% dedicated to learning Spanish.

b) Believe it or not it’s possible to add many multiples of your salary in value to your company w/o even knowing what O(n) means.

scanners.gif

We have some endpoints on our site that perform searches and enumerate the results, a page at a time. I personally set the max page size pretty high, my theory is, if someone wants 100k results, they're going to get them, either through a ton of small requests or a smaller number of bigger requests.

Anyway, didn't really think about it until someone decided they were going to search something that returned every result, and then go through every page.

There are roughly a billion rows in the database. I added a max page parameter.

(Does your backend really return 30k rows, or is it just that you want to get them all a page at a time?)

I really don’t want to work for large Corp. I don’t want to take 6 months+ to get plugged in. I want to wear more hats and not be pegged as just “the node guy”. I want to build something from the ground up. I want to work for a company that might put up with me building something for a few years, then working part time from South America for 6 months (I don’t tell them that part).

our back end is um.. challenging, in that yes UI can make a request to get all widgets and if all widgets is in the B range (and at this company it is), it will really attempt to do that. Problem is its hard to say what is in that range and when its fine to get all widgets (<1000) and when its not.

Welp market is good but not that good imo. It took a few months but I more or less figured out I was hired into this job with humblebrag a really good total comp because the product I'm delivering will result in 8 figure savings yearly for my company after it replaces various 3rd party products with our internal tool. If you can deliver that kind of value awesome but def have to communicate that.

FWIW - I should know a lot of the CS stuff I’m getting dinged for. I’m realizing it is a definitely leak in my game. But it’s also easily possible to be really productive w/o it.

I seriously doubt most companies have any idea how much a developer is actually worth to them. They just know boondoggles cost a lot and good devs are expensive.

I also think great devs are generally worth many multiples of what they're actually paid. So it's not like the market has anything to do with actual value added. It's all just the least you have to pay for a dev who keeps your stuff from blowing up - like every job.

If you mean after a couple years - sure everyone looks around after a couple years. But my track record is pretty good about staying with companies for a while. I have no idea why they think I'd take an offer then keep looking for something better.

Why don't companies have any problem hiring devs with long commutes? Shouldn't it be the same principle?

If so though all I literally had to do was a) not complain about the commute and b) not give them a number and I probably earn an offer. Argh I SUCK at this. There is nothing else in the interview that went badly. Unless I'm too old.

I don't mean to come off entitled in all this btw. This has been a really humbling experience and I realized I should have been doing a TON more to keep my skills up to date with the latest and greatest, and be more curious about learning more in my areas of expertise as well.

I won't slip into that rut of just doing enough to satisfy my job requirements again.

But why not hire someone who can write code well? I probably spend 30% of my time refactoring garbage, convoluted, inefficient code written by senior devs. These senior devs (age 40+) get away with high flying salaries writing mediocre code (I'm 28). Funny how you alluded to age discrimination.

+1

Seems like you have the financial resources to take some time to rectify this though.

Putting on my cynic hat. From a company's point of view, if they have their choice between a candidate who wants $75K that will probably write crappy code and a candidate that wants $150K that will probably write code that is somewhat less crappy but still crappy then guess who they are going to hire.

I am saying front end devs can right perfectly fine code without ever knowing O(n) and if they do need it for something, it is easily implemented by googling.

Man, I just build paging into everything. If the consumer says he doesn't want it I build it in anyway and make it optional.

My largest project is going into testing. It gets the right answers, runs quickly, and has reasonable functionality. I'm hoping there's not much left to test.

Tell me if you think any of this isn't written well. https://github.com/jackspaniel/guar

Sorry about your experience with senior devs. But I take exception that not knowing O(n) inside and out is correlated with writing garbage code.

What does "going into testing" mean exactly?