Ever had a colleague who nosed into what solution you brought to a problem and then stole your credit, telling the CEO how they found the solution and not you?

Yeah.

You better not tie your ego to your job.

ImgBurn has one of the weirdest sounds ever..

-job completed- Some kind of funny instruments jingling
-job failed- Sexy woman voice: "Oh no! :("
-you press 'stop job' more than once'- Sexy woman voice: "Hey! I said I got it!"

Lmfao..

LoL, why do we even have job reference contacts? So your previous manager can tell your new potential employer how much you sucked?

It's all so pointless..

Sometimes I think of applying for a dev job as 'pick your poison', since the chance of landing a job with fun languages and few headaches is slim these days.

How active is your GitHub repository?

Mine's been dead for over 5 years. Lmao.

I have found that once you work for a company where you have to implement everything in its raw form using the raw language and raw logic, you really have to know what you're doing and knowing some basic/medium programming and having some algebra knowledge doesn't cut it (unlike some people think).

I've been at two sides of the coin: I worked for a company that had everything in place, a framework that handled all edge cases and what not and I just had to focus on user stories, but I also worked for a company where I had to do everything manually.

For example, at the latter company I had to know Discrete Mathematics; truth tables to their most convoluted and disgusting form, having to be able to apply this on a late Friday night with a headache and lack of food and sleep with the PM stressing out.
I've had to deal with NOT AND OR AND OR AND OR AND branches or whatever, where an OR behaves like an AND and if you want a value between an AND AND and an OR, you'd have to do a NOT OR.. to think about latches, all in my head, sigh, anyway, within limited time constraints, without even having time to write tests, having to make sure that everything checks out while the client is breathing down my neck. Yeah, not such fun times.

I'm happy for those of you who can just write some moderately difficult logic but you don't have to break your head over doing everything manually, as if you're in the coding stone age and nothing is taken care of.
Companies like these make me want to run away.

Contrary to popular belief, after having been in the working world I've realized that what matters and what is of value is book knowledge, not experience.

I find 'experience' an overglorified waste of time. Having in-depth knowledge of everything is what's important.

One of the most inefficient practices I've seen done in companies is the company housing 50+ devs having to hire an expensive consultant who is only available on a limited time to figure out mysterious or in-depth problems with the company's main application (for example, JavaScript problems).

Then the whole dev team sits on his shoulders and production can't run smoothly until he fixes things. Even worse, him having the so-called qualifications, being the 'expert', but when asked an in-depth JavaScript question, they don't know the answer.
When I suggest to figure out things in-depth so problems like these can be prevented in the future, I'm met with: "Nah bro, we'll just apply quick fix #2" just because I carry the title 'Junior Developer'. Makes me want to hit my head on the wall on how stupid these people are.

This could all be solved if the dev team would be competent in the first place, knows how to read documentation and isn't lazy, most importantly. I hate teams like that.
Grab, the damn, documentation, read W3C, read MDN, get educated, and stop using band-aid solutions! Gah.
Toxic companies like these are what's wrong with some places in the development world.

I'm a proponent of knowledge.
Fellas, know your stuff.

Since you started your job, how many programming books have you read to get ahead in your job?

Examples:
- You're a Java programmer, so you read the OCP for Java 11 and then you get your OCP cert
- You're a .NET consultant, so you read another .NET book

Hmm.. I've noticed a trend in teams at companies: they always seem to have similar personalities, rather than similar skills.

For example, if the team leader is a pathetic, pretentious, sarcastic, frigid, lifeless loser who pretends he's happy, then he usually has a herd of equally pathetic and frigid losers following him. I notice that every time I apply to a company that has such a group, they instantly disqualify me as a member. Interesting, interesting..

The same goes for a company that has down-to-earth people like myself, then the team is usually a down-to-earth manager and down-to-earth, warm-hearted colleagues.

It all makes sense now.

Explain to an end user 'like-I'm-five' why webpages sometimes cause stress on the CPU.

Does your company chicken out on doing multithreaded programming because it's 'too complicated and unpredictable' for their programmers? lol

When you apply for a job, what is your top-selling sales pitch?

LoL.. I knew this one successful independent developer who told me:

"Why do all these companies use inefficient technologies - seriously? What I usually do is: I present myself to a company, I ask them what they would like to happen, what their problem domain is and then I present a solution. A lot of companies I've consulted for were jaw-dropped that an entire efficient and complex system was only a size of 52 KiloBytes because I just used simple languages to accomplish the task".

