Waking up late and working late.
Worst day ever.

Why are most (cloud-based) websites failing? They just spew out 5xx HTTP errors all the time. I can't even register properly on a website anymore. What the funk, man.

Do you sometimes get lazy and you don't feel like refactoring?

Corona shows that certain webshops were bought up cheaply and can't handle large loads. The fact that my shopping cart constantly crashes, the website itself crashes, flips between logged in and logged out, state is constantly corrupted and.. every so now and then I get 500 server errors, yeah, clear signs of no load balancing policy.

Everyone is raping the shopping sites right now.

I hate cheapskates.

MDKFJMQLSKDFJMQLSKDJFMQSLKDFJMQLSKDFL.

I hate websites that refresh the entire page and the entire effing web stack after every trivial change to a request.

HELLO AJAX OR WEB FRAMEWORKS ANYBODY

What is your faaavorite Software Development methodology?

Scrum, Kanban, ..

I am fed uuuuuup with the whole Corona bullshit at work, every, single, damn, daaaaay.

Fack.

You can say you know a computer language to a decent level when you can in fact make useful programs with it.

For example, I can say I know JavaScript to a basic level. I know its basic core functionality by heart (which can't be said for some people I know), such as:

- it manipulates the DOM, the DOM has Element, Nodes, TextNodes (all to be found on W3C documents with its own specs)
- useful functions are:
getElementById()
getElementsByClassName()
Also knowing that these return either HTMLElementCollection or NodeCollection because you have to iterate over it differently then
- element.textContent
- == and ===
- dynamic typing
- closures
- avoid global variables
- nodes have parentNodes
- isNaN, undefined
- arr.push()
- arguments don't have explicit types defined
- etc.

Using this knowledge I built an antispam script for a particular server. It's good to know the model of a language, that it sits in your head and that you can use and understand the constructs when you want and how you want.

Try creating a Java multi-dependency project without Maven and just manually adding the jars. It's super annoying as nested dependencies will arise and sometimes conflicts. :P

I think software development would be immensely difficult if there were no internet and you would have to search everything in a physical library whilst left to your intellectual wit. That would require great skills.

I used to do it like that back in 1994, but of course now I don't have the time for that unless it would be on a hobby project.

One of my UUID's contains the string 'f00bar'. Haha. What are the odds?

I sent an e-mail to my friend containing new information about something we were discussing.
He said: "It's cumbersome for me to access my e-mail, could you take a screenshot of it to me and send it on Skype?".

I was appalled. The e-mail is full text and he wants a screenshot of text. E-mail's primary purpose is to send text content. This guy never heard of copy paste text (which is what I did)? And he works in helpdesk, which is even more ironic.

While programming is imperative (how to x) rather than declarative (x = y) (mathematics), it deceives me from the idea that I won't have to touch a lot of math.

To my dismay, I now realize that in order for the imperative process to be correct, I have to do immense amounts of declarative thinking (algorithms, proofs,..). That which is written has to work.

If somebody creates rules around you, they're not your friend.

e.g.: you want to ask your colleague a question but they block you off and say that they have a set of bureaucratic rules you have to live by before you may even attempt to ask them a question.

Sigh.

As a developer I have a problem I have to get over and it's called: negative spiral thinking. It's the biggest impediment to progress (that and bureaucracy).

You sit there facing a problem, you keep focusing on the problem, but the problem spouts other problems and then you care too much about those other problems and you start fussing around, negative thoughts start to spout everywhere and you end up continuously losing your focus.

Blah.

For myself, I choked on the following:

- "Why do you want to work for us?"
- "Why us, specifically?"
- That stupid logic test with the guys wearing the red and white caps
- "Convince us how you're not overqualified. We're simple people."
- "Convince us how you're not going to leave us in the long run."
- Stupid db test: here is a scenario. You have 15 minutes to write an entire relational db with 20 tables, keys, relationships..
- "Why would we want to hire you?"

Fuck. Lack of sleep messes up work. I was writing code changes to a build for two hours but I deployed it to the wrong directory every time and then I wondered why my changes weren't reflected..

sleep++ needed..

Windows update just crashed my Outlook permanently.

Thank you, Windows Update.

I need to stop treating an OO language as if it were a procedural language.

I have the tendency to turn my code into GOTO spaghetti even though I'm semi-aware that objects exist and that they are distinct.
I still have to get used to this paradigm.

My Java professor always swore by the Plato paradigm, i.e.:
""Platonism" and its theory of Forms (or theory of Ideas) denies the reality of the material world, considering it only an image or copy of the real world.
According to this theory of Forms there are at least two worlds: the apparent world of concrete objects, grasped by the senses, which constantly changes, and an unchanging and unseen world of Forms or abstract objects, grasped by pure reason (λογική). which ground what is apparent." (wikipedia)

Thinking in objects, abstractions and metaphysics is not something I haven't done before (I've practiced it during Sociology and Ethics with the whole Pascal Leibniz, Newton and DesCartes approach) but it's certainly not easy.

Then there was my cool Programming 201 professor who said: "Don't worry man, just read those great UML, Program Design and GOF books and it will all become easy, like a story. It'll all make sense.
I mean, I've graduated, I've passed my Software Engineering I, II and III (hard as hell) but since I haven't focused on those theories and practices anymore, I've lost my touch.

