You know what really grinds my gears?

Seeing a 5-line comment, that have absolute no value, for a variable declaration.

Example:

/*
*
* String that holds a delivery address.
*
*/
public String deliveryAddress;

To become an engineer (CS/IT) in India, you have to study:
1. 3 papers in Physics (2 mechanics, 1 optics)
2. 1 paper in Chemistry
3. 2 papers in English (1 grammar, 1 professional communication). Sometimes 3 papers will be there.
4. 6 papers in Mathematics (sequences, series, linear algebra, complex numbers and related stuff, vectors and 3D geometry, differential calculus, integral calculus, maxima/minima, differential equations, descrete mathematics)
5. 1 paper in Economics
6. 1 paper in Business Management
7. 1 paper in Engineering Drawing (drawing random nuts and bolts, locus of point etc)
8. 1 paper in Electronics
9. 1 paper in Mechanical Workshop (sheet metal, wooden work, moulding, metal casting, fitting, lathe machine, milling machine, various drills)
And when you jump in real life scenario, you encounter source/revision/version control, profilers, build server, automated build toolchains, scripts, refactoring, debugging, optimizations etc. As a matter of fact none of these are touched in the course.
Sure, they teach you a large set of algorithms, but they don't tell you when to prefer insertion sort over quick sort, quick sort over merge sort etc. They teach you Las Vegas and Monte Carlo algorithms, but they don't tell you that the randomizer in question should pass Die Hard test (and then you wonder why algorithm is not working as expected). They teach compiler theory, but you cannot write a simple parser after passing the course. They taught you multicore architecture and multicore programming, but you don't know how to detect and fix a race condition. You passed entire engineering course with flying colors, and yet you don't know ABC of debugging (I wish you encounter some notorious heisenbug really soon). They taught 2-3 programming languages, and yet you cannot explain simple variable declaration.
And then, they say that you should have knowledge of multiple fields. Oh well! you don't have any damn idea about your major, and now you are talking about knowledge in multiple fields?
What is the point of such education?
PS: I am tired of interviewing shitty candidates with flying colours in their marksheets. Go kids, learn some real stuff first, and then talk some random bullshit.

!rant

*Just got a package delivered, didn't check yet*
Friend: who sends you stuff from from the USA?
I (excited as fuck): uh it must be my
DevRant
Duck
Delivery.
Friend: your what?
I explain, he walks away not giving a fuck.

But I don't care what he thinks, i love my new devDucks. Oh and special thanks to @dfox for the autograph. Well technically you just signed the customs declaration, but an autograph none the less.

Just learned that my employer withhold part of my salary every month the past 5 months! I did not notice it as it was overtime compensation.

I first thought maybe it was a mistake so I asked, the reply I got was: Oh you know that compensation we agreed upon? I wasn't having it anymore so I decided to half it and been since then editing the hours you billed every week to reflect that and accedently forget to tell you.

Accedently?! My ass! One week is believable but not 20 weeks. The only reason I found out is that they tried to lower the compensation even further which caused these hours to show up differently in the hour declaration software we use.

So currently on my way to return company's property and quit.

Python: I hate the way it uses True/False over true/false

Java: Static. Just fuck static. oh and System.out.println(), why the fuck did they make the basic print function so long to write.

C#: I despise the way the curly braces get automatically put under the function declaration rather than beside it since it's a language style thing.

C: the inability to declare vars in altho declaration of a forloop. Although I think C11 let's you do this.

Javascript: Fucking prototypes.

Coldfusion: it runs like an elephant. Slow and heavy.

Go: The way the compiler won't let you have unused variables/imports. Pain in the ass for testing.

When I'm forced to maintain a C project having recently done a lot of C++:

Compiler: Declaration may not appear after executable statement in block.

Me: dEcLarAtiOn mAy NoT aPpeaR aFtER eXeCuTAblE stAtEmEnt iN BloCk. *pffffttt*

If you make students take coding tests/quizzes on paper, don't grade them on picky syntax errors! We don't code on paper in the real world; syntactic highlighting and red squiggles will usually show you that you accidentally typed that declaration incorrectly. Understanding programming concepts is much more important than being able to write a program on paper.

Now that's a declaration of independence.
Happy 4th everyone 🎇🔥🎆🎇

Not the declaration I deserve, but the one I need right now.

Don't you feel confused if someone in your team declares variables like this?

TextArea textarea1, textarea2;
Component component1, component2, component3

