|
I sleep until 9, take a 2 hour lunch and I'm home by 4:30, that's about as close to my platonic ideal (which is doing nothing) as I can manage right now.
|
#
?
Jan 9, 2018 00:26
|
|
|
|
| # ? Apr 20, 2024 04:06 |
|
|
Jaded Burnout posted:I sleep until 9, take a 2 hour lunch and I'm home by 4:30, that's about as close to my platonic ideal (which is doing nothing) as I can manage right now. Occasionally I daydream about retiring early, but every time I find myself without obligations I end up going stir-crazy. ...I'd better figure this out sometime in the next ~30 years.
|
|
#
?
Jan 9, 2018 02:15
|
|
|
Pollyanna posted:For some bizarre reason I'm being asked whether I am interested in a front-end team lead position. I don't know how to break it to them that they're really barking up the wrong tree. My dude, maybe by some bizarre twist of fate, everyone else posting here telling you to not use recruiting agencies, was right?? It's unlikely I know, but you'll have to take a leap of faith and trust that they aren't gatekeepers to the promised land
|
|
#
?
Jan 9, 2018 02:36
|
|
|
Mr. Crow posted:My dude, maybe by some bizarre twist of fate, everyone else posting here telling you to not use recruiting agencies, was right?? It's unlikely I know, but you'll have to take a leap of faith and trust that they aren't gatekeepers to the promised land This was a hiring manager from said company actually
|
|
#
?
Jan 9, 2018 02:53
|
|
|
JawnV6 posted:No, no, All Development That Matters looks exactly like my container-slinging remote work, any delta from this platonic ideal can best be explained as a failure of management, possibly even personal failure of the developers involved to be looking out for their own happiness! Sorry you have to be physically present next to some hardware to do your job, but the vast majority of s/w development is just slapping some codes together that run on easily reproducible hardware/software setups (e.g. a web server or desktop.) For those developers, working from home is mostly seen as a huge positive benefit. If some developers that could otherwise work from home want to go into the office, that's fine, but they can't make the claim that working remotely doesn't work.
|
|
#
?
Jan 9, 2018 02:56
|
|
|
Working remotely works if it is done well. Doing it well is not simple and I would argue that it is uncommon.
|
|
#
?
Jan 9, 2018 02:57
|
|
|
Pollyanna posted:Working remotely works if it is done well. Doing it well is not simple and I would argue that it is uncommon. Regale us of your tale(s) of how you know these things.
|
|
#
?
Jan 9, 2018 03:58
|
|
|
JawnV6 posted:No, no, All Development That Matters looks exactly like my container-slinging remote work, any delta from this platonic ideal can best be explained as a failure of management, possibly even personal failure of the developers involved to be looking out for their own happiness! There are more container-slinging jobs (or jobs that could rise up to container-slinging) than there are expensive-proprietary-hardware jobs. The original guy was claiming it's only possible to do in a few cases which is not true.
|
|
#
?
Jan 9, 2018 04:08
|
|
|
Skandranon posted:Regale us of your tale(s) of how you know these things. She's not wrong, though. Supporting remote work has to be built into the fabric of an org for it to work at any decent scale and velocity.
|
|
#
?
Jan 9, 2018 16:03
|
|
|
Blinkz0rz posted:She's not wrong, though. Supporting remote work has to be built into the fabric of an org for it to work at any decent scale and velocity. Yeah, but it's not hard to do as an org, or rare anymore. Mostly it just requires a commitment to the idea, not telepresence robots or whatever.
|
|
#
?
Jan 9, 2018 16:30
|
|
|
Mao Zedong Thot posted:Yeah, but it's not hard to do as an org, or rare anymore. Mostly it just requires a commitment to the idea, not telepresence robots or whatever. Whether or not it is "hard" is arguable, but given how few places actually pull it off well the difficulty is irrelevant.
|
|
#
?
Jan 9, 2018 16:36
|
|
|
Another absolutely massive blunder on Hrunting's team courtesy of Mr. Manager (not related to me, thankfully) but I've actually begun to lose track of all the off-the-books poo poo that happens because there's just so much. Don't worry - I'll start a doxument to share with you all from here on out. My next meeting with HR is tomorrow so stay tuned for updates. Communication with the Senior on my team has opened my eyes to just how many people know this guy is total trash and how everyone is afraid to say anything because of how much power he has -- we know how he will literally just blame us for not being "technical enough" when the project fails again.
|
|
#
?
Jan 9, 2018 16:48
|
|
|
Mao Zedong Thot posted:Yeah, but it's not hard to do as an org, or rare anymore. Mostly it just requires a commitment to the idea, not telepresence robots or whatever. It’s not “hard”, but it does require a bit more effort than non-remote work. I managed multiple offshore (outsourced) teams and a few remote teams at various branches at my last job (huge company with global presence and a fuckton of resources) and it was absolutely more effort than managing local, in house teams. It greatly benefits from overcommunication by all parties, much more well defined work, and good time management skills on everyone’s part. Those things SHOULDN’T be uncommon, but, well, there you have it. At my new job (tiny start up, everyone in the same room, virtually no resources) it’s like barely any effort in comparison. Saying it can’t be done well or it’s just super difficult to do well is maybe an overstatement, but it definitely adds a non-trivial amount of challenge.
|
|
#
?
Jan 9, 2018 17:00
|
|
|
Outsourced teams are even harder because you have us vs them issues.
|
|
#
?
Jan 9, 2018 17:03
|
|
|
Jaded Burnout posted:Outsourced teams are even harder because you have us vs them issues. Outsourced teams are terrible because the vendor keeps rotating lovely engineers in.
|
|
#
?
Jan 9, 2018 17:56
|
|
|
I don't disagree that it involves a bit of effort to make remote work. It's also not for everyone. I think it's way overblown how rare 'good remote' is though. I've been remote for like.... 7 years now across 3 jobs (from 8 to 400 employees). Interviewed at probably 20-30 other places that had seemed to have their remote poo poo together. I wouldn't even consider a non-remote job in the future. (Not to mention I make probably literally 200% what I could locally, lol). Outsourcing is a horse of a different color.
|
|
#
?
Jan 9, 2018 18:10
|
|
|
friendbot2000 posted:I kind of fell into the career path of being a Test Automation Engineer and I am being groomed to become a lead of a new Automation Team in the near future. I still can't shake the feeling that my niche could be dangerous to my long term career health if Test Automation goes away. Do any of the more experienced old timers have any advice on where I should start branching off too as a contingency? I do a lot of work with frameworks (I built the one we use for automation) so that was my first guess, but I am looking for some outside input. I did an effortpost here: https://forums.somethingawful.com/showthread.php?threadid=3753052&userid=141478&perpage=40&pagenumber=3#post480031896 In fact, this whole page is about testing: https://forums.somethingawful.com/showthread.php?threadid=3753052&pagenumber=132&perpage=40
|
|
#
?
Jan 9, 2018 19:34
|
|
|
Was asked to give a quick dive into something technical I was into and somehow ended up talking about React and Redux and functional code in general, how that influences the design of an application and a program, and the effects it has on understanding the behavior of the product, readability of the code, an engineer's mental model of the application, and how easy it is to onboard new developers. I feel like I completely BSed that entire thing, but somehow the person I spoke to was satisfied. 
|
|
#
?
Jan 9, 2018 20:52
|
|
|
Pollyanna posted:I feel like I completely BSed that entire thing, but somehow the person I spoke to was satisfied. Congratulations you are now a senior engineer 
|
|
#
?
Jan 9, 2018 20:57
|
|
|
Pollyanna posted:Was asked to give a quick dive into something technical I was into and somehow ended up talking about React and Redux and functional code in general, how that influences the design of an application and a program, and the effects it has on understanding the behavior of the product, readability of the code, an engineer's mental model of the application, and how easy it is to onboard new developers. Jose Valasquez posted:Congratulations you are now a senior engineer Enjoy the 30-50% pay increase and twice the meetings.
|
|
#
?
Jan 9, 2018 21:03
|
|
|
Let me be clear, nothing I said made any loving sense and was definitely poorly organized and had zero proof to back it up. But, at least I got into it!
|
|
#
?
Jan 9, 2018 21:04
|
|
|
Pollyanna posted:Let me be clear, nothing I said made any loving sense and was definitely poorly organized and had zero proof to back it up. But, at least I got into it! The ability to string together a few related thoughts can be valuable even when the thoughts are bullshit.
|
|
#
?
Jan 9, 2018 21:09
|
|
|
Pollyanna posted:Let me be clear, nothing I said made any loving sense and was definitely poorly organized and had zero proof to back it up. But, at least I got into it! oh wow didn't know Robert C. Martin posted here
|
|
#
?
Jan 9, 2018 21:26
|
|
|
Pollyanna posted:Was asked to give a quick dive into something technical I was into and somehow ended up talking about React and Redux and functional code in general, how that influences the design of an application and a program, and the effects it has on understanding the behavior of the product, readability of the code, an engineer's mental model of the application, and how easy it is to onboard new developers. That's how I got my third coding job except F# vs C# instead of JS frameworks. I had also had three beers at lunch a couple hours before because the interview hadn't been scheduled yet.
|
|
#
?
Jan 9, 2018 22:41
|
|
|
remote teams are generally more functional than all-local teams in my experience. this is probably because the average experience level is higher for remote workers (companies are more likely to trust competent devs with a track record to work remote than new hires) but i also think it's because practices you have to adopt for remote teams are just better for development overall. documenting, async discussion and automation are all way more critical for remote teams than they are when you can just walk over to a coworkers desk
|
|
#
?
Jan 9, 2018 23:04
|
|
|
Munkeymon posted:That's how I got my third coding job except F# vs C# instead of JS frameworks. I had also had three beers at lunch a couple hours before because the interview hadn't been scheduled yet. Been there. Interviews and stuff coming up really really quickly and last-minute is the bane of my existence, I need time to mentally prepare  Looks like one of the opportunities I was considering (some local government transportation thing idk) is a contract role, and as a result they don't want to refer me to them without locking in my hourly rate. I'm tempted to tell them that I'm not interested in less than $125/hr, especially since it's a contract role and I'd have to buy my own insurance and poo poo. Don't contract roles practically require you to quote a high price like that to be worth it?
|
|
#
?
Jan 10, 2018 01:07
|
|
|
JawnV6 posted:God forbid a developer have like, a physical piece of hardware they need to test on. Unthinkable in the year 2018, must be evidence of outdated management processes. All my work at my last job was on embedded devices. (We made widgets, and watches, and cameras and all sorts of other things) and I worked with several people who were remote. It was never an issue. Just had to remember to ship them a test unit or 3 every so often. One of them was so good at staying in touch I kept forgetting he worked remotely until it was time to schedule the next round of HW deliveries. Working on HW is not a meaningful impediment to remote work. The goal is to eventually ship thousands if not hundreds of thousands of your product after all. If the corporation is having a hard time shipping a single test unit they're going to have real trouble when it comes time to actually sell the silly thing. LLSix fucked around with this message at 15:53 on Jan 10, 2018 |
|
#
?
Jan 10, 2018 01:46
|
|
|
LLSix posted:All my work at my lost job Nice Freudian lovely Springsteen B side. Has anyone ever worked on (a) project(s) where they had no idea if the product was ever even used or not? It seems like a kind of bizarre situation made possible only by the bizarro world of defense contracting. It's like, well, it might be great? It might be used all the time and save money and time and keep 'murica safe.. or it's never actually even been used by any end user. Seriously these are equally possible outcomes due to things I know about the projects. And the odd thing is absolutely no one else seems to care at all, or at least they've never mentioned it. I'm at the point where I don't know any more if it's weird that I get preoccupied with it, but it just seems hard to be motivated when you actually have no idea if the thing will even be used. Supposedly there is a very high 'failure rate' for projects though what the hell that means I don't know. A couple weeks ago I very inadvertently found a bug in IE (all they use of course) that rendered a significant portion of the UI on the homepage unusable. This is an app that has been in production for months now. I suppose this is just military_industrial_complex.txt that anyone ever on a defense project could write 
|
|
#
?
Jan 10, 2018 05:28
|
|
|
Dogcow posted:Nice Freudian lovely Springsteen B side. Has anyone ever worked on (a) project(s) where they had no idea if the product was ever even used or not? I've worked in (civilian) consulting and there's sometimes the same kind of thing. Organizations want, and then later don't want but have already paid for, software for all kinds of reasons, and for some consulting companies landing a project which costs a lot but winds up never going to prod or going to prod and never having any end-users is practically a victory condition. If feeling pride in "real people's lives are improved by the things I've worked on" is important to you, it can be a hard corner of the industry to work in.
|
|
#
?
Jan 10, 2018 07:32
|
|
|
The one time I did defense contracting the project I was working on was explicitly never intended to actually be used. A different department already had a working version of the thing we were building but wouldn't share it, so we were supposed to make it look like we had a bunch of useful features they didn't have so that they'd agree to an exchange. Naturally the punchline was that it turned out that their version didn't work either.
|
|
#
?
Jan 10, 2018 07:32
|
|
|
LLSix posted:All my work at my lost job was on embedded devices. (We made widgets, and watches, and cameras and all sorts of other things) and I worked with several people who were remote. It was never an issue. Just had to remember to ship them a test unit or 3 every so often. One of them was so good at staying in touch I kept forgetting he worked remotely until it was time to schedule the next round of HW deliveries. Counterpoint: I too have worked on hardware. Generally we didn't work on the mass produced hardware that eventually went to the consumer because that didn't exist yet because, obviously, we were in the process of developing it. We had large, fragile prototype boards and every so often there would be a hardware fault that meant the hardware guys would have to solder something or change a physical connection and I'm pretty sure they would not have been excited to drive to my house to do that. Nor would they have been thrilled to come round and put an oscilloscope on something while I poked it to determine whether something bad happening was a hardware or a software problem. Hardware can absolutely be an impediment to remote work.
|
|
#
?
Jan 10, 2018 14:27
|
|
|
feedmegin posted:Counterpoint: I too have worked on hardware. Generally we didn't work on the mass produced hardware that eventually went to the consumer because that didn't exist yet because, obviously, we were in the process of developing it. We had large, fragile prototype boards and every so often there would be a hardware fault that meant the hardware guys would have to solder something or change a physical connection and I'm pretty sure they would not have been excited to drive to my house to do that. Nor would they have been thrilled to come round and put an oscilloscope on something while I poked it to determine whether something bad happening was a hardware or a software problem. Hardware can absolutely be an impediment to remote work. You're a hardware production company right? Simple! Product 1: remote waldo system with built-in diagnostic tools Product 2: whatever your actual product is I'm sure the PMs would be fine with that.
|
|
#
?
Jan 10, 2018 14:30
|
|
|
Plorkyeran posted:The one time I did defense contracting the project I was working on was explicitly never intended to actually be used. A different department already had a working version of the thing we were building but wouldn't share it, so we were supposed to make it look like we had a bunch of useful features they didn't have so that they'd agree to an exchange. Naturally the punchline was that it turned out that their version didn't work either. It's less funny when this happens and you work on medical device software.
|
|
#
?
Jan 10, 2018 14:57
|
|
|
Pollyanna posted:Don't contract roles practically require you to quote a high price like that to be worth it? Take whatever counts as a reasonable salary for your area and experience, and divide that by 1000. That's the rate you quote, but you can probably accept 10-15% less and still be whole, depending on the insurance you pick. Also you'll probably want to create an S corp to receive the money, pay yourself a reasonable salary from and take the rest as pass-through because that'll probably get you a lower overall tax rate, but you'd want to talk to an accountant about specifics.
|
|
#
?
Jan 10, 2018 15:15
|
|
|
Munkeymon posted:Take whatever counts as a reasonable salary for your area and experience, and divide that by 1000. That's the rate you quote, but you can probably accept 10-15% less and still be whole, depending on the insurance you pick.. I'd say that's a good rule of thumb. I've set my prices through trial and error and it's wound up about at that. Of course when you're quoting a fixed price job all that goes out the window and you quote as high as you can get away with.
|
|
#
?
Jan 10, 2018 15:23
|
|
|
Munkeymon posted:Also you'll probably want to create an S corp to receive the money, pay yourself a reasonable salary from and take the rest as pass-through because that'll probably get you a lower overall tax rate, but you'd want to talk to an accountant about specifics. I've usually heard to create an LLC for independent contractors. What's the advantage of an S-corp vs an LLC?
|
|
#
?
Jan 10, 2018 15:24
|
|
|
vonnegutt posted:I've usually heard to create an LLC for independent contractors. What's the advantage of an S-corp vs an LLC? S-corp is what you want to do when you want to eventually sell your company. The difference is in how the enterprise value is calculated (because of a slight tax difference), which is relevant for mergers and acquisitions. Source: I read a bunch of entrepreneur books last year along with all of the programming books and video courses.
|
|
#
?
Jan 10, 2018 15:50
|
|
|
Munkeymon posted:Take whatever counts as a reasonable salary for your area and experience, and divide that by 1000. That's the rate you quote, but you can probably accept 10-15% less and still be whole, depending on the insurance you pick. I’ll be greedy and begin the bidding at $120 I guess, just to be an rear end in a top hat. quote:Also you'll probably want to create an S corp to receive the money, pay yourself a reasonable salary from and take the rest as pass-through because that'll probably get you a lower overall tax rate, but you'd want to talk to an accountant about specifics.  sounds capitalist but ok
|
|
#
?
Jan 10, 2018 15:57
|
|
|
vonnegutt posted:I've usually heard to create an LLC for independent contractors. What's the advantage of an S-corp vs an LLC? My accountant said S corp and that's what stuck in my head but he's a CPA, not a corporate lawyer  Pollyanna posted:
Call your congressperson and tell them you want real tax reform with some loopholes closed, then, I guess. Munkeymon fucked around with this message at 16:08 on Jan 10, 2018 |
|
#
?
Jan 10, 2018 16:06
|
|
|
|
| # ? Apr 20, 2024 04:06 |
|
|
Pollyanna posted:
Don't hate the playa hate the game
|
|
#
?
Jan 10, 2018 16:15
|
|