When you're really senior - you'll understand

Lisp: spaghetti ain't Italian, I invented it ;)

Being wise about you dev tools is using VSCode (remote pressure)

With the exception of other free thing from MS.. like Visual Studio Community edition

You mean those who write shitty code that needs commenting and those who write readable code that does not need comments?

@slar I'm married and have a daughter, not much time to learn at home.
That's why I learn at work. If you work at a place that doesn't give you the opportunity to learn and improve, find a new place.

Why bother doing a bachelor's degree if you don't remember anything from it?

Fuck side projects, you'll have you whole life to code.
Go party, drink, hit up some friends, party with chicks... In 10 years you'll be deep in work, when you'll party?

Begin a DICO (Daily Interrupt Chief Officer) regime. Each day some one else will eat the shit from all the interrupts and get better domain knowledge to the point where there is no longer "junior" "senior" knowledge separation.

@ninjatini documentation !== Commenting the code.

Leaving documentation of what a method expects, what it returns and what it does is great, especially for external interfaces. BTW a method, interface should never do more than it's name suggests and never should do more than one thing. Understanding what a method does solely out of documentation and not the name+prameters+response is a red flag for a code smell.

Commenting an if statement is wrong because it means the logic of this if statement is too complicated to understand from reading the code, hence the comment is an excuse for writing poor code.

@ninjatini documentation as in javadoc style is great for future reference and maintenance, and for every bug fixed - unit+functional+integ/e2e tests added. Of course code should be thoroughly tested with meaningful e2e tests that describe the system use case flow.

Comments inside the code should be rare and sparse since no one will maintain a god damn comment.

a broken test === broken build === red in the CI === notifications in NATO distribution === developer fixes the code or adjusts the test to systems flows.

Well commented code is shitty code that need excuses.

Code should tell what it does, not how.
If your code is telling "how" and not "what" you should refactor it.

Fix it. You'll be sorry you didn't in the future. Code tend to become legacy very quickly if you don't keep clean code and good development practices.
We have a project the was supposed to be legacy replacement, due to poor code style and lack of practices it's informally called LegacyVNext.

@shantnuchaubey maybe you are limited in funny stuff and fuck with code... Some of us actually have a life mate...

I can swear some one here uploaded this image and said it was his son

@anth12 I'm getting sick of kids who wrote some Hello world program and think they have a minor clue of how to write real software, such that will make you a billionaire and not just pay the bills.

@VirtualProtect did you ever write any single line of code that ever was as profitable as any software in Microsoft portfolio?
Bet their fucking solitaire freebie made more profit than anything you've ever written.
Hate it when people shit on stuff when they've never done anything meaningful

@Jop-
a. Some users don't know they can update/change.
b. Some users don't feel the need to update/change.
c. Some users might be restricted and cannot update/change.
d. Some users don't know how to update/change.

As long as these users are bringing revenue to your site/application you should support their platform as long as the investment doesn't out weight the benefit.

@erik404 ouh you mean you don't want to do frontend... Then don't do, what's the problem?

What does that even mean?

After using numerous IDEs I really think VS+resharper is the best, but you can also use:
VSCode
Rider EAP
Xamarin Studio

Why were you waiting? Start working on unrelated things and queue the bug for when he is ready to go with you over it.

@CorruptComputer well you are building the site for the users to use not the browser. As long as your target audience uses IE11, not supporting it will be losing revenue.

@CorruptComputer following your logic you should support only 7.1.2 and O DP4
Why bother supporting 5.* or 6.*?

I know it's not popular to say "chill mate and support the client" especially when it has anything to do with MS tech.

@CorruptComputer @Jop- so...?
Android 4.4 is old too but still supported, you cannot always only support the newest version, you have to cutoff at some point where you support the majority on platform users with in reasonable investment of deployment.

if those are the choices - cobol

What's the problem with ie11?

naaaah, you're wrong.

@kp15 Indians outsource to Indians?

yo dog I heard you like outsourcing, so I outsourced your outsourced work, so you could outsource while outsourcing...🤣😂

That "job" is called pension mate...