My 2 cents...

I used SO extensively when it first arrived. It was great. Really helpful people and I got answers pretty quickly.

These days, I try to avoid it. As a long time user, I am used to researching first and making sure my posts are well formed. I even make sure I read the suggested duplicates, include the links in my post and explain why they don't answer the question. Some dicks still close the post as a duplicate of the thing I said wasn't a duplicate.

I'm all for cleaning out the crap but seems to me some mods just love trolling the site.

And @Fast-Nop, sorry, you're wrong. SO IS a Q&A platform. You'll just have to deal with it.

"I wonder if talking to a marketing type..."

;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D ;D

That's a "no" from be, btw.

You don't just get a certificate and get a job unless you're extremely lucky. Unfortunately, there's too many unemployed people out there with more certificates/qualifications/experience than you going for the same job. Only thing you can do is keep applying. On the side, as others have said, work on your own projects. Create your own website. Create an app; doesn't have to be fancy, could just be a simple game. Look at flappy birds!! Some recruiters will pick up on this. Some will be looking for people for whom computers is a passion.

Too long to write???? Spoken like a true noob! :D

Do you also name your variables/classes/functions in as few characters as possible to make others lives harder (as well as your own a year down the line when you've forgotten what doStuffFn() does!)?

It's clear and concise. It's nice being able to read code and just know what it does without having to have spend a year learning it.

I just got to add my 2 cents...

When I first started using SO, oh my days I was a happy little developer.

Forward to now...
You have to list all the other SO posts you have read detailing why they are different to your question and hope some f-tard mod STILL doesn't close it as duplicate.
Still get some nonces, who know very little, searching for your question and closing as duplicate cus there were more than 0 search results.
Lot of good members have fled cus of all the point system/moderator bollox.
Posts keep getting edited by point hungry mod-wanna-bes. IME, sometimes for the worse.
As of late, they appear to have let some marketing types loose. Now SO keeps getting changes that are of no use or degrade the site.
List goes on...

RIP SO

Sad fact in IT that there's a lot of pompus, arrogant scunthorpes that got where they are by shouting louder. Shit managers will listen to them and accept their shit because they sound confident.

Side effect of this is that the little twerps actually start to believe they are as good as their managers perception of them. Once they've got to this stage all you can do is hope that a senior figure recognises them for what they are and gives them a dressing down... or hope they get run over.

@null-pointer-ex +1 that.
I've always gotten on fine with eclipse. Sounds like dodgy plugins. Always been faster than netbeans. I've tried intelliJ but only a bit, looks good.

Imagine my surprise when moving to Android Studio :O what fuckery is this????

I'm lucky enough to have worked in companies where you're expected to work overtime for free... but they turn a blind eye if you leave early/arrive late. And if asked to work considerable overtime they make some recompense, normally time off.

It depends on the company and your boss. If you like your boss then do him a favour and expect one in return. If you want to climb the ladder then expect to go the extra mile. If you know your extra effort will never be recognised then up to you; don't do it or do it to make yourself feel good.

Anything I did as a junior dev, I would check.

As a senior dev, generally have the belief in oneself that I did a good and full implementation as code reuse is one of the fundamental tenants of software development (not all would agree, but hey, some people have the time and inclination to re-invent the wheel. I'm not saying that's a bad thing. Some wheels are shitter than others!)

@wisecrack touché, I agree whole heartedly. Why do folk keep coming up with 1001 ways to do the same shit? It's basically more ways to cause confusion between dev's and cause a FU!

Basically what you got is a war between ES6 and CommonJS.

This is how I understand it...
- node uses require
- react uses import
It's to do with static/dynamic loading so react can get rid of unneeded imports.

"module.exports" and "exports" are almost the same apart from when assigning a function. It screws it up for some reason. Just stick to "module.exports" and you'll be fine.

"export default class Arse" means you can use "import AnyNameIWant from ..." but "export Butt" without 'default' means you have to use same name when importing and you have to use curly brackets -> "import { Butt } from ...."

"import Arse from './Butt'.TP", all you're doing is referencing TP in Butt.

@LucasLarson according to me???? Abso-bloody-lutely not!!!! At least my code would work :D

@gitreflog thats nicer, thx :)

I'd just like to add, I'm loving some of the other syntactic sugar. Shame java not catching on quick enough.

Only if it's immutable

if (nfcAdapter == null || !nfcAdapter?.isEnabled!!) {

soooooooooooooooooooo ugly :(

I can see Kotlin was trying to do something to avoid all those null checks and NPEs but to me it just appears all they have done is introduce a lot of fluff for dealing with nulls. When I see people defend it, perfect example is @gronostaj lock analogy, it's not really a good defence (I honestly mean no offence). If you're designing a safe lock which won't let people in then don't add potential design flaws! Whether or not you use the '?' your design still has to take into consideration when a reference may be null.

What I've learnt is my estimations are always optimistic and don't take into account such things as interruptions. I finally learnt my lesson and caved. Now I just double my estimates! Thing is, they are usually fairly accurate now!!

And to expand on @angelbetancourt point, sometimes the spec is written by HR who haven't a clue what's going on.