Well, since a long time ago, i could not accept that some developers would title themselves as "Front-End Developer", or "Web Developer"...

It's like WTF!!! You are a Developer, why would you want to stay just in web development? if you're a developer you can move on anything you want anytime!! Why are you locking yourself just into "Web Developer"?

Well, that's my rage... Lots of answers from friends, basically, they are all afraid of tools they've never used, and they don't even bother to try them out.

I like to do any kind of work, from deployment scripts, load balancers, distributed computing, web front-end, desktop front-end, mobile, database, hell, i like to be part of all the entire project!! I've have a lot of luck because i've always been in small companies, and maybe we don't deliver the best solution, but the solutions work, and work really well, i have developed lots of systems, and they are not a headache to support, so i'm proud of what we have achieved...

But recently, when people ask you "what kind of developer are you", you can't just say "i'm a developer", because, i don't know why, but people assume that you don't know Web, SQL, FrontEnd, etc... And magically, a "Web Developer" is way better than just a "Developer". That happened to me lots of times, just because my title said "Developer", people that didn't knew me don't consider me for projects.

That's why i am now using the "Full-Stack Developer" title, you just can't use any other title on today's market. I don't want to be doing just "Web Frontend", or "Database Administrator", or "CI Manager"... Heck, i want to participate in all the project.

And i agree with other people here, a Full Stack doesn't needs to be a guru on every language/framework. You just need to know how to assemble everything to make it work. And it WILL NEVER be perfect, because requirements change everyday, but your stack can evolve to adapt to those changes.

Same goes for a "Frontend Developer"... A frontend developer can be really bad frontend developer, but he's a frontend developer because he wants to do only that and is happy whit that...

I believe a Full Stack developer is a guy that is not afraid to solve a problem in any stack of the system, not a guru or a genius.

Well, that's my point of view.

Well, each time a new article claiming that HTML5 has better user experience (as stated by this article "Speed and user experience"), i can't find an app that feels just right made with HTML5.

Just can't find any HTML5 app that feels better than a native app. It doesn't even feel the same, at least to me.

I've seen great apps, with great user experience, but all of them could be a lot better if they were native.

Just my opinion, no disrespect to anyone, and i'm not saying i won't develop an app with HTML5, i just think that we just can't compare them, so we should stop comparing them.

I wonder why nobody has trademarked the word "birds" by now...

Wow this engine is really amazing... Need to start stressing it out to se What's its made of...

Congrats

> Isn't this more or less a problem of the past?

You are using Unity 3D, so NO, it's not a problem of the past. You have multiplatform because Unity developers decided to go with OpenGL.

Hmmm, meybe i'm getting this wrong, but... Isn't a color code too basic to be in a card in your pocket?

I mean, c'mon, i haven't used color codes since High School about 17 years ago and i still remember how to decode them. It's not that hard.

i feel that consulting a table is more time consuming that knowing how to decode it... Usually while working with prototyping you end up with lots of resistors, and i can't see someone checking each one at the time against a table to reveal it's value...

But maybe i'm getting it all wrong, someone?

If you're breadboarding a lot, or manually stuffing printed circuit boards, or otherwise doing manual assembly in some way, you quickly learn to read most common ranges of values on sight. Maybe some people like to keep a reminder around for when you encounter weird values, or when troubleshooting.

I need to color-code a resistor a few times a year. To do so, I usually consult the table on the wall in our electronics shop or just grab an ohm-meter.

If I needed to do it daily, I'd get real good real fast.

Yeah, 3-4 months seems too little to expect some income... This guy just wanted to make it big, and wasn't in the mood of creating new features...

All he was doing is what he wanted with the product, not what the potential customers need... I agree that you cannot do everything that the customer ask for, but from my point of view, this guy doesn't even knew the needs of his target market.

Wait, so, they were expecting to develop agains an X version, and then after release, when they release the source it will compile easily for all it's users with zero dependencies problems?

I don't see how bashing Go would help these guys out of the hole they are in, same would have happened with any other programming language in a project that uses fast-moving dependencies...

They were making a game, they could have just forked the projects they needed, and build from that, that's the way to do these kind of projects, you stick on a revision, and when there is an update on a dependency, the team should agree to make the upgrade changing all the required source code.

For what they say, the main developer had no idea that the repositories were changing a lot, and he never updated them, so everything was going thru smoothly... I don't see the need to bash Go, neither the main programmer, i just believe he needed more experience to handle the project correctly.

What i don't like is their attitude "nobody can fix this Go garbage code because Go is all wrong"...

As a 3+ years of playing every night, i will have to disagree. The weapon spots are not important... The replayability comes with everything it provides. I have over 1 tb of dem files because i record every single match since start, and i still enjoy it.

Oh, I don't think the game is not replayable, I had a lot of fun playing it and L4D2. I just don't think it was at all obvious accomplished their goals with the director AI that they set out to. Hence "replayability section" (directly referring to the PDF)

I belive the 1% example is referring to trust your heart even when people discourages you but you know your idea should work...

Also i belive, being able to take orders is very valuable to the team, even if you are the ultra master chief... Closed to not taking orders? Then you are starting with your left foot in being a leader...

Just my thoughts...

Actually, I think part of being a good leader is not ordering people around, but inspiring, guiding, and teaching them.

I don't mind taking direction, but traditional management turns me off.

Yeah, you're right, that's a better approach