|
the talent deficit posted:i like one commit per pr, whether you get it from rebasing or from squashing on merge. that way the thing that was reviewed is the thing that was merged and there's no opportunity to revert part of a merge or whatever That makes commit messages entirely unhelpful, though. I'm not advocating that you leave the random "WIP" messages, but if a PR is only one commit and it touches a bunch of different things how in the world do you know if the work is appropriate? At current job, on my team, we do light-weight PRs which give you the nice advantage of not having to worry about too many commits (ours average 2-4) and keeping the work scoped to very small changes.
|
#
¿
May 9, 2017 13:10
|
|
|
|
| # ¿ May 10, 2024 05:55 |
|
|
Pollyanna posted:I feel kinda bad just going home at 2~3pm whenever I'm in the office, cause there's literally nothing to do on my team right now and my time is better served somewhere other than an office chair if this is how it's gonna go. I know it sounds awful and lazy, but seriously. I'm gonna lol in a sad way for you when you get put on a PIP because you're "just not putting in the work."
|
|
#
¿
Jun 8, 2017 04:17
|
|
|
I like my open office because I'm really friendly with the people who sit near me and the whole office is non-sales or marketing so it's pretty relaxed generally. 
|
|
#
¿
Jul 22, 2017 19:09
|
|
|
Or, and my guess is this is more likely because goons, they're the kind of people who can only work in perfect silence and take that deficiency out on coworkers.
|
|
#
¿
Jul 24, 2017 14:32
|
|
|
If having your own office is the deciding factor in taking a job or staying with a company then you should probably just leave because there are clearly enough other red flags if that's your sole decision point.
|
|
#
¿
Jul 26, 2017 14:01
|
|
|
Pycharm is an assemblage of plugins and features that are available to the paid version of IntelliJ IDEA.
|
|
#
¿
Aug 20, 2017 18:10
|
|
|
Pollyanna posted:love2get inundated with Slack alerts about bugs found in my PRs and side effects from other tickets getting deployed while I'm off for two days to interview at a different company. Real good reminder of why I'm leaving. Your code not working and being called out for it is a good reminder of why you're leaving? If that's the case, unless the call-out was exceptionally rude you're in for a world of disappointment no matter where you go.
|
|
#
¿
Oct 5, 2017 22:48
|
|
|
Hughlander posted:Depends... I dunno, in my mind that's sort of part of what you get when you put Slack/Hipchat/Flowdock/whatever the gently caress on your phone. You can 100% ignore every single message that comes in while you're out of the office. It's easy. You can even put up OOO statuses in Slack (I'm sure the competitors have the same feature) that changes your notification setting so you don't get bothered unless someone DMs you and even those you can turn off. When I go on vacation I disable Slack notifications entirely at the OS level. What I'm trying to get at is that if you get annoyed at things that fall in the scope of everyday working life, the problem might be you (Pollyanna) and not the job or coworkers.
|
|
#
¿
Oct 6, 2017 12:16
|
|
|
Moved to a new team and welp stand-ups are now 15 minutes minimum where we go through currently in-flight tickets and points are time-based with everyone having 20 arbitrarily assigned points per sprint. Luckily I'm in a position to change this poo poo because goddamn that's bad.
|
|
#
¿
Nov 7, 2017 00:34
|
|
|
Fwiw I used to work at a shop where I had a windows desktop that had McAfee installed and it chugged whenever I tried to use IntelliJ. Turns out every time IntelliJ tried to execute a jar file, McAfee decompressed it to see if there were any suspicious files in it.
|
|
#
¿
Dec 15, 2017 20:13
|
|
|
A lazy question is a bad one. That's about it. Anything else I'd just varying degrees of good and if you're so petulant as to passive aggressively respond to coworkers that ask non-lazy questions you're part of the problem.
|
|
#
¿
Jan 23, 2018 18:09
|
|
|
Keetron posted:General question. That's been my experience with contractors as a whole; they're firefighters more than anything else. Their job is to right the ship and bring any kind of sanity to process and/or a codebase. I think you'll find slim pickings if you're looking for contracts where you're not working with garbage code or a team that ultimately doesn't take your advice or simply blames you for their problems. Just charge more and laugh all the way to the bank.
|
|
#
¿
Jan 24, 2018 13:22
|
|
|
Pollyanna posted:Even a benign “we don’t have anything for you” is alarming and makes the engineer think they are superfluous and therefore about to be fired. It’s especially bad when it’s a new job. I would even take a large backlog of stuff to do instead of having nothing to do, cause either I work a little more (subject to proper work-life balance) or I stop getting money to live. From the opposite point of view, filling out a backlog and having enough work for a new hire is actually pretty hard when you're unsure of the full skillset, level of expertise, and how long it will take for that employee to ramp up.
|
|
#
¿
Feb 1, 2018 14:42
|
|
|
Pollyanna posted:Which is perfectly fair - I’m more thinking of this in terms of how truly a company needs me. For example, at one place I interviewed with today, I dug into exactly what the company needed in terms of head count, skill set, etc. Their response was that they don’t really need an engineer, though they have wants in terms of skill sets and soft skills - they’re aiming for doubling their user base and everything dependent on their next round of funding and that may pan out, but in the short term i.e. now it didn’t seem like they were hurting for a new engineer or anything yet. That made me a little nervous, since there wouldn’t be anything clear to point to when asking the question “why did we hire her?” and makes me feel more superfluous than I am comfortable with. If I get hired, I want to know that I am needed. Stop interviewing at startups. Go apply for a programming job at the MBTA if you want to do something interesting with good job stability. e: https://angel.co/massachusetts-bay-transportation-authority-mbta/jobs/117785-software-engineer Ffs they even ask for Elixir and Phoenix. Weren't you going on a while ago about learning Elixir?
|
|
#
¿
Feb 1, 2018 23:52
|
|
|
You're currently unemployed and have been bouncing from job to job where you've never found satisfaction. Maybe don't artificially limit yourself?
|
|
#
¿
Feb 3, 2018 02:21
|
|
|
You sound absolutely miserable to work with. Are you that guy who sits in the corner and grunts whenever anyone tries to talk to you?
|
|
#
¿
Feb 5, 2018 06:01
|
|
|
leper khan posted:using Nonsensical.Extraneous.Overly.Verbose.Names.Is.a.Social.Construct.Of.Java.Developers.Not.Required.By.The.Language; Verbosity is always better because 99% of the time you're writing code for other people to read later.
|
|
#
¿
Feb 5, 2018 13:24
|
|
|
I had my own office at my last job and while storage space has decreased I don't really find much of a difference between it and my current open office layout. I like that it's easy to engage my co-workers ad-hoc instead of having to quietly knock on the door in the hopes that they're a) there, b) not on a call, and c) ok with being disturbed. If I'm really trying to concentrate I'll grab one of the small rooms we have and go heads down for a while. It's not really a big deal and folks who get up in arms about it just seem weird to me. It's the equivalent to people who join a company because of snacks and ping pong.
|
|
#
¿
Feb 11, 2018 05:56
|
|
|
baquerd posted:If their door was closed, they probably didn't want to be disturbed. Think about that occurrence rate next time you decide to go all open plan collaboratey on heads down engineers and interrupt their flow state in an open plan office. Thing is, work doesn't happen in a vacuum. No matter how much engineers like to think that they're special, part of their job is to be available for other people; whether it's their boss, a project stakeholder, or a junior engineer who needs help. Of course, sometimes you just need to go heads down and be left alone but if someone trying to get your attention to ask you a question breaks your flow so much, that's a failing on your part. The ability to multitask and, more importantly, switch contexts is way more important than how fast you can churn out code in isolation. One of my major bugaboos with the way the tech industry handles interviews and hiring is that it's made"culture fit" a proxy for soft skills like teamwork, communication skills, writing ability, multitasking, etc. rather than a complement. Unfortunately this means we end up with an industry full of technically competent people who can't work with others and lack the basic facilities to adapt themselves to different situations. It's really unfortunate.
|
|
#
¿
Feb 11, 2018 12:06
|
|
|
Che Delilas posted:I had a lot typed up but I'll just say I find your statements rather disingenuous. They ignore a lot about what can make an open office lovely, and they assume everyone can or should think and work in exactly the same way. Of course open offices can be lovely. Just like places where everyone has their own office can be lovely. A terrible workplace is terrible regardless of where you sit and if having a door to close is your only sticking point then you're looking at a terrible place to work without even realizing it. I stand by my statements about not looking for enough soft skills in hiring. I hate working with people who isolate themselves in order to get work done. It always ends up that their idea of work is drastically different from project management, product management, leadership, and the team's idea of what work actually is.
|
|
#
¿
Feb 11, 2018 14:15
|
|
|
It is you, the person that can't do their professional job without any distractions, who is wrong. e: leper khan posted:In every open office I’ve been in, I’ve at varying points been distracted I want to call this out very specifically. If you are so fundamentally broken that being distracted by personal conversation makes for unpleasant working conditions then the only place you will ever find yourself happy is working a remote job from your home.
|
|
#
¿
Feb 11, 2018 14:28
|
|
|
Brain Candy posted:But use slack first instead of doing a drive-by. That's not how an office works. Part of the contract of having a place to work is that you are there to be available. You don't go to work to sit in isolation and hammer at a keyboard. That's not how any of this works and it astonishes me that some of the folks in this thread seem to think that it is. quote:Wanting engaged people doesn't excuse you from forgetting what a calendar is. Schedule things, that's part of your loving job if you are in management. That's not what we're talking about at all. We're talking about people who have such a tiny attention span or have such a fundamental inability to ignore others that their own work happiness suffers because they get distracted. Meetings are one thing but I'm not going to schedule 5 minutes with anyone to go over a question or some feedback. If you feel like that's unacceptable then I'm not sure what to tell you.
|
|
#
¿
Feb 11, 2018 14:58
|
|
|
B-Nasty posted:Serious question: what would be the problem with hitting up the person you want to talk to on Slack (or even email) with a "hey, I know you're busy, but when you hit a natural stopping point, can we chat for 5." Ideally, the chat could also happen somewhere outside of the earshot of others. Why are you assuming it's not sop to slack first? All I'm saying is that you come to work to do work and part of work is working with others. Isolating yourself to bang out code is only part of your job. gently caress off. If you're trying to extrapolate effects on working conditions in the tech sector based on the conditions in a Chinese mobile phone factory I don't know what to do with you.
|
|
#
¿
Feb 11, 2018 15:37
|
|
|
Brain Candy posted:Why not? Why should anyone respect you if you don't respect them? You have to be kidding me.
|
|
#
¿
Feb 11, 2018 15:38
|
|
|
leper khan posted:
Your assumption is that distraction is detrimental to work. What I'm trying to get at is that your job isn't only working in isolation.
|
|
#
¿
Feb 11, 2018 15:54
|
|
|
vonnegutt posted:Somehow it seems like the most talented of my former coworkers all have ended up working remotely for large successful companies, and at this point I'm unsure how I ever got anything done in an office environment. This isn't uncommon. A lot of the folks who are the most talented in terms of raw output are absolute messes when it comes to everything else. I'd much rather hire someone who's well rounded than someone who will pound out lines of code but can't work with others in an office. quote:Yes, teamwork and collaboration are important to the rapidly-shifting demands of early product development. However, large stretches of uninterrupted time are usually required to actually build said products. Removing your developer's ability to concentrate for more than a few minutes at a time is a guarantee that the product will take longer than anticipated to build. Teamwork and collaboration are crucial to continued delivery. If you work for a company where those two things aren't important I'd argue that attitude is far more problematic than whether you're in an open office or not. Main Paineframe posted:No, but that doesn't mean I need to hear the person sitting three feet behind me having a discussion about something that's completely irrelevant to me, nor do I need to be interrupted when I'm in the middle of explaining something to someone via Skype messages. Just because communication is part of the job doesn't mean it's ideal to just have everything completely unfiltered. You have 2 options. 1. Put on headphones 2. Ask the loud folks to lower the volume Neither of the two are hard. CPColin posted:I want to call this out very specifically as being incredibly rude. 
|
|
#
¿
Feb 11, 2018 16:54
|
|
|
Keetron posted:Nobody is disputing this. I don't disagree at all and I want to make clear that I'll never defend open offices as the solution to all problems. What I've been arguing is that there are far greater concerns to an organization (and that you should have when looking at a new job) than whether individuals have their own office.
|
|
#
¿
Feb 11, 2018 16:58
|
|
|
Brain Candy posted:You don't use slack? Nobody ever says 'give me [5 min, 15 min, 30 min, 1hr], I'm in the middle of something'? Everybody loves it when they are in the middle of collaborating and management swings by and you have to halt the world to talk about something else? You sound like the most insufferable person to work with. When you work in an office you're on company time and part of your job is fielding drop-ins. If you hate it so much then find a remote position.
|
|
#
¿
Feb 11, 2018 17:00
|
|
|
Pollyanna posted:Clearly there must be a way to allow for collaboration between engineers and not expose them all to sales and marketing never shutting the gently caress up. Opposite sides of a floor, something. It's weird that this one gets it more than the rest of you. Open office in and of itself isn't bad. It's that too many companies slap it on as a cure for everything rather than addressing organizational deficiencies like, for example, sales and engineering sitting in proximity.
|
|
#
¿
Feb 11, 2018 17:14
|
|
|
CPColin posted:Nice counter argument. I meant it literally, too; when you used that argument, in my eyes, you became much less credible. Your style of argumentation is offensive and, while I see the point you're trying to make, the way you're trying to make it is bullshit. Not sure what to tell you on this something awful dot com internet forum
|
|
#
¿
Feb 11, 2018 17:16
|
|
|
CPColin posted:"I'm leaving this thread forever!" would be a good start. No such luck big guy. How about you contribute to the discussion rather than being a white noise poster.
|
|
#
¿
Feb 11, 2018 17:20
|
|
|
Meh, I have a small team that skews more junior on the experience side of things and I'm more than comfortable avoiding remote workers entirely. It might work fine for other teams but I'm acutely aware of what it would take to successfully support a remote worker when the rest are in the office and no thank you at all. Sorry, not sorry.
|
|
#
¿
Feb 11, 2018 19:15
|
|
|
speng31b posted:A team's ability to support remote workers is a litmus test for its in-office communication, full stop. You are 100% wrong. Team composition matters a lot as to whether a team can support full time remote workers. If I had a few more senior engineers I'd be much more comfortable with it but at the end of the day, for us, it's a maturity issue more than anything else.
|
|
#
¿
Feb 11, 2018 21:49
|
|
|
the talent deficit posted:how many remote teams have you been a part of? my experience is that remote works when teams are managed well and falls apart when managers expect remote workers to take on the burden of communication. every well managed team i've been on could handle remote people I've been on a 40/60 remote team and, at a previous job, worked about 30% remote. I know what's required both from an IC perspective as well as a management perspective because I've seen where it falls apart on both sides. Personally, I would rather have my current team in its current state work out of the same office and would only hire remote if I was really crunched for labor or was hiring for an extremely specific set of skills. I don't say this because I doubt my own management skills or feel like the company can't support remote workers. I say this because I don't think the team is mature enough, both in terms of process as well as individually, to make 100% remote work effectively. In the future I'm sure we could get there but I don't really see the point. It's not like we're short on talent or hurting to recruit.
|
|
#
¿
Feb 12, 2018 12:31
|
|
|
the talent deficit posted:yeah but the point is that if your team was competently managed there really shouldn't be any barrier to having full time remote team members. if you rely on in person discussion and face to face meetings to get poo poo done it means you're not adequately putting process and expectations in place and you're relying on oral tradition instead of documentation. that's lovely management, not immature team members There's the ability to do a thing and then there's the desire. I just don't want to deal with a remote worker. Full stop.
|
|
#
¿
Feb 12, 2018 18:42
|
|
|
Mniot posted:It's not Lol there are so many reasons a team may not want remote workers. Attributing it to lovely management is lazy as hell and makes you look completely out of touch.
|
|
#
¿
Feb 12, 2018 23:17
|
|
|
Volguus posted:There are indeed many reasons. the talent deficit listed a few. There is only one valid reason though: legal/compliance. Even that one can probably be taken care of if there's a will, but usually is probably not worth the effort. The rest are easily dismissed without a second thought. Disagree 100%. Dismissing concerns over employee maturity and team process is one of those things that people who think their poo poo doesn't stink do. I'm glad if remote works for you but I wouldn't hire you if that's your sticking point. Sorry, not sorry.
|
|
#
¿
Feb 13, 2018 00:03
|
|
|
baquerd posted:So you'd rather have immature employees that can't follow processes than someone who wants to work remote? No, I'd rather develop a team and mature them before I take on the additional requirements of a remote worker.
|
|
#
¿
Feb 13, 2018 00:09
|
|
|
Volmarias posted:Your argument continues to basically boil down to "Remote work is bad because I don't like it and also my particular team is Not A Mature Team" (whatever "Not A Mature Team" is even supposed to mean here), so, uh, I guess it's good that we're not working together. Maybe rig up an air horn to blast whenever someone gets a commit into master, because only True Developers work there and they are all immune to losing flow from distractions so it's really just a fiesta! Look back through my posts. At no point did I say that remote work was bad. What I said are 2 things: 1. Turning down a job because of an open office is dumb because, generally, they're not bad although they can be if they're treated as a panacea for organizational problems. 2. I wouldn't hire remotely for my team because a) we're pretty new and b) the composition of the team is pretty junior; less than 3 years of experience except for me. Also please don't commit to master. Just don't do it. Please. the talent deficit posted:team process is exactly what we're talking about; if you have functional process and good communication remote is no big deal. if you need everyone scurrying from desk to desk to figure out what's going on you are bad at your job Let me give you another example of team process. My boss used to be a bit of a micromanager and only very recently let me run sprints for my own team. We're still refining our process and moving from time-based tickets (sad and bad) to complexity-based. Until our team's process is built up I can't support the additional burden that a remote worker brings. But again, that's an organizational issue which is what we've been talking about. Basically this: Maluco Marinero posted:This feels like a case where people are totally not addressing the modifiers that tip the decision towards remote or not. If you’re involved in a lot of design discussions, supporting juniors, collaborating cross disciplines, it’s a lot harder to do those things effectively in a remote situation.
|
|
#
¿
Feb 13, 2018 16:04
|
|
|
|
| # ¿ May 10, 2024 05:55 |
|
|
Main Paineframe posted:It sounds like you're violently agreeing, then? Everyone else is saying "remote work should be just fine with good processes, a competent team, and decent management", and you're responding with "well, our processes suck, our team sucks, and our management sucks, so remote work doesn't work for everyone". Read Maluco's post: Maluco Marinero posted:This feels like a case where people are totally not addressing the modifiers that tip the decision towards remote or not. If you’re involved in a lot of design discussions, supporting juniors, collaborating cross disciplines, it’s a lot harder to do those things effectively in a remote situation.
|
|
#
¿
Feb 13, 2018 16:57
|
|