When I was 14, I was bad at many things. I sucked at sports cause I was weak and small. School was boring so I did not study. I mostly played games.
During a summer break, I wanted to change shit in WarCraft 3, as I heard from a friend that heard it from a friend, that you can do that. Many internet searches later I realised that you kind of just tell to the game what you want it to do, just simplified. If (target is enemy) do damage, for (every human player) make sparkly stuff...
After months of "playing" games, the new school year started and I got, for the first time, a proper computer class. Imagine my surprise when we started doing the shit I did all summer. That year I had 100% on all tests.
Many years later programming gave me friends, made my inner nerd and geek come out, gave me a free trip to the USA to represent my country, two TEDx talks, and finally a job that I like with the pay I can live with.

That moment when your at a career fair and a non-tech recruiter won't hire you because you don't have the paper experience but the tech recruiter is questioning a guy with "5 years of Java experience" who can't answer what an anonymous inner class is.

On my former job we once bought a competing company that was failing.

Not for the code but for their customers.

But to make the transition easy we needed to understand their code and database to make a migration script.

And that was a real deep dive.

Their system was built on top of a home grown platform intended to let customers design their own business flows which meant it contained solutions for forms and workflow path design. But that never hit of so instead they used their own platform to design a new system for a more specific purpose.

This required some extra functionality and had it been for their customers to use that functionality would have been added to the platform.

But since they had given up on that they took an easy route and started adding direct references between the code and the configuration.

That is, in the configuration they added explicit class names and method names to be used as data store or for actions.

This was of cause never documented in any way.

And it also was a big contributing cause to their downfall as they hit a complexity they could not handle.

Even the slightest change required synchronizing between the config in the db and the compiled code, which meant you could not see mistakes in compilation but only by trying out every form and action that touched what you changed.

And without documentation or search tools that also meant that no one new could work the code, you had to know what used what to make any changes.

Luckily for us we mostly only needed to understand the storage in the database but even that took about a month to map out WITH the help of their developer ;)

It was not only the “inner platform” it was abusing and breaking the inner platform in more was I can count.

If you are going down the inner platform, at least make sure you go all the way and build it as if it was for the customers, then you at least keep it consistent and keep a clear border between platform and how it is used.

>first day at programming school
>we have to bring our own laptops
>teacher asks who is using windows
>every one raised their hands, except me...
>fuckme.jpeg
>teacher says: sorry, but we don’t support mac/linux
>twitchy_eye.tar.gz
>my inner voice: then why the fuck do we have to bring our own laptops, if you don’t support all fucking systems...
>teacher: so, do you guys ever heard of Visual Basic?

My point is, that a PROGRAMMING school should support all platforms if they consists that we have to bring our own machines to class.

Back in school a class mate used a bat file to recursively create a directory an then enter it and repeat.

The directory also ended with ascii 255 which looks like a space and when placed at the end is invisible.

This was in msdos and there was no mouse or autocomplete, also no deleting of non empty directories.

The teacher finally gave up and admitted he could not solve it.

You had do make a new script first to traverse to the inner most dir, then recursively back trace removing directories.

I'm currently one of two "pen testers" for the anticheat system of a game.

It all started a few days ago when the developer handed me the obfuscated package and told me to go at it. No big deal, I've bypassed it before the obfuscation, so I just changed some imports and sent in the screenshot.

Fast forward 100+ hours, it's turned into a cat-and-mouse game. He sends us (the testers) an update, we break it within hours. We show him what we exploited and he attempts to fix it. Rinse and repeat.

Finally, today he patched the one hole that I've been using all this time: a field in a predictable location that contains the object used for networking. Did that stop me? No!

After hours of searching, I found the field in an inner class of an inner class. Here we go again.

So, here is the worst experience, not one.. but recent two of many of the encounters I had with my OOP teacher... (I am in Second Year of Engineering). Lets Call him T.
To give a background of T... He knows nothing but acts like he is the master... you'll get to know this...

Incident #0:
*me developing a website for a client and T just bumps in*
T: Hey, what are you upto.
M:Nothing sir, just some Web-dev stuff.
T: What languages do you use?
M: I am currently using embedded ruby.
T: No no, I meant, what languages do you use for web-dev?
*inner* M: Ok, try to act stupid... He is not worth of all the knowledge.
M: Sorry sir, I just use simple HTML-CSS.
T: Ohh, I use Wordpress... It's a great language to build websites.
*inner* M: He has no idea what WP really is, he is a fuckshit.
T: It's so simple and easy, that you code for Desktop view, press Ctrl-M and then it automatically makes it for mobile view.
*inner* M: Bursts out into laughter
M: OK sir, will look over it.

Incident #1:
*He is teaching, suddenly topic comes of Oracle Certification for Java*
T: I know many of you have idea about java, but do you have what it takes to be an OCJP..
*inner* M: LOL...
T: It is a really hard thing, and I can bet... I can bet *he did repeat that twice* that no one from you can even qualify OCJP.
*inner* M: It's time... It's time
M: Excuse me sir, first of all it's OCA... OCJP does not exist anymore... And secondly, I am an OCA...
*inner* M: Yeah... Fuck you bitch!
*assucimg inner* T:Fuck, asshole..$#@#%@!@$@%#

