|
alright, so we've totally lost the "const correctness" context that set this off and we're 100% on some fucken PM's ginned up fantasies about devs separated from that, glad we could post today
|
# ¿ Feb 5, 2020 01:12 |
|
|
# ¿ May 17, 2024 09:29 |
|
Wallet posted:You think the next person to mess with that code is going to read comments on a PR that was merged forever ago next time this comes up? In the original context we're talking about consistency across separate files; I don't know any developers who are likely to catch that, and I definitely wouldn't have when I was mostly a developer. Maybe the world is just too poo poo for your genius. yeah you were a poo poo developer if you can't notice something like const correctness across the vast, impermeable gulf of... "separate files", hth and yes, if I see something done vastly different in two places, i will absolutely pull up a PR for one of them as part of investigating. or ask a colleague. or respond to an explicit request in a PR. if you're not allowing devs time/space for that amount of digging or polish, you're a poo poo PM and org. for a long, ongoing concern like adding const correctness eventually everyone should be aware of the technical debt and the standard folks are working towards and shouldn't need to go digging every single time. or you can just let folks go hog wild, have no standards or expectations, force push to master/prod, and deal with the resultant chaos, whatever im not ur mom
|
# ¿ Feb 6, 2020 23:53 |
|
smackfu posted:Has anyone worked at a big company that acquired a small company and then had to deal with the small company’s senior developers not handling it well? I used to hang out with a HR person whose job was essentially going to the small acquihires and informing them that the Party was Over.
|
# ¿ Mar 9, 2020 17:59 |
|
Volmarias posted:It sounds like you just need to have a channel for everyone who isn't your boss, to say that boss called, everyone do their updates (like standup??????????), and designate the person that calls boss back later.
|
# ¿ Apr 17, 2020 17:08 |
|
the talent deficit posted:ageism isn't really that big a deal in my experience. not keeping up with trends and tech is really harmful to your career tho. always be learning well gosh there's no problems up thru my mid 40's, what could possibly happen beyond that point qsvui posted:unless you work in embedded in which case you can go your entire career knowing nothing but C
|
# ¿ May 5, 2020 20:18 |
|
lifg posted:I’ve worked with programmers in their fifties or sixties (I don’t ask) in literally every job I’ve had over the last 15 years, except at that 2-person web dev company. But I’m not in Silicon Valley or at a FAANG. ChickenWing posted:y'all need to find some less toxic companies, peer review is great if your workplace isn't a toxic hellhole. honestly progressive JPEG's anecdote doesn't even say it was a toxic place before the budget troubles led to layoffs. like are you 100% certain this gold standard of peer review wouldn't bite you in the future if the top-down direction of the company changed? how would you feel if your fair critical feedback was in someone's COVID-19 layoff notes?
|
# ¿ May 6, 2020 16:12 |
|
i directly ask peers what they want put in their review notes and if you don't you're a narc
|
# ¿ May 6, 2020 16:14 |
|
Slimy Hog posted:I'm glad I don't work with you.
|
# ¿ May 6, 2020 17:29 |
|
Space Gopher posted:If your go-to burn is "how can workplace culture and feedback even exist if I can't put them into an excel pivot table" then you might. just. be. part. of. the. problem. Space Gopher posted:If management wants to fire someone, your peer assessment email that says "Joe's a technically solid developer who has excelled under high-pressure situations, but I'd appreciate it if he works on providing more descriptive code review feedback" is not going to meaningfully tip the balance.
|
# ¿ May 8, 2020 16:41 |
|
prom candy posted:When the list of things that only you know how to do grows too long you simply find a new job and enjoy being the dumb guy again for a while.
|
# ¿ May 17, 2020 03:35 |
|
yeah google does it by throwing a shitload of "geniuses" at the tooling problems that inevitably crop up, blithely tossing out "its a safe pattern" without mentioning the other half of the tradeoffs seems irresponsible at best
|
# ¿ Jul 8, 2022 00:12 |
|
Volmarias posted:My dude you need to calm down, Reader has been turned off for a long time now, let it go. lol was that a sensitive spot? i specifically quoted someone else's language about monorepo. not everything's about you, buddy!
|
# ¿ Jul 11, 2022 17:35 |
|
Pollyanna posted:I…what what is even happening here The PM's asking a perfectly reasonable question. "Delete after 30 days" doesn't tell you when the check is implemented or when a user would actually observe a deletion occurring. Do we check the entire spam folder every morning at 8 AM, so a spam email arriving at 8:01 could potentially sit there for 30.999 days? Is that operation done more frequently, like every 15 minutes? Or is there a continuous loop checking every spam email every second to ensure, against all reason and practicality, that the "delete after 30 days" requirement is met precisely? It might sound silly but for certain applications, legal requirements around retention policy might make that the preferred method. But, for a certain kinda nerd, it's really fun to pretend like you can't possibly understand how a "human" uses a computer and continue talking past each other in increasingly histrionic ways!
|
# ¿ Aug 9, 2022 17:54 |
|
ThePopeOfFun posted:I've never been in this situation, but I have been told the way to answer this is, "I will get started on the internal projects. Client projects will be delayed X amount of time." that's exactly what OP said? phrasing might be different but that's the gist of it, and the mental model of dev work revealed in the aftermath was certainly worth discovering
|
# ¿ Aug 30, 2022 23:24 |
|
I always thought the benefit of an intense micromanaging boss was having that person in your corner fighting for your raise, like yeah every staff meeting is gonna suck but... you get a raise is that not the deal???
|
# ¿ Sep 1, 2022 17:28 |
|
downout posted:If it was a high priority ticket then why did it keep getting pushed into the backlog? your high priority isn't my high priority
|
# ¿ Sep 22, 2022 01:03 |
|
are y'all really too dumb to keep 2 loving posts of context around?
|
# ¿ Sep 22, 2022 01:12 |
|
New Yorp New Yorp posted:Also keep in mind that not everyone on earth shares the same political viewpoint as 99% of this forum and some people who work for Twitter may even like Elon Musk and agree with the direction he wants to take the company. yeah i can totally imagine a twitter engineer who's just seething at the success of prior free-speech platforms and is eager to watch twitter turn into Gab, Truth Social, or Parler. musky's other companies aren't really known for paying top dollar either. but after you lop off the folks who know anything and folks who have better options bolt, the company might get desperate to retain anyone at all?
|
# ¿ Oct 30, 2022 15:22 |
|
|
# ¿ May 17, 2024 09:29 |
|
worms butthole guy posted:Dies this advice ever leave to anything other than them terminating you the first chance they get for poor work ethic yeah, the team that just lost a manager and now has a sr manager with 18 direct reports with their hair on fire trying to elevate one of them to the single point of contact? they're in a great position to be immediately firing the most senior person on the team who's capable of moonlighting for the role briefly for mild pushback. they're gonna fire them, and now the sr manager has 17 reports, so obviously it's an improvement. can't see any downsides, they'd definitely throw him out on his rear end first thing for talking back like that.
|
# ¿ Dec 2, 2022 00:53 |