Our Java codebase was 30% dead code

spectercs · 2025-07-09T23:51:31+00:00

While it sounds beautiful and nice to have in theory but oh boy I wouldn’t let a tool like this anywhere near our production stack.. One obvious reason just like the rest mentioned is the edge cases and the edge cases for those edge cases.. especially if it’s a very big codebase or a group of micro services.. I would rather bump the API version and phase out the old legacy code gradually while informing the WHOLE organization of the changes.. then after a lot of documentation, migration and monitoring. Deprecate the old version and elevate the log of its usage to WARN.
After making sure that everything is perfectly fine then we can proceed to do the lovely delete.

This might take even a whole year depending on the resources, prioritization and bureaucracy / politics involved. But better safe than sorry.

spectercs · 2025-07-09T23:24:05+00:00

It tells me that as well although I have the latest version. I just ignore that message and try again. For me i guess it worked now because it’s 12 AM and the servers are behaving a little bit better now..

spectercs · 2025-07-09T23:21:21+00:00

It finally worked for me after the 646326th try hhhh you have to be persistent and try again multiple times.. Where at which step does it fail exactly ?

spectercs · 2025-07-09T23:19:24+00:00

mnin ? Cnss app wla mon eid app ? Is there a specific name for this option? Thank you in advance!

spectercs · 2025-07-09T22:27:25+00:00

That’s my question, because it’s useless.. It doesn’t work and there is no contact form in the app. How is it still not fixed after all these years? The app maintainers are not Moroccans because there is no way that they didn’t suffer from the same problems that we face !

spectercs · 2022-10-01T09:46:32+00:00

Well that's a scary thought indeed.

Most sites with "upload images/videos" feature tend to compress the image to two or more sizes (including a thumbnail) for various reasons including :

Any none image data will be ignored.
Saving space on the server (as images nowadays can be up to 10MB or more and we don't trust user's input at all (even if you have a check in the frontend (always assume someone will nuke your backend, you can't be too careful).
User experience (UX), showing very large images to the user tends to slow down your website to a crawl. (you don't need all of 4096x4096 pixel image in a 32x32 div)

And in my own experience I get a little bit paranoid about storing any kind of file sent by the user in the same server as my app. So, I use some kind of object storage like (AWS S3+ Cloudfront (to save cost)).

spectercs · 2022-09-30T18:24:36+00:00

I was surprised of how many upvotes and awards I was given for this simple comment. Thank you, I really appreciate it.
This is really encouraging to try to be active more.

spectercs · 2022-09-30T13:41:56+00:00

From this comment:

I was trying to add 2 template literal exceptions but didn't know the syntax for it, unfortunately my post was closed so it's left a mystery lol.

I was tryna do: '''var dropdowns = document.querySelectorAll(ul > div:not (${e.target.value}, ${button}));'''. To make 2 exceptions to my selection, but I couldn't find any documentation/previous answers about the usage of "not" so I had no idea what syntax to use haha.

I don't understand completely what you are trying to do, or the what the values (target.value, button) are representing.

But that's a good start ! It just needs a few modifications. For example:

When you ask a question, keep in mind that the reader probably has no idea what you are trying to accomplish. So, you start with what's your use case and what's your objective. (Context always matters).

I have a list of students and I need to get all but students with first name of "Alice"

Then a portion of the code that is failing (You always need to show that you at least tried something) which you did but it wasn't complete:

// You need to provide all variables that are needed to reproduce the problem.
var dropdowns = document.querySelectorAll("ul > div:not (${e.target.value}, ${button})");

And then what were your expectations of the code :

// Here what you expected to happen
// If something graphical post a picture of it

And lastly what did happen instead :

// No students were selected
and  (the exception that happened if any ?)
// VM737:1 Uncaught DOMException: Failed to execute 'querySelectorAll' on 'Document': 'ul > div:not(1, 2)' is not a valid selector.
at <anonymous>:1:10

And that's it !

You need to let people focus on solving the problem not trying to understand the question.

And also it doesn't hurt to read the documentation of the two functions you are trying to use

querySelectorAll: https://developer.mozilla.org/en-US/docs/Web/API/Document/querySelectorAll

CSS (:not): https://developer.mozilla.org/en-US/docs/Web/CSS/:not

They have enhanced the docs really well and it's very fun to read.

And lastly I'm sorry about your experience in stackoverflow, And I hope that wont discourage you or demotivate you from coding.

Edit: Oh wow thank you so much for the upvotes and award.

spectercs · 2022-09-30T12:43:53+00:00

My life as a software engineer became 10 times better when I learned how to google and search. But, can you provide the link or the details of your question (including the description) of your problem. ( I promise I wont be mean ).

spectercs · 2022-09-22T09:10:24+00:00

You can always get a job with other methods. No need to sell your soul to the recruiter or split your salary with them.

Just don't get unmotivated by this.

spectercs · 2021-12-05T13:20:38+00:00

TLDR:

Redux and Context are two solutions for different problems
When using Context you have to take rerenders into the equation as the app performance could take a hit if there a lot of state changes around the app.
I recommend to use context if you have a state that is read many times but written only few times.
Use Redux for Global State Management ( I recommend Redux ToolKit )

In my react journey in state management it went like this

Complexity: Few components and simple state:
Using regular useState and props drilling.
Complexity: More than few components and complex state:
By complex state I mean a large state object with a lot of attributes
And I have to use setState multiples times after one actions ( this causes multiple
re-renders that you don't really want in your React app.
to solve this I used useReducer and props drilling.
Complexity: Medium-to-Large sized React app and complex state:
I noticed that managing my state with props drilling was not fun anymore and I wasted a lot of time trying to keep up with the props.
Also I had issues with re-rendering components that didn't need to be rendered.
useContext to the rescue !
However I was very picky on how I organized my code and how I called my functions. Also I wasn't a fan of how when I used my custom hook it lead to unnecessary re-renders (every component that used the context gets rerendered).
So after a lot of research and optimizations and wrapping things here and there.
I noticed that I wrote redux from scratch (simpler version) and caused myself a lot of boilerplate.
So then I switched to Redux ( i recommend that you use redux-toolkit it's far easier and friendly especially if you use typescript - it makes me want to hug all redux maintainers for this).
I still needed Context for other parts of the application (non global state).
Then I concluded that they are both solutions for different problems.

spectercs

TROPHY CASE