It's definitely not easy for a novice programmer to transition between paradigms..

It annoys me when restaurants provide an online form for reservations, put in their disclaimer that "no reservation = no table", but when you make the reservation things go wrong.
For starters: their infrastructure not working on weekends (while they are open on weekends), them doing manual instead of automatic validation of a reservation, them not even knowing how to manage their own reservation system (which gives me the idea that they purchased some random reservation software).

I ended end having to call them about my reservation, they had a confused voice at the phone while they were navigating their own reservation software and ended up saying "Yeah ok table is booked, bye". I understand they're stressed out but come on, I don't think this is a modern nor graceful process. If you're boasting about having a reservation form, then at least live up to it. It reminds me of another restaurant where I had made a reservation online and when I got there, they told me "Next time book by phone please, we're not used to our software". For *********** sake.

Bah.

It reaaaally annoys me when my business logic is sound but the data is corrupted.

For example, find duplicates in a HashMap<String>.. but I didn't take into account the input could contain a space either before or after.. so I end up wondering: if a HashMap only contains unique keys, how come the count of items in the map is the same as the count of the input keys?! Well.. spaces were the culprit.

"12345" != "12345 ".. and therefore the Map sees it as two distinct keys..

What an annoying bug.

Lesson learned: 1) Sanitize input first and never trust it. 2) Never make assumptions

I adhere to the Socratic method. I don't like people in business who 'explain' things to others by stating "this is obvious" and "this is obvious" about various aspects of very business-specific rules.

No, it's not 'obvious', explain to me ad minutae how something works if you want to transfer your mental image to mine.

Software Development:
Too many problems, too little time.

"What the f, why isn't this Type or expression recognized?!" you think as you are writing your code.. and then you realize you're not inside a function.

I wonder how many times this has happened.

A friend asked me to set up a system that allows them to see their desktop on their tv and use a remote to wirelessly control it.
Fine, so I set up a system that allows them to interact with their desktop on tv wirelessly with their phone. Once the desktop booted, all they have to do is click one single button to open the thing they need.

Guess what? They come tell me: "This is too much work". What, clicking on a single button is too much work? Now you want it to auto-load too? Right, so apparently this is better: when the users plomps their @#!* on the couch, the OS has to be already booted, the desktop has to be ready and the desired functionality has to be launched. How lazy can you be?

Users can be so lazy.. and I thought I was lazy for not wanting to debug Python to webscrape a website that asked for cookies.

++ != [read, seen]

It annoys me immensely when I struggle with myself, criticizing my own lack of knowledge in certain areas and my colleagues say: "You'll learn by doing". No, I won't, that's a foolish dogma.

I won't and I have never learned by 'doing'. The best results I've obtained have been through understanding every last bit of what's under the hood of a particular functionality. I'm not going to understand the white box by constantly probing the black box, it's just unsatisfactory and insufficient information. It's even dangerous to base yourself on the black box results because you often might get false positives.

I got through university by massive multilateral sensory focus: kinesthetic (writing things down), auditory (listening to the professor), visual (observing graphs and models of the material taught), conscious (mentalizing it all and interlinking information so that later it's accessible from long-term memory). I can confirm this is necessary for the brain because a Neurologist once told me just that.

At least for me, I had the most horrible grades (D's and F's) in freshman year with the 'learn by doing' method and the best grades (A, A+) with the multi-sensory method in later years as I matured my studying methods. In fact, with that method I've continuously outsmarted other people who had 10 years more experience than me ('experts', 'consultants',..) but they preferred to stay in the ignorant 'bro zone' rather than learning things properly. Even worse, the day they arrived on the scene, they completely broke the production environment and messed it up for the whole team. I felt like banging my head on my desk. It just makes me disappointed in the system.

If you follow popular method, you'll soon find yourself in the same problems that arise from doing what everyone else does. What happens at that point? That's right, they have to call in someone who actually bothered learning things.

Time to take my whiteboard and draw out inheritance hierarchies in an effort to understand (Java) Collections. :)

<O.o>.. I think recruiters have their spam periods regularly or something (lol). I mean, I read about people here complaining about harassing recruiters and now I got a few of them myself in my mailbox.

</O.o>

I would like to share this piece of knowledge for the web devs out there, even though it's probably known:

If you're using the Spring framework and you want to accept a list of items as a multipart/form-data request, then Spring will only be able to correctly deserialize your JavaScript FileList in the backend if you have scripted it as follows:

var data = ev.dataTransfer.files;

var formData = formData();
for (i = 0, j = data.length; i < j; i++) {
formData.append('files', data[i]);
}

The for loop with the 'files' name is key here. Why? Because then it will resolve into:

key=val&key=val&key=val

and that's how Spring will correctly be able to deserialize it into a List. We remember from our HTML learnings that if we want values in a form to be processed as one, we must provide the same name= for each element in the form, otherwise if you have a separate name for each input, it won't be passed on as one collection of values.

This is why my list was originally null when received in the backend.

Courtesy of StackOverflow:

https://stackoverflow.com/questions...