@soull00t well... The times we hang out you can't use to further your career, so that might've been a bad move career-wise ^^

How the fuck did his pseudo code look?

MyAwesomeClass{
public static void main(String[] args){
//do everything I want
System.out.println("PM IS GREAT");
}
}

Well he did one thing right

There definitely are communication problems... Just not the way he thinks there are

Get out fast enough so the shit won't hit you on it's way down

@soull00t does he know agility and volatility aren't the same thing?

Holy shit, what did he do now?

@soull00t because he'll lose roles or because the roles get even shorter abbreviations?

I'm really excited to see how long his role list is gonna be at the end.
And what's gonna be the next title? I don't know, you don't know, when he doesn't know yet! One of the great riddles of our time

@PeterDCarter we could make it a 4 letter acronym and just call it "fron"

Understandable. But the death wishes are a bit too much, no need to traumatize the poor bus driver, just have him fall of a cliff or something
Also, fuckingRetardedObfuscatingName is a really bad name for a type. Did you recommend a small intro into clean coding conventions to him?

@soull00t let's hope with him involved in the development poc doesn't stand for piece of crap

Employee Boi, worst superhero ever

If you can't beat 'em join 'em?

@daniel-wu precisely my opinion. After the first two comments here were on the teachers side I really thought I was going mad xD

@nemetepst yeah, you can't just start with the OOP principles immediately, but doing procedural stuff first is... Very boilerplate heavy

@dotenvironment nice one, maybe I should check that out, it sounds at the very least very precisely defined :P
But no, I honestly think the opposite, it was trying to explain more than it had to at that point in time, and for my friend it was confusing ^^ they didn't see the point of it until I explained it how I did in the previous comments ^^
quite an obvious result, but: seems like different people respond better to different teaching approaches xD

@dotenvironment interesting. I feel like the explanation and what static does have pretty much nothing in common, but that might be different ways of thinking. I actually didn't think anyone would disagree here, but good to know there's people who agree with the teacher xD
The biggest problem I see is that they didn't do anything non-static anyway, so for me there wasn't even the need to explain it at all, at least no more than "you'll need this for now", same as you'd skip explaining everything in "public static void main" for the first hello world program. But if you explain it, it should be correct (in my opinion ^^)

@netikras I just wouldn't explain it at all at first. Just "you'll need this for now, it's gonna become clear why you do later on" and leave it at that. You wouldn't try to explain "public static void main" when showing someone how to do a hello world program. Maybe that's just differing styles, who knows, but my friend didn't get it when the teacher explained it and did get it when I explained what it actually did (with the preamble that it would make more sense later)

@Ranchonyx static makes a member object independent, so you can access the same value (in case of static attribute) or call the same function (for static methods) from any created object or without creating an object at all.
Nothing to do with visibility or accessibility, right? ^^

@netikras well you technically can access a static attribute/method from all class internal methods, sure. But that's not because of the static keyword you can access ALL attributes and methods from class internal methods (and all public ones from outside of it as well). Static just makes a class member object independent, so you can access the same value from each object or without even creating an object. Same for calling a static method.

So the explanation doesn't necessarily make the code not work or anything, it's just wrong. Again, they were still learning procedural programming, so they didn't even create any objects, literally everything they did was static.

@qwwerty same here. I still get annoyed by the stupid processes, but... Well you can't change it anyway, so why bother

@Oktokolo yeah, can't really help it. It's still annoying ^^ I'm not gonna put any roadblocks in the way, that'd be really hypocritical.
Oh but no, this part of the code isn't even doing user data. But who cares at this point ^^

@Fast-Nop yup, they're already in the loop. I'm complaining less about the admins and more about the stupid process ^^ ultimately they're just the messengers

@soull00t great... Well who wants to have free time anyway ^^

Work life balance? In THIS economy?
Are these guys delusional or just workaholics?

What the... Would they verbalize even stuff like brackets? Or hey if they use e.g. Python they'd have to spell out the indentations, right? Honestly I'd have agreed to that test just to hear someone try to verbalize code like that

@Oktokolo yeah I'm honestly wondering who coded that crap. Maybe an intern

@IntrusionCM no complaints about the 3 people rule, not my call though. And I definitely agree it's pretty bananas doing it alone, but well. Not much of a choice atm ^^

@IntrusionCM honestly, sounds like a decent idea, even with the organizational overhead. But that's not gonna work for my situation, wasn't an internal software and no one knows how it works except for me ^^ so a 3 person process is... Well. Impossible for a single person ^^

I like being a programmer, just dislike my current work
Also I love how not a single comment until now just outright said "no I hate my job" ^^