I think this fits well in the context of software refactoring. Sometimes cleaning up existing code just isn't practical.

You got 3 useless vars in your code.

Just kidding. Happy new year!

I like it how C is represented by what is basically a bullet and a hammer — even if you could make it work and fire the bullet, the sound and the raw recoil would still terrify you to death.

Fuck man this is actually brilliant.

Claims he won't use shortcuts while coding yet he uses an IDE. 🙄

Don't they have a toggle to "opt-out" and display function keys on the Bar instead?

Pretty!

Isn't the general consensus is to code in English?

Short answer: www.yegor256.com

Long answer: Getters/setters supposedly make your classes/objects less OO. Since most will tend to over-abuse them and turn all of their classes into "dumb" databags. OO dictates that any data should not be exposed to anyone. You ought to expose only the flow of logic/interaction of objects but never more.

While that sounds nice and all, actually trying to stand by those values in the real world translates to pure pain. Workable for small projects, borderline impossible for bigger ones.

Yeah and when you spot a burning bridge ahead, keep your hands on the wheel and foot down the pedal. That fiery fire is nothing but a mere illusion. You'll make it through. /s

Having an OS built from the ground up with powerful console interaction in mind makes for a good dev environment. That said, committing to Linux means that you will spend more time getting stuff right on your own at times.

But first and foremost, use what you think is best for you. The competence of a developer shouldn't be affected by what OS he/she prefers to be in.

@nik123, well, I guess you could always go for something like Atom, Sublime, or even Vim since the build system is not an integral part of Studio.

@ClemFrieckie, everytime I tried to plan my project I tend to overthink the possible scenarios and thus rarely finish the actual work in time. It might be that I'm just not on the same level you are skill-wise, but that's been my experience.

Working the duct tape way, on the other hand, helps my intuition to find the right amount of solution. Although what you said is true: I do tend to spend more time revisiting my classes polishing and refactoring from time to time.

Slap on some liquid cooler there too while you're at it. 🤣

The general consensus I've been getting from various discussion online is this: If you are new to programming in general, go Java. Otherwise, Kotlin all the way.

Just a heads up: If by any chance you got Fabric's plugin installed, that might've been the culprit. I've read a thread on Reddit the other day discussing how damaging Fabric plugin has been to build times. A shame considering their analytics and crash reporting solution is second to none, IMO.

@hausen, I wouldn't touch a girl with a hardware with a ten foot pole.

Software on the other hand...

@filthyranter, it's doing to Java what Swift is doing to Obj-C. And then some.

JetBrains made a perfect decision when they decided to build on top of the JVM as opposed to making everything from scratch.

@MrHadiSatrio, holy grammar, Batman!

@theScientist, you're right. But it was my first web scraper. After seeing my colleague painstakingly manual-scraping data from some site, I decided to help him out. Figured to go with Phyton after hearing the praises people often throw at it.

You can say that again. On my first day learning Python, I went from "Hello world" to a working web scraper in under 6 hours. And it's not like I'm a whiz or anything - the language is just that good.