|
Keetron posted:Also, I love refactoring so I am biased. my man my team does not understand my rabid enthusiasm for refactor/remove/revamp tech stories
|
#
?
Mar 26, 2018 14:23
|
|
|
|
| # ? May 10, 2024 11:35 |
|
|
This team seems to want to refactor and improve, but it looks like there’s just so much tech debt and so little opportunity to focus on it that they haven’t had a chance. I hope I can help alleviate it.
|
|
#
?
Mar 26, 2018 14:24
|
|
|
Pollyanna posted:This team seems to want to refactor and improve, but it looks like there’s just so much tech debt and so little opportunity to focus on it that they haven’t had a chance. I hope I can help alleviate it. I love refactoring. I think it's the feeling that what you've done has made an improvement while writing new code theres always the doubt you havent done it 'optimally'.
|
|
#
?
Mar 26, 2018 14:28
|
|
|
Bongo Bill posted:You're probably not being scrutinized that closely. This was correct
|
|
#
?
Mar 26, 2018 14:46
|
|
|
Pollyanna posted:This team seems to want to refactor and improve, but it looks like there’s just so much tech debt and so little opportunity to focus on it that they haven’t had a chance. I hope I can help alleviate it.
|
|
#
?
Mar 26, 2018 15:10
|
|
|
Everyone has tech debt, but not everyone is trying to manage it.
|
|
#
?
Mar 26, 2018 15:12
|
|
|
I mentioned technical debt the other day and everybody acted like they'd never heard the term before. 
|
|
#
?
Mar 26, 2018 15:54
|
|
|
When I manage tech debt the product owner says, "Why didn't this new feature get done? I promised the customer it would be done by this date [That I came up with without consulting engineers]." The good news is that he never has a leg to stand on so it all just amounts to whining on his part, but it's like clockwork and gets annoying.
|
|
#
?
Mar 26, 2018 17:25
|
|
|
I had a low-key panic attack today about trying to build something and it took me ages to get it done, like a solid 8 hours. I had an array which called 2 things from an end-point. We put them in the array then we have the ability to remove them and re-add them. The call, remove, and add all obviously come from different end-points. I had 4 buttons, remove and add. So basically I had a combination of YES YES, YES NO, NO YES, NO NO and 4 buttons which modified the values which disappeared and reappeared based on constants I had assigned or whatever. It was something wild like 32 possible combinations of actions I had to build and account for and it drove me to a mental breaking point building it but by about 4pm I did it. I'm so drained right now.
|
|
#
?
Mar 26, 2018 18:30
|
|
|
Ape Fist posted:I had a low-key panic attack today about trying to build something and it took me ages to get it done, like a solid 8 hours. All I can picture is one of those puzzles in an RPG where when you hit the first switch, the first and fourth light toggle, the second one controls the second and third light, etc. And you just have to turn all the lights on to unlock the stupid chest with a Hi-Potion in it.
|
|
#
?
Mar 26, 2018 18:47
|
|
|
Ape Fist posted:I had a low-key panic attack today about trying to build something and it took me ages to get it done, like a solid 8 hours.
|
|
#
?
Mar 26, 2018 23:26
|
|
|
Just woke up from a dream where I closed a file and then clicked "Don't save" in a reflex. It was a nightmare, I tell you.
|
|
#
?
Mar 27, 2018 05:41
|
|
|
Keetron posted:Just woke up from a dream where I closed a file and then clicked "Don't save" in a reflex. It was a nightmare, I tell you. the day I have to use an IDE that doesn't autosave like Intellij will be the day I lose all of my work repeatedly for about a month
|
|
#
?
Mar 27, 2018 13:39
|
|
|
Ghost of Reagan Past posted:Truth tables are your friend. And K-maps (or just plugging the logical expression into Wolfram Alpha)
|
|
#
?
Mar 27, 2018 15:36
|
|
|
My team has become almost mechanically good at delivering the agreed upon features for a release cycle, but holy poo poo I sometimes long for the chaos of a non-agile/whatever company where I could just log in and work on new things every day without needing to define spikes or some other “no QA” tasks in the last sprint of the cycle.
|
|
#
?
Mar 27, 2018 20:07
|
|
|
Iverron posted:My team has become almost mechanically good at delivering the agreed upon features for a release cycle, but holy poo poo I sometimes long for the chaos of a non-agile/whatever company where I could just log in and work on new things every day without needing to define spikes or some other “no QA” tasks in the last sprint of the cycle. Just wait til you take a step back and realize all the features you've delivered for the past 6 months are dumb made-up-on-the-spot poo poo that your PO shoves in the backlog just to fill it out without understanding a real customer's needs or real-life use case. also your product is a steaming pile of poo poo because you've never focused on anything that doesn't add direct user value so a stiff breeze will blow it over speng31b fucked around with this message at 02:42 on Mar 28, 2018 |
|
#
?
Mar 28, 2018 02:38
|
|
|
speng31b posted:also your product is a steaming pile of poo poo because you've never focused on anything that doesn't add direct user value so a stiff breeze will blow it over God, this is the worst. Especially when your operational monitoring is so lacking that you have no insight into the stiff breeze, any way to predict the stiff breeze, or even if a stiff breeze is indeed blowing.
|
|
#
?
Mar 28, 2018 07:52
|
|
|
Product owner: "Okay fine, I'll give you a timebox of one day to add some alerts BUT THAT'S IT"
|
|
#
?
Mar 28, 2018 10:20
|
|
|
Sagacity posted:Product owner: "Okay fine, I'll give you a timebox of one day to add some alerts BUT THAT'S IT" In one sentence what is wrong with the concept of an IP sprint in SAFE that is supposed to be used for tech debt.
|
|
#
?
Mar 28, 2018 14:14
|
|
|
Timeboxing is good but product owners are bad
|
|
#
?
Mar 28, 2018 14:20
|
|
|
speng31b posted:Just wait til you take a step back and realize all the features you've delivered for the past 6 months are dumb made-up-on-the-spot poo poo that your PO shoves in the backlog just to fill it out without understanding a real customer's needs or real-life use case. This but describing my adult life
|
|
#
?
Mar 28, 2018 14:55
|
|
|
Customer: "Is it possible to allow admins to make edits, even when the dates they're trying to edit are locked?" Code: if (!isDateLocked(date) || isAdmin()) { ... } Me, to other developer: "Hey, it looks like what the customer is asking for is already possible. Any ideas?" Other developer, direct quote: "Although the code appears to handle the admin case, the database trigger on Foo does not allow anyone (including admins) to modify reservations on locked days. The database trigger was added as a stopgap workaround for code flaws that allowed users to make changes in certain cases. I'm sorry to say that I do not have a good record of the details behind the flaws (just a many-year-old recollection that they did exist)." He goes on to say how the trigger could be altered to account for an "admin" flag. You know, as opposed to fixing the code and getting rid of the trigger that makes a liar out of it. I honestly don't know how this guy ever got anything done, seeing as he never made any record of what he was doing or what bugs he was encountering. Edit: The trigger is on the Production database, but is missing on the Test database. 
CPColin fucked around with this message at 16:39 on Mar 28, 2018 |
|
#
?
Mar 28, 2018 16:25
|
|
|
speng31b posted:also your product is a steaming pile of poo poo because you've never focused on anything that doesn't add direct user value so a stiff breeze will blow it over
|
|
#
?
Mar 28, 2018 16:26
|
|
|
speng31b posted:Just wait til you take a step back and realize all the features you've delivered for the past 6 months are dumb made-up-on-the-spot poo poo that your PO shoves in the backlog just to fill it out without understanding a real customer's needs or real-life use case. At my previous job, the first feature I shipped to production without any errors made me really proud. Couple years later we're re-writing the application and auditing functionality and come to my thing and find out the business never actually populated the tables that drove the behavior. So my code was just sitting there for 2 years, doing nothing, after the fire drill of collecting and refining requirements and getting it through the QA process. Learned a lesson that day, I tell ya.
|
|
#
?
Mar 28, 2018 16:42
|
|
|
CPColin posted:Customer: "Is it possible to allow admins to make edits, even when the dates they're trying to edit are locked?" Is this from radium.txt?
|
|
#
?
Mar 28, 2018 17:26
|
|
|
Clanpot Shake posted:At my previous job, the first feature I shipped to production without any errors made me really proud. Couple years later we're re-writing the application and auditing functionality and come to my thing and find out the business never actually populated the tables that drove the behavior. So my code was just sitting there for 2 years, doing nothing, after the fire drill of collecting and refining requirements and getting it through the QA process. Learned a lesson that day, I tell ya. Let me tell you about the set of APIs I developed that our frontend steadfastly refuses to implement in any respectable fashion because they think having to use more than one API call for a certain behaviour is confusing
|
|
#
?
Mar 28, 2018 18:06
|
|
|
It's very fun, and cool, to develop a solid and at least reasonably RESTful API, and then have your frontend forcibly seize the reins after falling too far behind schedule to understand things like "code quality", and then start mandating hacks to your API because otherwise your app will never release
|
|
#
?
Mar 28, 2018 18:10
|
|
|
New Yorp New Yorp posted:Is this from radium.txt? It's from one_guy_working_by_himself_for_a_decade.txt, so, basically. I hope to avoid having whoever comes after me think the same thing about me (but it's inevitable).
|
|
#
?
Mar 28, 2018 18:11
|
|
|
no i'm not bitter about that steadily backfiring since release why do you ask 
|
|
#
?
Mar 28, 2018 18:11
|
|
|
colin how could you murder my triple post combo like that you monster
|
|
#
?
Mar 28, 2018 18:12
|
|
|
Occasionally we have app admins implement some kind of security requirement from up high so that all PUT and DELETE get blocked and we have to explain again that we use those and their list of uncommon http verbs is outdated. And every time we have to explain to a management position why we don't get remove all puts and deletes.
|
|
#
?
Mar 28, 2018 18:25
|
|
|
ChickenWing posted:colin how could you murder my triple post combo like that you monster It's unforgivable and I'm truly sorry.
|
|
#
?
Mar 28, 2018 18:41
|
|
|
Rubellavator posted:Occasionally we have app admins implement some kind of security requirement from up high so that all PUT and DELETE get blocked and we have to explain again that we use those and their list of uncommon http verbs is outdated. And every time we have to explain to a management position why we don't get remove all puts and deletes. That hit a nerve since I wrote this a couple minutes ago const url = `${somestuff}&_method=${method}`
|
|
#
?
Mar 28, 2018 19:16
|
|
|
one time I worked on an API that was required to return 200 for every http request. If it was an error we were required to return 200 with a body of {error_code: 500, error: foo}. We asked the client why and they acted like we were the weird ones.
|
|
#
?
Mar 28, 2018 19:32
|
|
|
There was a period in Experts Exchange's history where somebody decided that the 404 page had little customer value, so we should keep chopping stuff off the path and redirect on up the chain until the user finally found a working URL. Well, it turns out search engines really don't like it when you never return a 404 for any URL. Right before that, somebody redesigned the 404 page to have a bunch of dynamic content on it, then wondered why the server load shot through the roof.
|
|
#
?
Mar 28, 2018 19:37
|
|
|
I worked with a client that had an API where you could POST some JSON to a Foo/Create method to create a Foo. They wanted to automate some stuff. I quickly discovered that the response would contain the HTML rendering of the page that normally invoked the API including the new Foo. That's it. No new Foo ID. I asked how anyone was supposed to use the API to automate anything. They seemed confused by the question.
|
|
#
?
Mar 28, 2018 19:54
|
|
|
vonnegutt posted:one time I worked on an API that was required to return 200 for every http request. If it was an error we were required to return 200 with a body of {error_code: 500, error: foo}. We asked the client why and they acted like we were the weird ones. This is usually because of terribly designed "rest" libraries that treat 200 and non-200 responses completely differently. I once had to work with one which just outright didn't give you access to the body of non-200 responses.
|
|
#
?
Mar 28, 2018 21:27
|
|
|
Change request PDF: "Deadline is April 22" Customer, just now: "Feature X is my lowest priority for getting ready for Tuesday." Me: "TUESDAY!?" God drat, the project management is terrible around here. Now we get at least one more round trip of emails before we figure out what's going on. And it's Spring Break, so nobody's paying attention anywhere on campus anyway.
|
|
#
?
Mar 28, 2018 22:32
|
|
|
vonnegutt posted:one time I worked on an API that was required to return 200 for every http request. If it was an error we were required to return 200 with a body of {error_code: 500, error: foo}. We asked the client why and they acted like we were the weird ones. Oh, you work at my company. (I'm sick of this and any new web services I create, starting from a few weeks ago, use HTTP status codes properly and if I need to hand back clarifying data I include it. No it's not consistent with the rest of the code base and I no longer give a gently caress if that's the only reason to not do something. The rest of the code base is more than a decade behind best practice anyway, if it ever was there in the first place.)
|
|
#
?
Mar 28, 2018 22:35
|
|
|
|
| # ? May 10, 2024 11:35 |
|
|
Sage Grimm posted:There's no question I'm bailing. The question I have to figure out for myself is whether to get out as soon as possible and then spend that time I would have been working for job hunting/resume updating or keep going and do all that on my free time when I'm not feeling burnt out. Pretty much the same. I knew I was gone when I got turned down for a very reasonable raise request, just a matter of finding a new job first.
|
|
#
?
Mar 28, 2018 23:03
|
|
