Vance sure does love fucking couches!

IF you’re correct, then hasbro would just force them to fix it, and it’d become a never ending game of whack a mole, where probably every update has to break existing mods based on the hack to further disuade people.

// I told them I'd do this but only if they gave me time next sprint to fix it  - 12-03-1997

Lol, that just made me think though.

Instead if made with slave labor labels

This PAC and or politician received donations from slave labor using companies and a list.

They should mandate a "made with prison slave labor " label…

Those times you see an oddly specific and very weird rule and you just know there’s probably a great story around it.

No one cares if you leave a ticket open due to a bug or incomplete feature

Product sure as hell cares if you’re going to ship a bug or incomplete feature.

Never worked at company that wasn’t the case in over 15 years.

Product owns the work they ask us to do. We do their bidding.

And we certainly aren’t allowed to just change the scope of tickets at our own discretion without checking in

Apple won’t like that doomsday event lol

Give it long enough and somehow the person who decided on IPv6 will feel the same as every piece of matter we want to interact with can be networked.

I’m sure many smaller companies had their own internal Y2K moment as they scaled and became a big hit, and realized they used a wrong datatype like int instead of long or something and shit was gonna break by XYZ date if they did nothing heh.

This is my typical experience as well, too many people don’t do a code review of their own PR first.

When I was a junior, I had this coworker who did all my reviews. I was doing my absolute best and wanted to show that I was learning, so I would review all my work before submitting it and think, how would he review and respond to this code.

That just stuck with me and it’s my normal practice now.

I eventually learned that’s not as normal as I thought. I also tend to give better code reviews than others.

Edit: the other thing I do is check in with who will be reviewing my code well before I submit anything someone might think is weird and have a discussion about it before the reveiw. If it’s weird, there might be a better way unless were stuck due to technical debt or something, and doing that early vs at the end usually saves time.

So say we all

I’ve caught problems in code review and had to do this even.

Often it’s reading it and realizing there’s a complicated edge case or they missed something entirely.

Sure we can make a different ticket for that to move this along, but we’re getting product to agree first.

“hey I wrote this 6 years ago and it still works but it’s gross … please don’t judge me”

“hey I wrote this 5 years ago and it still works but it’s gross … please don’t judge me”

“hey I wrote this 4 years ago and it still works but it’s gross … please don’t judge me”

“hey I wrote this 3 years ago and it still works but it’s gross … please don’t judge me”

“hey I wrote this 2 years ago and it still works but it’s gross … please don’t judge me”

“hey I wrote this 1 years ago and it still works but it’s gross … please don’t judge me”

“hey I wrote this last month and it still works but it’s gross … please don’t judge me”

“hey I wrote this yesterday and it passed QA but it’s gross … please don’t judge me”

Wait, I knew they usually can’t void it without proof, but that’s NOT the case for an extended warranty add on?

Well, I’ve never said eff as many times in a row as I have today now. Thanks.

You mean the one that no one asked for, makes it harder to do the primary thing the app is designed to do, and all the involved developers have told management it’s a bad idea with a detailed list of why?

The actual problem is if you don’t add new features, there’s nothing for people to do beyond maintenance and you aren’t going to keep good developers to only stick around for that.

So your option is new features or a new app entirely, but coming up with other good apps isn’t easy and is a huge risk.

So if you actually did good market research and spoke to users, you could find new features to add.

Beyond a tiny company or sole developer, it doesn’t really work.

I have this problem with games, but there’s no rewind on games, and for some reason every game maker has decided that the most critical information you ever get happens when there’s loud sounds going on as some climatic event is happening and you can’t understand a fucking thing they say.

So most of the game I don’t need it, except for what ends up being the most important times I need it and don’t have it, so I have to leave them on in games.

And ya it’s distracting. At best I’m concentrating on not reading them which is distracting itself.

Learning Java for android is still useful as a lot of legacy stuff is Java, but given Google has gone Kotlin first, and Kotlin is IMO easier and less error prone, dipping their toes in that first would probably be the better move.

You can always circle back to Java, you will need to understand it if you get serious about Android development.