throwawaybcknd

6 ms·

1.
by throwawaybcknd 2y ago
> What am I doing wrong? I got some very helpful answer to this. The most important one was probably "Just ask the other people there how things get assigned." (And independent of front- or back-end engineering, while reading
2.
by throwawaybcknd 2y ago
Someone has to write the compilers. ...In their spare time, as an open-source project, something to keep their mind alive after a day of doing JavaScript on the front-end.
3.
by throwawaybcknd 2y ago
> Maybe at Google you can get away with The recent example was a large, international company. I mentioned this in the post. > Your job is to do _the thing_ Like I said in the post, I do what I get paid to do, and the idea is to figu
4.
by throwawaybcknd 2y ago
> You haven't described the positions you interview for, If the JD says "JavaScript" or "CSS", I politely decline. > Note that you may not realize they are similar positions, or what it is that they have in co
5.
by throwawaybcknd 2y ago
> Lastly and most simply, just ask employees there what they are working on You are the second person to point this out, and I feel like it should have been obvious to me that this is the easiest way to tell. I appreciate it.
6.
by throwawaybcknd 2y ago
I know "some front end". Some things I have picked up like I always knew them, some things required study, some things I'm not going to be good at, and at this point, I'm old enough to know the difference.
7.
by throwawaybcknd 2y ago
Yeah, in that situation, it's better to get out as quickly as possible. I want to avoid getting into that situation, though.
8.
by throwawaybcknd 2y ago
> I'm hearing "I only do frontend badly and under protest". That's complicated, "I don't do frontend" is simple This makes sense.
9.
by throwawaybcknd 2y ago
> there's the philosophy that good engineers can apply learnings from one domain to another, and therefore a senior is a fungible resource. I see that a lot. I mean, JavaScript isn't hard to pick up, but the front-end is not a
10.
by throwawaybcknd 2y ago
> I would have thought it is much harder to find a back-end specialist these days. It would seem that way. > Are you not working in a team? Unless I am doing a contract job, I'm always on a team.
11.
by throwawaybcknd 2y ago
> why the strong resistance to frontend work? I am bad at it. So they get an under-performing employee with low morale and I get complaints about my work. > It can be helpful for a career if you don't have to frequently tell peo
12.
by throwawaybcknd 2y ago
Cynical but kind of accurate. > One of those guys that gets invited to unwind a particular clusterfuck, gets paid $500/hour and quickly moves on to the next gig. This is a "plays golf with the CTO" rate; I spent some time
13.
by throwawaybcknd 2y ago
> Specialising is only possible in larger companies (more than 500 employees). I think it depends on the company. You get niches at 10 employees. > A smaller company might want to hire a backend expert, but who might have to jump int
14.
by throwawaybcknd 2y ago
> I have encountered the same problem but as a FE engineer who doesn’t do backend. (we should hang out) Maybe we should. I know a good ops guy, we've got a minimum viable tech team. > My suggestion would be to look for info earl
15.
by throwawaybcknd 2y ago
> several times in the past few years? Several times in the past fifteen years, but it was that I got fired or quit. > Do they tell you its because you can't do frontend or is it for performance issues? The times it was involunta
16.
Ask HN: Front-end bait and switch?
53 points by throwawaybcknd 2y ago|74 comments