Flexport is hiring engineers in Amsterdam
1 by thedogeye | 0 comments on Hacker News.
Saturday, March 13, 2021
New top story on Hacker News: Ask HN: Is there a book that teaches you dark patterns of office politics?
Ask HN: Is there a book that teaches you dark patterns of office politics?
41 by lifeplusplus | 31 comments on Hacker News.
i read a book best described as dark patterns 4 office politics. It was sociopathic. I disliked it.. but here we're. I gotta develop my office political skills asap. share ur wisdom nuggets I've noticed who writes the best code doesn't matter and there're opportunities which no one will offer, u have to take them Laws of prosperity: 1) Prioritize VISIBILITY - ask ur way into bigger meetings show interest in biz/product side, biz start to trust u and u become the crucial bridge - propose new ideas as question to whoever above u'd listen - do value work. emergency fixes and high ROI projects. lots of PRs alone are of no value - give presentations, move cards in trello. updates to manager his/her manager. ask 4 future plans - bigger things udo, more biz and architecture knowledge gets locked up in ur head, more valuable u become - propose & get entire project to yourself. leaving grunt work. massive visibility - go hard on crucial proj. visibility is double edge sword. keep spacing 2) Socialize - do this u're already beating most of engineering team. hangout, talk daily - remember what ppl say - talk about industry - get to know their network in the company - ask questions only they can answer 3) Get transferred to non-eng team - u're THE engineer in marketing, adops... - become go to tech person, do their tickets fast. eventually ask to join their team. u'll have so much industry specific knowledge. 4) Make it hard 4 others to encroach ur territory - 4 new projects structure ur code differently than rest. no frameworks. big files. minimal comments. u get it done in 1 day. - use new tech. most would be too lazy to pick it up and be totally happy to give that part of the code base to u. to mgmt, u're the owner of this code now = more valuable. - use odd conventions & make sure every PR adheres to it. nobody will like that code. goal is to do min work, max impact and have all the cards
41 by lifeplusplus | 31 comments on Hacker News.
i read a book best described as dark patterns 4 office politics. It was sociopathic. I disliked it.. but here we're. I gotta develop my office political skills asap. share ur wisdom nuggets I've noticed who writes the best code doesn't matter and there're opportunities which no one will offer, u have to take them Laws of prosperity: 1) Prioritize VISIBILITY - ask ur way into bigger meetings show interest in biz/product side, biz start to trust u and u become the crucial bridge - propose new ideas as question to whoever above u'd listen - do value work. emergency fixes and high ROI projects. lots of PRs alone are of no value - give presentations, move cards in trello. updates to manager his/her manager. ask 4 future plans - bigger things udo, more biz and architecture knowledge gets locked up in ur head, more valuable u become - propose & get entire project to yourself. leaving grunt work. massive visibility - go hard on crucial proj. visibility is double edge sword. keep spacing 2) Socialize - do this u're already beating most of engineering team. hangout, talk daily - remember what ppl say - talk about industry - get to know their network in the company - ask questions only they can answer 3) Get transferred to non-eng team - u're THE engineer in marketing, adops... - become go to tech person, do their tickets fast. eventually ask to join their team. u'll have so much industry specific knowledge. 4) Make it hard 4 others to encroach ur territory - 4 new projects structure ur code differently than rest. no frameworks. big files. minimal comments. u get it done in 1 day. - use new tech. most would be too lazy to pick it up and be totally happy to give that part of the code base to u. to mgmt, u're the owner of this code now = more valuable. - use odd conventions & make sure every PR adheres to it. nobody will like that code. goal is to do min work, max impact and have all the cards
Subscribe to:
Comments (Atom)