He has a point.. look at all these companies nowadays forcing you to Java, GlassFish, NodeJS and what not. Just the frameworks and libraries alone hog down 10 minutes of build time (sometimes 30!!), the worst companies using frameworks that require you to rebuild an entire project just to see a change in the UI.. they don't even add a watcher, and even then.. omg, not to mention averaging project file sizes of 100+ MB.

Sigh.. where is the development world going?

I wonder what percentage of developers are actually extroverted salesmen and can thus become a consultant...

One of the top annoying behaviors of interested hiring parties is recruitment agencies cold-calling you, as if you're a disposable packet of Skittles! It's outrageous!

Today I learned:

In Java, you're supposed to compile a source file in its package one directory up, outside of its package. You can't compile the source file in its own package directory, for it will state "cannot find symbol" on files in the same package, even though they're in the correct package directory. That can be quite confusing at first.

Given the following directory structure:

|_
|_ \pkg
|_ _ Src1.java
|_ _ Src2.java (interface with static method)

and the following source:

package pkg;
public interface Src2 { static void doStuff() { ... }; } // assuming JDK8+, where static default methods are allowed

package pkg;
public class Src1 { public static void main(String[] args) { Src2.doStuff(); } }

..being inside the pkg/ directory in the console,

this won't work:
javac -cp . Src1.java

"cannot find symbol: Src2"

However, go one directory up and..