And whole class was like -> o.O

Sooooo ok ok. Started my graduate program in August and thus far I have been having to handle it with working as a manager, missing 2 staff member positions at work, as well as dealing with other personal items in my life. It has been exhausting beyond belief and I would not really recommend it for people working full time always on call jobs with a family, like at a..

But one thing that keeps my hopes up is the amount of great knowledge that the professors pass to us through their lectures. Sometimes I would get upset at how highly theoretical the items are, I was expecting to see tons of code in one of the major languages used in A.I(my graduate program has a focus in AI, that is my concentration) and was really disappointed at not seeing more code really. But getting the high level overview of the concepts has been really helpful in forcing me to do extra research in order to reconnect with some of the items that I had never thought of before.

If you follow, for example, different articles or online tutorials representing doing something simple like generating a simple neural network, it sometimes escapes our mind how some of the internal concepts of the activity in question are generated, how and why and the mathematical notions that led researchers reach the conclusions they did. As developers, we are sometimes used to just not caring about how sometimes a thing would work, just as long as it works "we will get back to this later" is a common thing in most tutorials, such as when I started with Java "don't worry about what public static main means, just write it up for now, oh and don't worry about what System.out.println() is, just know that its used to output something into bla bla bla" <---- shit like that is too common and it does not escape ML tutorials.

Its hard man, to focus on understanding the inner details of such a massive field all the time, but truly worth it. And if you do find yourself considering the need for higher education or not, well its more of a personal choice really. There are some very talented people that learn a lot on their own, but having the proper guidance of a body of highly trained industry professionals is always nice, my professors take the time to deal with the students on such a personal level that concepts get acquired faster, everyone in class is an engineer with years of experience, thus having people talk to us at that level is much appreciated and accelerates the process of being educated.

Basically what I am trying to say is that being exposed to different methodologies and theoretical concepts helps a lot for building intuition, specially when you literally have no other option but to git gud. And school is what you make of it, but certainly never a waste.

Lua users, have you used moonscript?

It's a little language that has it's own interpreter or can be compiled down to Lua and it's absolutely lovely (currently using it with Love2d).

Of course, as with most things, what I love about it also royally pisses me off sometimes.

For starters local has to be declared for variables, unlike lua.
Otherwise the variable goes to _
Also note, that some tutorials literally tell you the opposite.

all variables are local by default
unless you don't declare them
then they go to _ (throwaway)
Some tutorials get this wrong too.

all variables have to be declared local
except tables. failure to declare a table WITHOUT a local will cause things like
table.insert to fail with "nil" values for no god damn reason.
No tutorial I could find mentioned this.

Did you know we call methods with '\'?
By the way, we call methods with '\'.
Why? Who the fuck knows.
Does make writing web routes more natural though.

Variables in the parameters of new are declared and bound for you. Would have loved to know this before hand instead of trying
to bind to them like a fucking idiot.

Fat arrows are used to pass in self for methods.
Unless you're calling a method. Then you use backwards slash. This fact is unhelpful when you're a beginner and dealing with the differences between the *other* arrow, the backslash, the fat arrow, and the fact that functions can be called with or WITHOUT parenthesis.
And on that note..

While learning all this other shit, don't forget parenthesis are optional!
Except when they're not!
..Like when you have a function call among your arguments and have to disambiguate which args belong to the outer call and to the inner call! Why not just be fucking consistent?

But on the plus size, ":" is now used for what it should have been used for in the fucking beginning: binding values to keys.
And on the downside, it's in a language thats built on top of another language that uses it for fucking *method calls*, a completely
different fucking usage.

And better still, to add to that brainfuckery thats lost in the mental translational noise like static on a fucking dialup modem, you define methods with the fat arrow. Wait, was that the single arrow or fat one? Yeah the fat one. Fuck. But not before you do THIS shit..

someShit: =>

yeah, you STILL include the god damn colon just so when you're coming from lua you can do a mental double take. "Why am I passing self twice? Oh right, because fuck me, I decided to use moonscript." It's consistent on that front but it also pisses me off.

A lot of these are actually quality of life improvements disguised as gotchas, but when you're two beers in to a 30 minute headscratcher it sure doesn't fucking feel like it.

Nevertheless, once I moved beyond the gotchas, it was like night and day. Sure moonscripts takes a giant steaming dump all over the lua output, like a schizophrenic alcoholic athena from the head of zeus, but god damn, when it works it just WORKS.

Locals that act like locals? Check.
Sane OOP? Check.
Classes, constructors, easy access to class methods, iterators? Check, check, check, check, check.

I fucking hate ceremony. Configuration over convention is for cunts. And moonscript goes a long ways toward making lua less cunty.
If you've ever felt this way while using lua, please, give moonscript a try.

You'll regret it, but in a good way!

Why Android uses so many quirky features in Java, like inner and anonymous classes, callbacks and nested generics?

I searched everywhere for the reason but can't find why, only how.

I rarely use these features outside of Android development.

Lmao, in Java you can put an inner class inside a method. I didn't know that.