textarea2.setText(textarea1);

It's an identifier for a reason, make yourself identified!

There is no other way to put this.

My HR manager just sent out her tax declaration sheet containing all her salary details out to the entire company via email.

The worst part, she makes as much as I do yet fails at the one single job she's supposed to do.

In the 1990s code editors on the Mac could insert the omitted function prototypes into a header file with one command; and even automatically keep the header declaration updated when you changed the source definition (name, parameters, etc)

Today in Xcode you have to copy and paste the stupid function header definition from the source code into the header file. What happens if you leave the "{" that got copied accidentally? OMFUCKING LORD, it triggers all sorts of erroneous errors in all the **source code** files where it is included instead of the header with the stray "{"

I started to question whether nor not I knew C, if gravity worked, if the sun would come up. I wasted a day of dicking around in StackOverflow trying to chase down all these insane error messages which make no sense in Xcode.

I just **happened** to see at the bottom of one of the source files, after all the erroneous error, a very important error:

"};" Expected

So I started deleting code from the bottom up in this source file, same error every time. Got to the point where the includes were all that was left.

FUCK YOU XCODE and the hacks that designed that horrendous piece of shit

Xcode is only free if your time is worth absolutely nothing.

Damn, my boss added me to a "almost" complete protect with a bunch of spaghetti code in a language that I don't know more than the syntax of for loops and declaration of variables (swift) ..... I'm really fucked

Syntax for my proposed "unsure" programming language.

Variable declaration:

let's just say that <variable name> = <value>

Function declaration:

hypothetically, we could <function name> (<args>){}

Try/ catch:

it's possible that
{

}
...or not (<ex>)
{

}

I love brackets on the same line as function declaration and I am proud of it.
func() {
return war;
}

This is the Result Declaration form of our university, It's all good but there is one thing (bug) in this form, you only need to fill the Recaptcha once and you can that same Recaptcha to extract as many results as you want. Though not a Security issue, we can extract results of many students as roll numbers are sequential, we just need a bot to fill roll number and click the button. The only use would be to conduct surveys on results, but, a bug is a bug.

The role of a Product Manager is just a decade or two old. Most organisations, including FAANG, are still figuring out what are the primary responsibilities of a PM.

A vast majority I know, including my dumbass, is struggling to keep things floating while in the role. Learning on the job is one of the only and most effective way to do so.

No wonder, imposter syndrome is so common in this group.

One of the main tasks is to make decisions. Important and impactful ones. The role came into existence to take the decision making load off our engineering friends while building any product.

This shit comes with huge responsibility.

BUT, not everyone understand this. In India, being a developer was a cool thing until 2018 and so everyone rushed into the role. Now somehow everyone started thinking being a Product Manager is cool because all you have to do is sit and shoot orders and things will happen magically.

I get reached out by so many folks every month asking for guidance and when I ask them what a PM does or why they want to be a PM, the narrative is more or less same.

Very few actually understand how taxing the role is or the challenges that we face while performing the job.

WHY THE FUCK ARE PEOPLE SO IGNORANT AND DUMB?

And in another news, my first week at new job was super amazing. Loved every bit of it. People are smart, processes are neat, things are structured, and lots and lots to learn for me.

How are you guys doing? Been a while that we spoke.

Official declaration: I am the dumbest person I know.

Me and my gf are looking for a house. Since we’re both on temporary contract we want a declaration of intent. For arranging a decent mortgage. My gf get’s called and signed within a day, getting compliments and a thumbs up.

I get called after three days; yeah eh we need to talk about this. I can’t sign this right now. A talk with both director and HR. Let’s get stressed...

As devs, our keyboards are arguably the most used tools in the creative process of software development. Shortcuts are essential for (most of) us.

What's your most used keyboard shortcut in your most used IDE? Please explain what it does in which IDE.

Mine is Cmd+Alt+L in IntelliJ (reformat code, but only VCS changed or selected lines). I press it all the time, almost maniacally, after changing anything.

Close second place candidates: Shift+F6 (rename anything, e.g. file, class, function, variable), double Shift (search everywhere), Cmd+Alt+F (find in path, also in code), Cmd+B (go to declaration).

did you know, that in PHP, you can do:
if ( ! function_exists('function_name'))
{
function function_name()
{
//code of the function
}
}

which apparently means you can do
if($var == 'something'){
function functionName(){
//some code
}
} else if($var == 'something else'){
function functionName(){
//some completely different code
}
}

