I don’t know about you guys but, IMO, the first skill listed on pretty much all of our resumes should be: Google

:P

Sadly I don’t think this kind of thing is uncommon. I agree that you could likely fight it in court and win (assuming your side project differs enough from the companies line of business) but at non-trivial cost.

Something that might help in the future is to mention any side projects when you’re hired and that you intend to continue working on them as side projects. I even went as far as forming my own company to do the work within. It’s actually made the conversations easier b/c they know you’re serious about it (so long as you’re acting in good faith).

Wait, hold up. You mean that we’re *not* supposed to write every function in the same class?! ;) /s

That Sam Harris stuff looks cool. Thanks for mentioning it; I’m checking it out too!

Lol, to serve you ads of course!! :)

@ScribeOfGoD, thanks, just wanted to make sure there wasn't something I'm missing. :)

I've done some Xamarin devving. Need any help or just looking for peeps?

Angular 4 is out now btw :)

So what of TypeScript then? :P

@codeRetard no, fuck him if he writes crappy code. The vast majority of your code shouldn't require comments for future maintainers to understand. If it does, you failed and wrote crappy code and that does suck.

Generally speaking I whole-heartedly agree with Robert. That being said, I agree that there are some scenarios where comments explaining 'why' something is done make a lot of sense (especially in scenarios where you have to use less-than-obvious code for performance reasons).

Also comments that become documentation for an API are acceptable (XML doc, jsdoc, swagger doc, etc.)

I'm personally a fan of R#! I've been buying my own personal licenses for years now. The keyboard shortcuts for navigation and refactoring​ are incredible.

It's a massively helpful tool especially if you're working with medium to large size code bases.
It has some nice linting features not in VS yet too; like possible NullReferenceException highlighting, dead code dimming, etc.

Plot twist: both are done in React ;)

J/k

OMG, this one drives me crazy. Delete it already :)

Yeah, not a fan of most comments. Would prefer to refactor the code to make more sense/be more readable.

Problem is that sometimes comments lie; code never lies tho.

Good question! Probably psychiatrist/psychologist....Possibly school teacher (math or science if I'm not allowed to teach tech)

@linuxxx omg, literally loled at this

@Traser source code is the ultimate comment; it never lies!! ;)

@blastosnr hmmm, that helps to explain some of the disconnect.

Please don't take any of this as disrespectful; that isn't my intent.

Is my $10/hr estimate too high for a dev in your area? It's been awhile since I've looked on oDesk, eLance or rentacoder but I thought most devs could pull at least that amount globally.

If a user is able to use devRant then they must have an Android or iDevice (or a PC). They likely also have monthly cellular service or home internet (unless they get free wifi somewhere...but I think most places that offer free wifi would expect you to buy something... or pay for the wifi like in an internet cafe).

Given all that, charging $1 or 2 for the option to remove ads from a service that you use on the regular doesn't feel unreasonable. Does it? Am I missing something?

@blastosnr

2. We've already established that most of us are devs. We, of all people, know what it takes to deliver good, quality, software. We know about initial development costs, ongoing maintenance costs, hosting costs, licensing costs, domain name costs, etc. Why would we begrudge a fellow dev of a few bucks to support the software and community that we visit, use and enjoy regularly?

There are other reasons too but I'll settle down for now. :)

One important thing I would add as a note to @dfox and @trogus: If you do add some form of ads, PLEASE give us the option to buy our way out of them.

@blastosnr I could write a whole blog post about this but I'll try to keep it short. :)

Yes, we're all devs. Could we get around the ads w/o paying? Sure. Should we? Probably not.

Why?

1. It's not cost effective to do so. Let's assume, as a dev, I make $10/hr coding (this is a low estimate but I'm being conservative). How long would it take you to disassemble the apk, patch it, rebuild it and reinstall it? 10 minutes? I think longer but let's go with that. That's 1/6th of an hour (10 minutes out of 60 minutes in an hour). So you just spent $1.67 of your time ($10/hr * 1/6th of an hour) in order to save the $1 it'd have cost you to buy the ad removal upgrade. Was it worth it? For some devs maybe. For most of us, omg not even close.

To be continued...

Fully agree right up until the last sentence.

The fault lies with the site owners, IMO, not the marketers. Site owners shouldn't be overloading their site with ads so much that it performs so crappily.

Tell them that with your eyes/clicks (aka, don't use the sites that do this)

Yeah, to call it from a public static function is the main reason.

Sometimes you want to encapsulate/organize functionality but not actually expose it on the interface of the object.

GTFO, that was what my highschool 'computer class' was too! Mine wasn't Excel and PowerPoint though; we learned how to use WordPerfect 5.1. In DOS.

#wp51baby #holyshit #amithatold

:/

Personally I don't see anything wrong with both.

Add simple banner ads at the bottom of the pages

Give the option to purchase an ad removal feature

Could also get a little more creative... No ads during your first two weeks or something. Then pop message explaining ads and offer ability to buy out of them if desired.

I wouldn't blink at paying a buck or two or three to support the community and not have to see ads.

Lol, feel for you dude. Good luck!

Your hate for that is justified and you're not the only one. Look up: 'arrow head anti-pattern'

Your fix is also known as 'guard clauses'.

I find myself stumbling upon, and fixing, these frequently in a few of the codebases that I work in. I feel your pain. :)

Lol, what the hell happened there dude?! :)

Personally I'm a fan of (and have had success with) Xamarin.

Regular Xamarin though, not the Xamarin Forms stuff.

Lately NativeScript has peaked my interest but I don't have any concrete experience with it yet.

Omg, wish I could ++ this 100 times. This is totally my office if I forget my headphones!