littletinman

I used to work at a two design/web agencies and left the design agency (as a developer) because of emails and discussions like this. For about 3 years I kept wondering "Is this every developer job? Turning accordion into dropdown, then into a grid, then into an endless scroll FAQ?" Finally I got a job working backend on enterprise software and have never looked back.

This thread is the first thing to remind me of all the stress I endured just a few years back.

My question is, how do we change this? That work was fun, but the high stress from either directors or CEOs or clients constantly changing their mind was overwhelming.

BEST NEWS EVER!!! Since I only have old cartridges on a wall for display, I'm actually pretty happy I won't need to use those.

Anyone else thought about the fact that now that they have removed this feature, they have put the "job death" sentence on those that accidentally used it and would have had a reasonable explanation to their boss?

"Look, this button is right here and I thought it was send." Now a non-technical boss will just assume that person is lying because no button is in gmail anymore. Thanks Google. Stay Classy.

This is no surprise as comcast has been and continues to be the worst internet provider in the US. I worked for a startup in Washington DC and internet would cutout for 5 minutes every hour. We called comcast dozens of times and everytime they said there were no reported issues on their end.

Twice internet went out for 2 days and only then did they admit there were problems in the area.

I've had them at home with the same problem: intermittent and occasionally completely out for days.

1000 times better! My eyes stopped bleeding!

For me it's more about what I put in to it than what I get out of it. I realized really quickly I wouldn't make much more than beer money out of this hobby.

I think the most difficult thing about the video game industry is the amount of drama in the hobbyest scene. Still trying to find a "group" that isn't jumping on the latest "cause" rather than feeding in depth discussions of randomly generated worlds.

This has been my strategy for the last few years. I've been making games on my own dime for just a few years but I now have two self published games on Steam, and a few Micro-Consoles, and a Job in entirely different industry with great benefits and hard stop 40 hour weeks.

I absolutely love programming games! It's the most fun programming I've ever had in the 10+ years of writing code. Nothing beats showing off your creations with family and friends and them "getting it."

I've gone back and forth of whether I should join the industry but with a kid and high priority of family time, I just can't do away with what's actually important to me. I've never regretted working a solid job to support an awesome hobby.

With the current instability of the entire industry, and my genuine disinterest in console or mobile development (one market is fading and one market is too cluttered) no matter how I run the numbers it would take at least 5 years before I would see profit.

I'll keep running numbers however and figuring out timing and niche!

The one thing that stuck out to me is the "resident artist". I'm curious is that the person's only role? Will more companies look at the talents of their employees and enable them to pursue their real interests? Is this even feasible to propose?

My dream job is to be a resident Game Developer for a non-game development company. Literally paid to make whatever games I want, no manager micro-managing me, no committee telling me what to make or what "they want int the game." This article gives me a small amount of hope that one day I could do this, but my question above is the big "speed bump."

Thoughts?

LOL! My comment is more on the perception disconnect that can take place. When I was a teenager I didn't yet have the experiences (being told what is or isn't appropriate and why) to know what was not ok like that.

To one extreme, this could be a case of "an unsolicited pat on the rear" being perceived by the offender as "a high five" and to the offended "a disturbing invasion or personal space."

On other extreme it could be he "chucked a tennis ball and it broke an office window." Everyone's perception these days of the extent/effect of any offense seems to broad that without details... what's the point of articles like these?

This is another one of those "I got fired but I won't tell you why" posts. There was another post on here not too long ago about a guy, who for very vague reasons, got fired from Google.

I don't understand why you wouldn't disclose why you got fired if you are going to write a post about how you feel after getting fired. It doesn't help anyone else because we don't know what mistake you made that we should avoid. It ends up feeling like the post is very one sided and IMO discredits the presented "feelings".

My 2 cents for you. :-)

*edited: spelling

I used YourMechanic for the first time in Denver Co just a few weeks ago: blown away by how easy it was. It absolutely felt like this was not a rushed endeavor and that paid off big time. I will be using them for the foreseeable future.

Any chance you have a parts list for your build?

The site says last modified in 2008... Might want to add (2008) to the title.

It looks like a cool concept! It seems like a slightly more "code focused" Scratch.

When I read the "Dear GitHub" repo my first thought was, I agree with some of this, but my overall attitude toward GitHub is gratitude and the flexibility to create whatever repo standards you want to. I then saw the "Thank You GitHub" repo and think it's a great way to express that gratitude!

I personally do not view these as rival repos. They just express different sentiment and serve two purposes (again not apposing each other).

Does this have to be viewed as a polar opposite response to "Dear GitHub"?

Shots Fired!

Oh how I wish this existed 10 years ago when all I had were library books and w3schools!

I hope so! As a kid, this would have realized so many dreams! Going on my list of tools to get!

I want... NO.... I NEED this! The price seems surprisingly reasonable for the amount of household items you could create that you "Forgot to get from the store."

Looking through the codebase for these to assess the teams review health is a fantastic idea!

This should be renamed to: "Common red flags to look for in merge requests and code reviews" and handed to every rookie, mid-level, and senior developer on your project!