so now, apparently:
1. before this code executes, the function doesn't exist at all (okay, i can live with that)

2. after this code executes, any call to that function can result in any of those two completely different bodies of the same-name function executing, depending on what the $var was set at that time?

...so... now not only the same call to the same(name) function can do two completely different things, *but if you change the value of $var afterwards, you can't even properly find out which version of that function is in effect for the remainder of the run of the script*...?????

WHAT.
THE.
...i mean... I can't help but think that the idea of conditional function declaration like this is... kind of cool (have I been warped by JavaScript too much?), but at the same time... WHAT THE FUCK.

I found this on a wiki with Haskell Humor... it's interesting...

How to Shoot Your Self in the Foot With Haskell: Putting the unsafe in unsafePerformIO!

You shoot the gun, but the bullet gets trapped in the IO monad.
Couldn't match expected type 'Deer' against inferred type 'Foot'.
While compiling your program the compiler produces a type error long enough to overflow a kernel buffer, overwrite the trigger control register and shoot you in the foot.
After trying to decipher the type errors from the compiler, your head explodes.
After you've finally found a way to circumvent the type system and shoot yourself in the foot, Oleg appears out of nothing and shoots you in the foot for coming up with it before him.
You shoot the gun but nothing happens (Haskell is pure, after all).
Your foot is fine, until you try to walk on it, at which point it becomes mangled.
You have a shootFoot function which you've proven correct. QuickCheck validates it for arbitrary you-like values. It will be evaluated only when you end up at the hospital. You hope this doesn't come to pass, as it actually returns a bullet-ridden copy of yourself and you don't want to be garbage-collected.
foreign import ccall "shootparts.h shootfoot" shoot_foot :: Gun -> Programmer -> IO ()
shootSelfInFoot = unsafePerformIO . shoot . foot $ self -- Shoot self in foot 0 or more times depending on evaluation order
No instance for (Target Foot)
arising from use of `shoot' at SelfInflictedInjury.hs:1:0
Possible fix: add an instance declaration for (Target Foot)
In the expression: shoot foot
You go to shoot yourself in the foot but the bullet is in the ST monad and the gun is in the IO monad, so you can't.
You ask Haskell to shoot you in the foot but by the rules of lazy evaluation you don't need the result yet so it doesn't happen.
You decide to shoot yourself in the foot but get distracted devising a ballistics algebra and wondering if you can do the calculations in the type system.
You want to shoot yourself in the foot but realize there is no Gun datatype so use Arrows instead.
You shoot in the direction of your foot, but since you are inside the STM monad you can just retry until you figure out what to do.
You shoot yourself in the foot, but you are perfectly fine as long you just don't evaluate the foot.
You shoot yourself in the foot, but nothing happens unless you start walking.
Don't forget about memory consumption! If you don't look, the bullet causes heap overflow. If you look, the bullet causes stack overflow.
You *appear* to have deliberately shot yourself in the foot, and yet your program actually runs perfectly OK due to lazy evaluation. (So long as you remember to not look at your foot...)
You aim the gun at your foot, pull the trigger and remove the clip. When you look at your undamaged foot, the hammer clicks on an empty barrel.

*My first internship*

Me: Hey, I'm unable to fix this issue with the interface.

Tech Lead: *Goes on giving me a lecture from the very basics* So, An Interface has the method declaration but not the.....

Me inside: I FUCKING KNOW WHAT AN INTERFACE IS JUST TELL ME HOW DO I FIX THIS FUCKING ISSUE.

Me outside: Right!

Official declaration: I am a fucking moron.

Last year, I acted stupid (as suual) and didn't invest enough money into some tax saving instruments.

I also picked the wrong taxation method and ended up paying more than double taxes.

Thankfully my country has an option where you can claim a refund by filing a return form.

And so I go ahead and I hire a finance guy who can help me do my taxes.

We sit at the table and do the math. It turns out my savings mindset prevented me from not investing enough and now it is difficult to claim the tax as refund.

I legit had no issues in investing more. Rather I was looking for ways to do so but I didn't. If I had done it, I'd would be paying zero taxes as my earnings would fall below a certain threshold.

Only trick is to evade by unethical means. Should I be the Jeff Bezos of my country and save my hard earned money from going to corrupt politicians?

Either way, I am a moron. Fucking hate my stupid decision.

How about creating a new programming language named "C slang"

highlights from the language:
1. variable declaration :
by default, all declaration are var, but inorder
to declare a constant, write:
cunt a = 15; // means const a = 15;

2. input and output :
suck(b) // input stored in variable b
spit(b) // output b

3. function declaration:
f**k <function_name>(parameters);

4. null or None will be replaced by sh*t
for example: if(node root == sh*t)....

any other sh**y recommendation will be appreciable

Whoops...
Guess who got their variable declaration wrong?

I should really use Postman

Where was the Declaration of Independence signed? At the bottom!

Debugging a java program for hours only to find that the mistake was a semicolon just after the for loop declaration FML

I just realised I can go to function declaration in Vim using ctags.

Life is so much easier now

!Rant
int[] thumbWar = {1,2,3,4};

I just pulled an all-nighter to write an usability testing protocol in Microsoft Word for a medical mobile app.

- statement of consent and privacy declaration; easy: 1 hour
- structuring the protocol and writing the different use cases; easy: 1-2 hours
- layouting the document so the tables don't look like utter shit and adding dotted lines into the columns so the user can write in it without fucking up the whole document when resizing a simple column width; a fucking nightmare: 5 hours

Why is the creation of a nice layout so inefficient to the point where I'd rather design a form in CSS and send it to my printer, get your shit together!

What are y’all thoughts regarding whitespace, I have a coworker that uses an absurd amount of white space between functions, declaration sections... declarations and logic within functions.... and makes everything very complex without refactoring we talking like 5+ if else inceptions deep.
His code always works never has a issues, but when we collaborate or I work on his files, I wanna cry lol ... he claims the whitespace helps with reading and focusing etc ... “compiler removes whitespace” yes I know that but this is beyond 1 or two new lines lol

I've spent a lot of time messing around with C, having struggled with object-oriented programming (due to not really knowing how best to structure things, not knowing when to apply certain design patterns).

When writing C code, I'd write OOP-esque code (pass around a struct to routines to do things with it) and enjoyed just making things happen without having to think too much about the overall design. But then I'd crave being able to use namespaces, and think about how the code would be tidier if I used exceptions instead of having every routine return an error code...

Working with Python and Node over the past couple of years has allowed me to easily get into OOP (no separate declaration/definition, loose typing etc.) and from that I've made some fairly good design decisions. I'd implemented a few design patterns without even realising which patterns they were - later reading up on them and thinking "hey, that's what I used earlier!"

I've also had a bit of an obsession with small executable files - using templates and other features of C++ add some bloat (on Windows at least) compared to C. There were other gripes I had with C++, mostly to do with making things modular (dynamic linking etc.) but really it's irrelevant/unreasonable.

And yes, for someone who doesn't like code bloat, working with Node is somewhat ironic... (hello, node_modules...)

So today I decided to revisit C++ and dust off my old copy of C++ in a Nutshell, and try to see if I could write some code to do things that I struggled with before. One nice thing is that this book was printed in 2003, yet all of its content is still relevant. Of course, there are newer C++ standards, but I can happily just hack away and avoid using anything that has been deprecated.

One thing I've always avoided is dynamic_cast because every time I read about it, I read that "it's slow". So I just tried to work around it when really if it's the right tool for the job, I might as well use it... It's really useful!

Anyway, now I've typed all this positivity about C++ I will probably find a little later on that I hit a wall with what I'm doing and give up again... :p

Oh wow Elixir, you are so fancy and beautiful. Where have you been hiding! Can i take you out some time? Maybe a small project? 🤓

Variable assignment as declaration is stupid. Looking at you, Python 😑

You can never be sure whether you accidentally overwrite a previous value and you have to fuck around with global because it doesn't know what's an assignment to a global var and what's a declaration. It's just not as satisfying as doing it explicitly and only leads to errors

Pointers like this:
char* string;

Or like this:
char *string;

?

Apparently, DRY is something my team has never heard of. I wonder how many places they need to repeat the same fuckass long declaration in before they would go "hold on..." - so far it's definitely not 4 files

My first PR for DefinitelyTyped got accepted. More PRs in the future

I'm so fucking fed up with the npm ecosystem. Every single god damn time I've had to do anything it always takes DAYS to figure out how to get anything working and I always have to try multiple tools or libraries to final get it half way sorta.
I'm so fucking annoyed right now. They always turn out not that great, have lacking features or trivial oversights in functionality and ALWAYS have garbage documentation.

I just want to build a fucking npm library with TypeScript to be used with node. That's probably the NUMBER 1 use case so how fucking hard can that be?

So obviously I start out with tsc. That's quite simple, compiles all my stuff and shits out .js and .d.ts files. Okay so how do I use them via es6 import? I don't fucking know, because it doesn't work no matter what I do. The 'module' option in tsconfig is absolutely useless btw. It does *literally* fuck all. Nada. Absolutely nothing.
Okay I'm far from defeated, maybe I'll just have to bundle it. So I waste two days finding something that half works (I'm using fusebox right now) and at last I get a stupid es6 module as a single bundle... But what about type the declarations? They are nowhere to be seen and of course there's no option for that. Because Fusebox the pile of shit that's oh so well Typescript integrated apparently doesn't think TYPE DECLARATION FILES are needed. What the actual fuck.

And that's where I'm now. I need the fucking .d.ts files so I can use it as a module with import. Do I really need another fucking piece of shit tool that bundles these files? Honestly fuck all of this. "Oh the Javascript ecosystem is so great" YEAH fucking great, alright. Where 90% of the ESTABLISHED tools and libraries (we don't talk about the landfill of all the other shit) flat out don't do what you need. Again, how fucking hard can it be to make a npm lib with typescript? That should be NATIVELY SUPPORTED. If not by npm atleast by typescripts tsc.

FUCK NPM. FUCK JAVASCRIPT. AND FUCK THE WHOLE ECOSYSTEM

I am ashamed to admit that I only learned recently that omitting 'var' in a JS variable declaration inside a function gives the variable global scope. So that's why it wasn't working properly....

Whenever anyone asks me why I dislike C++ I'm just going to point to this current app I'm working. Had a unit test with an extern method declaration that had 7 or 8 different parameters. No big. Problem is that the ACTUAL definition of the method had 1 less parameter than the extern declaration. It worked perfectly fine in x86. Ported to x64, compiled fine, hard crash at runtime. Debugger not a super lot of help. Took me a couple days to figure that one out. Also I am broke so I can't even drink the pain away. Neat.

I'm a C++/Obj-C programmer finding it ludicrously hard to switch to Swift.

I find that the constant ability (leading to very poor programmer code) to reduce syntax and add tokens reduces readability and nowhere is this more apparent that with closures.

I'm working through (to my shame) Ray Wenderlich's Swift course and the closure chapter has this:

PS I loathe K&R as much as I do Swift so it's all in Allman formatting for clarity.

let multiply: (Int, Int) -> Int =
{
(a: Int, b: Int) -> Int in

// do Something else

return a * b
}
Why oh why isn't this more simply and elegantly written as:

let multiply = (a: Int, b: Int) -> Int
{
// do Something else

return a * b
}
The equals sign shows clearly that it's a closure definition assignment, as does the starting 'let'. But this way all of the stupid excesses, like the 'in' keyword, the repetition of the params / return type only this time with useful labels and additional tokens are removed and it looks and reads much more like a regular function and certainly a lot more clearly.

Now I know that with the stupid ability of Swift you can reduce all this down to return $0 * $1, but the point I'm making is that a) that's not as clear and more importantly b) if this closure does something more than just one line of code, then all that complicated stuff - hinted to by the comment '// do Something else' means you can't reduce it to stupid tokens.

So, when you have a clousure that has a lot of stuff going on and you can't reduce it to stupid minimalism, then why isn't is formatted and syntactically better like the suggestion above?

I've mentioned this on the Swift.org (and got banned for criticising Swift) but the suggestions they came up with were 'use type inference' to remove the first set of params / return type and token.

But that still means the param list and return type are NOT on the same line as the declaration and you still need the stupid 'in' keyword!

- Hey, I need to do X and I need your department to do it.
- "We can't do X, this is against company policy!"
- Oh, sorry, I didn't know. But I will have to justify it to my boss, can you point me to where in the policy it says you can't do X?
- "No I can't, it won't be there. It is just common sense"
- Wait, what? You saying you can't do something because it is against the company policy even though there is no restriction against it in company policy?!
- "Other companies don't do it either"
- I will need you to say that in writing, I need to explain it to my boss.
- "Our email server is FUBAR"
- It can be hand-written
- "I can't give a declaration in name of my department!"
- Wait, so you can interpret company policy any way you want, make decisions regardless of what the policy actually says but you can't own up to it in writing?!?
- "..."
- ...

(Some context: I've been emailing them about X for more than a week. Just got crickets for a response. Not even an evasive coward response, just no answer at all. And calling them leaves no paper trail. Fucking oxygen thiefs)

For fuck sake, are non-tech departments always filled with complete morons?!? Does anyone have ever worked with smart, or at least minimally-coherent non-tech people?!?!
Seriously, does anyone there have some story about some non-stupid non-tech/analog/muggle coworker?!?
I'm inclined to think that anyone who can think systematically is either working in tech or not working at all.

Dear programming languages,
If you had to be case sensitive, then why the fuck can't you settle on whether to use an S or an s for a
S/string declaration.

I had a developer put the css font declaration on every css class, instead of the body... The site used just one font 🤔😂

Java rant...

If public field declaration is so so bad, why can't all class fields in java just be private by default? And make it a pain in the ass to expose it as public?

I can't actually remember a time declared a class field as public, it is muscle memory now... Private bla Bla Bla, return, private bla Bla, return...

Am I the only one who's so fkin fond of the ES6 function declaration of (params) => {//code} over other declaration types?

Today a member of an other team said that React would be better than Angular 2. Mainly because React allows HTML inside the components declaration and One-Way-Data-Binding.
Me then: Sure, but Angular 2 also has this features 😞

spent 2 days trying to figure out why my css was working fine on one page but not another. found it was due to the doc type declaration on one of the pages was mad about me not putting height:100% on a parent div. smh

A highly efficient reusable pattern declaration and parsing engine.

Where was the Declaration of Independence signed? At the bottom!

CSS4 seems to add some cool features. But my favourite will be the new color declaration. What is yours?

I just spent about 4 hours debugging a PHP bug because of its weak type declaration. Some please point me to another language, Im done with PHP.

Dear Prestashop developers, f**k YOU!

I already hate this shitfuck what you call the best open source e-commerce solution, but your module validation technique sucks.

They use tons of useless rules, but the last addition was the last drop: they force you to use the old (and long) array declaration.

So now I have 500 new errors in this fucking module.

Why the fuck do you want me to force an old syntax?

Doesn't Python kind of contradict its own mantra. When they write explicit is better than implicit but at the same time they provide collection literals?

Not a fight per se, but I once had a debate with a tech lead who thought you could set a variable in the ‘then’ clause of a Javascript promise and just use said variable after the promise declaration and assume it would be populated.
“no.... thats not how asynchronous code works.”

I have, once again, figured out why I keep dropping C as a language. The answer is because the errors are incredibly unhelpful and actively want to implode your brain.

Examples currently being spat out by gcc for my driver:

`error: conflicting types for ‘block_read’; have ‘ssize_t(struct file *, char *, size_t, loff_t *)’ {aka ‘int(struct file *, char *, unsigned int, long long int *)’}`
`note: previous declaration of ‘block_read’ with type ‘ssize_t(struct file *, char *, size_t, loff_t *)’ {aka ‘int(struct file *, char *, unsigned int, long long int *)’}`

`error: initialization of ‘ssize_t (*)(struct file *, char *, size_t, loff_t *)’ {aka ‘int (*)(struct file *, char *, unsigned int, long long int *)’} from incompatible pointer type ‘ssize_t (*)(struct file *, char *, size_t, loff_t *)’ {aka ‘int (*)(struct file *, char *, unsigned int, long long int *)’}`

Go character by character for those types as listed, and tell me where they differ, because I can't find it.

Hey devRant! Long time no see
I recently landed a job as a java developer so that's amazing
Still getting my head around the company's codebase, and holy fuck its huge.
I was taught best oop practices and patterns in CS class, but seeing them implemented in such a huge project is kinda pisssing me off: every single thing in the code has dozens of classes that call and implement each other, I spend half my time spamming the "open declaration" shortcut in a futile attempt to understand how the pieces fit together.
Sometimes I wish they had stuck to implementing everything in a handful of files, instead of the jungle of nested packages and references I got :pensive:
Oh well at least most thing are documented :shrug:
I kinda get y some people despise java for being so verbose and forcing strict pop on the programmer XD

Where was the Declaration of Independence signed? At the bottom!

Just use a promise that sets this variable, and then you can use the variable as long as its after the promise declaration.
No, just no. Thats not now asynchronous code works.

Sydochen has posted a rant where he is nt really sure why people hate Java, and I decided to publicly post my explanation of this phenomenon, please, from my point of view.
So there is this quite large domain, on which one or two academical studies are built, such as business informatics and applied system engineering which I find extremely interesting and fun, that is called, ironically, SAD. And then there are videos on youtube, by programmers who just can't settle the fuck down. Those videos I am talking about are rants about OOP in general, which, as we all know, is a huge part of studies in the aforementioned domain. What these people are even talking about?
Absolutely obvious, there is no sense in making a software in a linear pattern. Since Bikelsoft has conveniently patched consumers up with GUI based software, the core concept of which is EDP (event driven programming or alternatively, at least OS events queue-ing), the completely functional, linear approach in such environment does not make much sense in terms of the maintainability of the software. Uhm, raise your hand if you ever tried to linearly build a complex GUI system in a single function call on GTK, which does allow you to disregard any responsibility separation pattern of SAD, such as long loved MVC...
Additionally, OOP is mandatory in business because it does allow us to mount abstraction levels and encapsulate actual dataflow behind them, which, of course, lowers the costs of the development.
What happy programmers are talking about usually is the complexity of the task of doing the OOP right in the sense of an overflow of straight composition classes (that do nothing but forward data from lower to upper abstraction levels and vice versa) and the situation of responsibility chain break (this is when a class from lower level directly!! notifies a class of a higher level about something ignoring the fact that there is a chain of other classes between them). And that's it. These guys also do vouch for functional programming, and it's a completely different argument, and there is no reason not to do it in algorithmical, implementational part of the project, of course, but yeah...
So where does Java kick in you think?
Well, guess what language popularized programming in general and OOP in particular. Java is doing a lot of things in a modern way. Of course, if it's 1995 outside *lenny face*. Yeah, fuck AOT, fuck memory management responsibility, all to the maximum towards solving the real applicative tasks.
Have you ever tried to learn to apply Text Watchers in Android with Java? Then you know about inline overloading and inline abstract class implementation. This is not right. This reduces readability and reusability.
Have you ever used Volley on Android? Newbies to Android programming surely should have. Quite verbose boilerplate in google docs, huh?
Have you seen intents? The Android API is, little said, messy with all the support libs and Context class ancestors. Remember how many times the language has helped you to properly orient in all of this hierarchy, when overloading method declaration requires you to use 2 lines instead of 1. Too verbose, too hesitant, distracting - that's what the lang and the api is. Fucking toString() is hilarious. Reference comparison is unintuitive. Obviously poor practices are not banned. Ancient tools. Import hell. Slow evolution.
C# has ripped Java off like an utter cunt, yet it's a piece of cake to maintain a solid patternization and structure, and keep your code clean and readable. Yet, Cs6 already was okay featuring optionally nullable fields and safe optional dereferencing, while we get finally get lambda expressions in J8, in 20-fucking-14.
Java did good back then, but when we joke about dumb indian developers, they are coding it in Java. So yeah.
To sum up, it's easy to make code unreadable with Java, and Java is a tool with which developers usually disregard the patterns of SAD.

When you learn a new Framework and pretty much understand everything of the Tutorial and then a major declaration changes and you don't know what's going on 😞

Random thoughts...
Just implemented policy-based authorization in dotnet core, long story short to lock an endpoint to a certain policy I just add: [Authorization(Policy = "NAME")]
on top of function/controller declaration

Was wondering how it is done in other languages, like NodeJs, Java, Kotlin ...etc

I genuinely want tp know why few devs don't add the opening brace on the same line as method/class declaration ??

Whenever I find a piece of code which follow such style a part of me cries thinking of the time I'll be spending first correcting...

Trying to update and add to my skills. Let's try angular,. Visual Studio sucks for this. Hey look vs code, this looks great.... Install, add some recommended extensions... Cool. Add eslint, hey look at these errors awesome I'm getting somewhere. WTF dont use var use let.. Ok why... Hours later and one drink, okay that makes sense. Change code.....
Unexpected declaration wtf why. Switch to var... Dont use var..... Fuck me... Google, read, google, read...... Wtf why why why won't this fucking work... I just want to code something using best practices

Unable to understand difference between variable declaration and definition. Can anyone help?

Has anyone used plpgsql? You almost have to sacrifice a goat during the function declaration in order for it to work.

Let us all have a moment of silence for the wasted lines used for individual variable declaration... we were so young and so dumb... YOU ARE IN A BETTER PLACE NOW!!!

Where is '*' in the variable coffee declaration?!! ;-)