The cool thing is that purple sort of doesn't exist indeed. The mix of red and blue should actually be green. But because the green receptor in your eyes doesn't fire, your brain gets confused and has to come up with a color, because it's definitely not green. So purple is green without green 🤷‍♂️

Reinventing the wheel is amazing for learning and you should definitely try to understand everything about the wheel.

But please don't reinvent the wheel for production purposes unless you understand the currently existing wheels very well already and have good arguments for doing it your own way.

@AlgoRythm And when you get them you're still crap at programming so they seem impossible at first. 😉

That sounds like one of those early programming assignments in university.

Write a program that gives you a list of years based on the amount of different characters you need to write them"

If only all educational books could be like this

Don't really get all the "back down" comments. The best thing to do for your career is being professional. You want to build a good product and do things right, that's the way you get better at doing things right. If you back down and just follow along, it's gonna be a waste of time anyway because you'll get a lot of practice in bad coding and some stuff might even rub off on you because you don't know better.
So I say "fight it", but be pragmatic about it. Try to understand their position too. They might have put a lot of effort in their hideous implementations, so don't be a bully by calling them out on their bad code directly.

Position yourself to be a teacher. You know stuff they don't know, so teach them.
It takes time to earn their trust and slowly breach the walls they built around themselves, but if you show that you have good intentions and you don't antagonize them, they will eventually love you for it.

It's probably because it's a managed solution. If you like to host and manage your own stuff that's fine of course, but the time you spend on doing that is also translatable into money.
For many companies the cost of managing and possible downtimes would be much higher or at least riskier

@Root I was thinking, isn't it that it was a time before the whole "computers should be a part of your home and therefore they should look good" mentality? Maybe this plastic was their way of making computers look like professional business tools and not toys.
Just a brain fart, but sounds logical to me.

@Root yeah thought so, still the question remains; why this terrible looking plastic? I know they could do better back then.

I sometimes wonder why pc cases, among other stuff, were made of this ugly greyish plastic back then. Was it just the design of the time or did it have something to do with sturdiness, material availability or material cost?

When you have built a template for most cases and the PO doesn't want to spend money on making a change for this specific case. "just fit it in the current implementation"

Just like some people: seem to be a big deal on the surface but are a lot less when you get to know them in depth.

Great quote from Learn You A Haskell For Greater Good: "if you still don't know what recursion is, read this line"

@cha-m-ra I'm sorry if I have offended you. I only hoped to challenge your assumptions and give you another perspective.

I have not commented anything about your code or capabilities. I don't get how you can infer the quality of my code by my comment.

You don't have to be a cook to know the food tastes like shit.

If the product you delivered did not live up to the expectations of the client, and the client wants something more professional, he/she has the right to say it.

The reason is obvious: mongodb

You can actually get really far really easy if you use Hidden Markov Models with bigrams and trigrams. That should be your starting point for text predictions. When you get the hang of that you can mix in neural networks and other advanced stuff.
Just write a simple HMM program and let it 'read' some books using trigrams. After that you have a simple autocorrect/autocomplete keyboard.
If you want to predict on higher levels than just words, let's say on sentences, you can actually use these same trigram and bigram models mixed with some cleverness of your own and a more advanced learning algorithm such as neural network stuff.

@SystemZ yes, 33% real coverage is better than 100% fake coverage. That still doesn't mean 33% real coverage is sufficient. 😉

It would be nicer to write tests covering the most of your current functionality. Git commit after that and start refactoring like crazy while using your tests to see if you haven't changed the functionality. Remember to keep committing every successful change. Revert when you fuck up. 😉

//malbolge

('&%:9]!~}|z2Vxwv-,POqponl$Hjig%eB@@>}=<M:9wv6WsU2T|nm-,jcL(I&%$#" `CB]V?Tx<uVtT`Rpo3NlF.Jh++FdbCBA@?]!~|4XzyTT43Qsqq(Lnmkj"Fhg${z@>

@Santaclauze I use the IntelliJ internal debugger. Just breaking and stepping through your code gives incredible insight.
I also have that problem with real TDD, but I tend to make small unit tests for the particular functionality I'm working on just to isolate running and debugging my code to the part I'm working on. Afterwards it doesn't matter whether you keep the test, alter it or remove it completely. It's just faster than running and debugging your entire application.

In case you don't already: use a good debugger. It sure beats putting print statements everywhere and it amazes me how many people don't use debuggers. Most of the time I can pinpoint the culprit within a few minutes using a debugger.

Also use unit tests during development. Might be TDD or not, just create a single or a few tests for the functionality you're currently working on and keep running it.

I'm pretty sure a lot of companies survey their clients for "help with their product". 😉

Isn't no annotation a subset of bad annotation?

Building portfolio: create some projects and share them on git or work on some open source projects on git. This way you'll get your name out there and you'll have something to show at a job interview.

Additionally, you will get actual experience!

I had this exact same problem during my studies. Glad I'm rid of that shit.

Numpy rules!

I'm Dutch and I actually started wondering if I had never heard of this old-dutch word 'true'. 😅

Don't use Java EE, use Spring and especially Spring Boot.

@TheBird956 That's 9 months of experience added to your resumé and 9 months closer to not being a junior anymore!
With your newly gained experience you can also better assess new job offers for their fit with you and probably find a better and more fun job, blowing this previous job out of the water.
With the right mindset any setback can be turned into an advantage.

I've encountered something similar in the code I'm working on. Yesterday I was mindlessly fixing sonar issues when I noticed I was fixing issues in a third-party library which was copy pasted into the project. 😢