|
Ape Fist posted:We got an internal e-mail basically saying all of our development roles (including my job) were being outsourced to India in the new year. They announced this via e-mail, in the most spineless way possible, then basically begged us not to start looking for new jobs until we've all trained our replacements. They begged you, so I guess it's out the door as quickly as possible?
|
#
?
Jul 24, 2018 20:59
|
|
|
|
| # ? May 24, 2024 15:20 |
|
|
Boiled Water posted:They begged you, so I guess it's out the door as quickly as possible? I've an interview tomorrow.
|
|
#
?
Jul 24, 2018 21:15
|
|
|
Ape Fist posted:We got an internal e-mail basically saying all of our development roles (including my job) were being outsourced to India in the new year. They announced this via e-mail, in the most spineless way possible, then basically begged us not to start looking for new jobs until we've all trained our replacements. But ... why would they tell you? Incompetence? Or is there something else going on?
|
|
#
?
Jul 24, 2018 21:29
|
|
|
Forward the announcement message to someone at the client company
|
|
#
?
Jul 24, 2018 21:30
|
|
|
rt4 posted:Forward the announcement message to someone at the client company Do it from the computer of someone you don't like, because whomever owns the account that email gets sent from will get sued into oblivion.
|
|
#
?
Jul 24, 2018 21:35
|
|
|
Volguus posted:But ... why would they tell you? Incompetence? Or is there something else going on? The truth is that as a company mine is actually really nice. It's not my company that's forcing this to happen, it's our parent company which is currently undergoing a financial restructuring post-meltdown after Q4. Plus all the seniors are quite buddy buddy and they're all blabber mouths so we sort of half knew this was coming via office scuttlebutt anyway.
|
|
#
?
Jul 24, 2018 21:56
|
|
|
Volguus posted:But ... why would they tell you? Incompetence? Or is there something else going on? Also, if you're not living in one of the weird outlier countries with at-will employment then your employer has to both give some number of months of warning (3-6 back home, typically) plus provide a reason for your dismissal. It's not like they can just summarily fire you, who would agree to that contract? 
|
|
#
?
Jul 24, 2018 22:04
|
|
|
Xerophyte posted:Also, if you're not living in one of the weird outlier countries with at-will employment then your employer has to both give some number of months of warning (3-6 back home, typically) plus provide a reason for your dismissal. It's not like they can just summarily fire you, who would agree to that contract? But gosh, don’t you want to be able to quit at a moment’s notice without reason? Fair’s fair! 
|
|
#
?
Jul 24, 2018 23:48
|
|
|
Ape Fist posted:We got an internal e-mail basically saying all of our development roles (including my job) were being outsourced to India in the new year. They announced this via e-mail, in the most spineless way possible, then basically begged us not to start looking for new jobs until we've all trained our replacements. That's okay, training people for outsourced jobs never works out so you can spend 10 years "training" them and they still can't take over.
|
|
#
?
Jul 24, 2018 23:56
|
|
|
What do you call a modernization effort that replaces maintainable and performant code/technology with unperformant and unmaintainable code/technology? Cause that's what I'm part of right now.
|
|
#
?
Jul 25, 2018 00:25
|
|
|
Rubellavator posted:What do you call a modernization effort that replaces maintainable and performant code/technology with unperformant and unmaintainable code/technology? Cause that's what I'm part of right now. demodernization
|
|
#
?
Jul 25, 2018 00:33
|
|
|
Rubellavator posted:What do you call a modernization effort that replaces maintainable and performant code/technology with unperformant and unmaintainable code/technology? Cause that's what I'm part of right now. Consulting?
|
|
#
?
Jul 25, 2018 00:40
|
|
|
Technical Reverse Mortgage?
|
|
#
?
Jul 25, 2018 00:40
|
|
|
Rubellavator posted:What do you call a modernization effort that replaces maintainable and performant code/technology with unperformant and unmaintainable code/technology? Cause that's what I'm part of right now. Is nodejs involved somehow?
|
|
#
?
Jul 25, 2018 00:58
|
|
|
Rubellavator posted:What do you call a modernization effort that replaces maintainable and performant code/technology with unperformant and unmaintainable code/technology? Cause that's what I'm part of right now. Hipster.
|
|
#
?
Jul 25, 2018 01:01
|
|
|
Ape Fist posted:The truth is that as a company mine is actually really nice. It's not my company that's forcing this to happen, it's our parent company which is currently undergoing a financial restructuring post-meltdown after Q4. Plus all the seniors are quite buddy buddy and they're all blabber mouths so we sort of half knew this was coming via office scuttlebutt anyway. That's sweet of your company and all, but do still blow that whistle.
|
|
#
?
Jul 25, 2018 04:21
|
|
|
Rubellavator posted:What do you call a modernization effort that replaces maintainable and performant code/technology with unperformant and unmaintainable code/technology? Cause that's what I'm part of right now. Defactoring?
|
|
#
?
Jul 25, 2018 04:38
|
|
|
Rubellavator posted:What do you call a modernization effort that replaces maintainable and performant code/technology with unperformant and unmaintainable code/technology? Cause that's what I'm part of right now. enterprise software.
|
|
#
?
Jul 25, 2018 04:58
|
|
|
Rubellavator posted:What do you call a modernization effort that replaces maintainable and performant code/technology with unperformant and unmaintainable code/technology? Cause that's what I'm part of right now. The
|
|
#
?
Jul 25, 2018 05:06
|
|
|
Rubellavator posted:What do you call a modernization effort that replaces maintainable and performant code/technology with unperformant and unmaintainable code/technology? Cause that's what I'm part of right now. Blog-driven development
|
|
#
?
Jul 25, 2018 06:00
|
|
|
Rubellavator posted:What do you call a modernization effort that replaces maintainable and performant code/technology with unperformant and unmaintainable code/technology? Cause that's what I'm part of right now. I believe the official term is "Refucktoring."
|
|
#
?
Jul 25, 2018 06:35
|
|
|
Rubellavator posted:What do you call a modernization effort that replaces maintainable and performant code/technology with unperformant and unmaintainable code/technology? Cause that's what I'm part of right now. uhh, i feel like after a certain point, you begin to have five goals in mind a) get paid b) don't work on anything unpleasant c) make users suffer d) minimize interaction with other teams e) guarantee project success Re-implementing something that already exists is great because a) You get to pick a hot technology that you don't know and get to put on your resume b) Don't have to deal with requirements issues - with new software, your PO will be like "oh, what if we put the controls on the screen in a different order" and act like that's revolutionary. If you're re-implementing something that already exists, "it worked like this in legacy" is pretty bullet-proof. c) Users will hate the new system and will either ask you all to roll it back or for endless bug fixes. Fixing these bugs looks a lot like work. d) Since you already have a system that works, no need to spend a bunch of time in meetings or talking to people about how it should improve, just make it look like legacy. e) Your project is already successful by definition because it is forced to be - you are rewriting software that was accepted and people pay money for. 90% of software projects fail so most of the time, if you work on new stuff, it's just going to get thrown out anyway, whereas people will probably begrudgingly use your rewrite anyway.
|
|
#
?
Jul 25, 2018 06:37
|
|
|
Rubellavator posted:What do you call a modernization effort that replaces maintainable and performant code/technology with unperformant and unmaintainable code/technology? Cause that's what I'm part of right now. Progress.
|
|
#
?
Jul 25, 2018 14:03
|
|
|
Rubellavator posted:What do you call a modernization effort that replaces maintainable and performant code/technology with unperformant and unmaintainable code/technology? Cause that's what I'm part of right now.
|
|
#
?
Jul 25, 2018 21:22
|
|
|
Abstruction
|
|
#
?
Jul 25, 2018 21:27
|
|
|
I always just called it job security assuming you successfully get rid of the old code
|
|
#
?
Jul 25, 2018 21:59
|
|
|
JawnV6 posted:Abstruction Nice!
|
|
#
?
Jul 25, 2018 23:38
|
|
|
Rubellavator posted:What do you call a modernization effort that replaces maintainable and performant code/technology with unperformant and unmaintainable code/technology? Cause that's what I'm part of right now. Leveraging industry-standard microservice frameworks to do the heavy lifting in our strategic initiative to improve productivity metrics.
|
|
#
?
Jul 26, 2018 05:30
|
|
|
Paolomania posted:Leveraging industry-standard microservice frameworks to do the heavy lifting in our strategic initiative to improve productivity metrics. Reported your blank post
|
|
#
?
Jul 26, 2018 15:43
|
|
|
What do you call a modernization effort that replaces unmaintainable and unperformant code/technology with unperformant and unmaintainable code/technology? Cause that's what I'm part of right now.
|
|
#
?
Jul 27, 2018 02:51
|
|
|
Captain Cappy posted:What do you call a modernization effort that replaces unmaintainable and unperformant code/technology with unperformant and unmaintainable code/technology? Cause that's what I'm part of right now. Capitalism.
|
|
#
?
Jul 27, 2018 04:03
|
|
|
Rubellavator posted:What do you call a modernization effort that replaces maintainable and performant code/technology with unperformant and unmaintainable code/technology? Cause that's what I'm part of right now.
|
|
#
?
Jul 27, 2018 04:05
|
|
|
Captain Cappy posted:What do you call a modernization effort that replaces unmaintainable and unperformant code/technology with unperformant and unmaintainable code/technology? Cause that's what I'm part of right now. Ordinary.
|
|
#
?
Jul 27, 2018 04:05
|
|
|
Captain Cappy posted:What do you call a modernization effort that replaces unmaintainable and unperformant code/technology with unperformant and unmaintainable code/technology? Cause that's what I'm part of right now. Devops
|
|
#
?
Jul 27, 2018 05:33
|
|
|
Captain Cappy posted:What do you call a modernization effort that replaces unmaintainable and unperformant code/technology with unperformant and unmaintainable code/technology? Cause that's what I'm part of right now. A normal day at the office.
|
|
#
?
Jul 27, 2018 09:53
|
|
|
Hey, I love talking about rewriting and retiring legacy systems! Because it sucks! But sometimes it can suck less and I have some thoughts and articles to help process the hell all developers live through at some point. One thing to keep in mind is you can't rebuild the whole thing. In a decent case it took five years and many engineers and production hours to get it to it's current state. In a bad case it has had 20+ years and hundreds of engineers and is also still under active development. And while it might not be great and a pain in the rear end to work in, it works. Your rebuild does not work, and probably doesn't have those learnings or the time to get there. You'll want to start with a single feature or component and an iron-tight business case for why a rewrite of that feature is necessary. Another thing to keep in mind, there can only be one source of truth. A two-way sync across databases is a good sign that someone hosed up. Hard. Ask me how i know. You might end up pushing data into the other database or reading data from a different database while doing the cutover, but there can only be one source of truth. Lastly, legacy is mostly a term for systems that current engineers don't understand. But it is usually cheaper and faster to fix the current system (while writing up docs and tests) than to build a new one from scratch. Some good info: 1.) 5 Red Flags Your Rebuild Will Fail : This one is a quick read and captures all the signs you're loving up on how/why to rebuild. 2.) Strangler Application: This one is also a pretty quick read about how to actually go about replacing an existing system with something new. 3.) Growing Old Conference Talk: This is more philosophy about rebuilds and legacy code, but I think helps give a good mindset about the how and why of rewrites. Long talk though.
|
|
#
?
Jul 28, 2018 05:47
|
|
|
Greatbacon posted:Another thing to keep in mind, there can only be one source of truth. A two-way sync across databases is a good sign that someone hosed up. Pssh if you think a two way sync is hard try a three way sync when you are trying to replace two legacy systems with different requirements with a single new system 
|
|
#
?
Jul 28, 2018 14:50
|
|
|
Been some Serious Analysis being done today of the Base64 encoded tickets we attach to URLs for customers, and the word "gently caress" appears in them with higher frequency than any other common word by a fairly high margin. At the minute we are giving approximately 0.03 fucks/ticket vs. a mere 0.004 shits/ticket
|
|
#
?
Jul 30, 2018 17:05
|
|
|
RobertKerans posted:Been some Serious Analysis being done today of the Base64 encoded tickets we attach to URLs for customers, and the word "gently caress" appears in them with higher frequency than any other common word by a fairly high margin. At the minute we are giving approximately 0.03 fucks/ticket vs. a mere 0.004 shits/ticket Please tell me this is in response to to a complaint.
|
|
#
?
Jul 30, 2018 17:25
|
|
|
|
| # ? May 24, 2024 15:20 |
|
|
wilderthanmild posted:Please tell me this is in response to to a complaint. Sadly not, more just for amusement on a slow day after someone noticed a few fucks. We couldn't figure out why gently caress was so common compared to anything else, it seemed non-random but was probably just the universe's general sense of humour
|
|
#
?
Jul 30, 2018 17:57
|
|