javac -cp pkg/*.java pkg/Src1.java

..it works!

Yeah, you truly start learning how the compiler works when you don't use the luxury of a IDE but rather a raw text editor and a console.

If your manager asks you to write a raw algorithm based on raw data in order to properly structure, sort and filter that data, how long do you take on average to complete said task?

Example:
Here's a text file with a bunch of continuous data like: john doe 5555 my street 123 karen wiscott 12347 her street 22 peter wright

..and then you first have to start identifying boundaries for each data entry (which is a task on its own, with comparators and shit), solve its bugs.. then you have to make sure it's properly getting sorted.. sort those bugs.. Yeah, it just takes a long time for me to figure all that out.

It takes me 4-5 days on average since I'm a junior but managers expect it to only take 1-4 hours.. madness..

You give out your e-mail address at a conference and they start abusing it for all sorts of marketing purposes..

Fuckers.

An annoying type of colleague: the kind that refuses to cooperate and insists on doing shit their own way because they have done it that way for years and they become little crybabies whenever someone new tries to work with them.

Somehow managers accept their baby-like behavior because they've been producing output. However, like my Business Processes professor said: "Don't focus on output".

It's just annoying trying to work with these guys.

How often do you write code in a raw text editor, without any tools whatsoever (no IDE, no colors, no syntax highlighting,..)? :P

I'm doing that now.

Job interviews are like code smells; if it stinks, it probably didn't go well.

I hate data structures. I try to work out their algorithms in my head but they're completely counterintuitive. lol.

Dear uni

Stop trying to fucking nose into my life and find out what I'm doing with it at this moment.

Thank you.

Regards
ilivemyownlifenoneofyourbusiness

https://youtube.com/watch/...

Aah, ooh-ooh-ooh-aah-aah-ooh-aah.. Aah-aah-aah-ooh-ooh-aah-aah..! Ooh-ooh-ooh-ooh-ooh-ooh.. Ooh-ooh-ooh-ooh-ooh-ahh.. ahh..

Warghl! -squeaky alien sound-
Worgblh! -big alien sound-

Trained in all weapons.. both human and alien..

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

In reply to:
https://devrant.com/rants/3957914/...

Okay, we must first establish common ground here. What do we understand about "showing"? I understand you probably mean displaying/rendering, more abstractly: "obtaining". Good, now we move on.

What's the point of a front-end? Well, in the 90's that used to be an easy answer: to share information (not even in a user-friendly way, per se). Web 2.0 comes, interaction with the website. Uh-oh, suddenly we have to start minding the user. Web 3.0 comes, ouch, now the front-end is a mini-backend. Even tougher, more leaks etc. The ARPAnet was a solution, a front-end that they had built in order to facilitate research document-sharing between universities. Later, it became the inter(national) net(work).
First there was SGML to structure the data (it's a way of making it 'pretty' in a lexicographical way) and turn it into information (which is what information is: data with added semantics) and later there was HTML to structure it even further, yet we all know that its function was not prettification, but rather structure. Later came CSS, to make it pretty. With its growing popularity, the web started to be used as a publishing device.
source:
https://w3.org/Style/CSS20/...

If we are to solely display JSON data in a pretty way, we may be limiting ourselves to the scenario of rendering pretty web pages using aesthetic languages such as CSS. We must also understand that if we are only focusing on making a website pretty with little to moderate functionality, we aren't really winning. A good website has to be a winner in all aspects, which is why frameworks came into existence, but.. lmao, let's leave that to another discussion.

Now let me recall back my college days.. front-end.. front-end.. heck, even a headset can be a front-end to a pick-order backend. We must think back to the essence, to the abstract. All other things are just implementations of it (yes, the horrendous thousands of Javascript libraries, lol).

So, my college notes say:
"Presentation layer: this is the UI.

In this layer you ask the middle tier for information, which gets that information from a database, which then goes back to middle tier, back to presentation. In the case of the headset, the operators can confirm an order is ready. This is essentially the presentation tier again: you're getting information from the middle tier and 'presenting it' as it were.
The presentation layer is in essence the question: how do I bring my application data to my end users in a platform-and solution-independent way?"

What's JSON? A way to transport data between the middle tier and the presentation tier. Is that what frontend development is? Displaying it in a pretty way? I don't think it is, because 'pretty' is an extra feature of obtaining and displaying data. Do we always have to display data in a pretty way? Not necessarily. We could write a front-end script (in NodeJS perhaps) that periodically fetches certain information from a middle-tier is serves a more functional role rather than a rendering one.

The prettification of data was a historical consequence of the popularity of the web (which is a front-end) (see second paragraph with link). Since the essence of a front-end is to obtain information from the back-end (with stress on obtaining), its presentation is not necessarily a defining characteristic of it, but rather an optional and solution-dependent aspect, a facet.

First company:

- being sat at an office that didn't have chairs with proper back support. It would kill my back every day. Like sitting on a bar stool coding.
- not having access to basic resources (cafeteria, salary bonuses)
- being seriously underpaid ($200 under)
- not having an IT process pipeline (yeah, this is a huge one): no JIRA, no git, no VCS, no continuous integration, etc. I fucking spend 45% of the time fixing coding-unrelated shit.

Second company (very aggravating):

- dumb frontend bitch and privileged colleague who both kept telling me months on end to shut up and who wouldn't listen to my advice on anything, while my advice would actually help the company advance in productive ways. The key here is being told to shut up while stagnating. i.e. dead end job.
- people advancing in the company based on nepotism and favoritism, based on having tits and ass, rather than skills and independence.

- pointlessssssssss meetings where decisions are made solely based on the opinion of Mr. favorite senior dev. The rest just sits there like a bunch of sad saps and yay-nodders. Incompetent PO's who "would like to hear your input" but then when you give it, they completely dismiss you.

- pointlessssssssss monthly meetings with stakeholders, where the dev teams do nothing but clash and act like pussies in front of the PM just to get in his favor, but behind scenes continue to make the same mistakes and telling the CEO everything is fine. Goodness, how can it get more unproductive.

- completely antisocial and nepotistic 'colleagues' who won't even talk to you, let alone smile at you or be friendly. You saying good morning and them pretending you're vapor that doesn't exist. Go go company atmosphere! Especially during lunch, those are the worst times. Imagine sitting at lunch where everyone looks like you killed their dog and the rest is huddled up in little high school groups.
What else? The incessant and pointless smalltalk that makes me want to bang my head against the wall. Talking about dogs, kids, what show was on tv last night. The fuck man, do you have a brain?!

Third company:

- HR bitches who think they are the shit and developers are antisocial, helpless misfits, but they work with computers and they don't even fucking know what a status bar is! The irony!

- forced socializing and stigmatization for the opposite. Imagine coming into a company and you don't say good morning. Should that be a problem? No. Instead, everyone starts dogging on you and hating you just because you didn't smile in their faces and said: hiiiiiiiiiiii how did you sleep? Did you feed your dog? Fuck you.
Elliot (Mr. Robot): "Wouldn't it be awesome if there was a mute button for life?" -boop, boop, boop, boop...- Ahh.. there.. that's much better."

- CEO's sucking up to you but when it comes to salary increase, they say shit like: "Ahhh ya know, it's kinda difficult." Yet another dead end job.

I think the biggest bullshit about work life and beginning of a career is that at the start of your new job, colleagues and employers keep telling you that everything's gonna be fine and that things come with time and you'll learn and grow as you go on.

Not true. If you just cruise along and you don't maintain your skills, sooner or later they're going to ask you to do something you don't have the skills for, you won't be able to do it or anything remotely like it because you don't have the know-how and the result is: you get fired. I should know because I've never once not been fired; I'm up to 5 jobs now. lol

There is almost no greater example that demonstrates humans are liars.