> > See you there bud. Bring your copy of Construct with you, we will all be fascinated. You could do a demo - wear one of those headset/mic thingies.
> I'm totally serious, actually. Shoot me which talks you're going to via PM and we can talk the realities of game development face to face. My company is having us share passes, so I won't be there every day, but I'm sure we can make it work. I'm generally interested in the design track stuff since that's my day job, but whatever, the place isn't that big.
Well, look at you. A "serious" game designer, with all the bells and whistles, and using Construct - what are the chances? As much as I'd love to chat "shop" with a total stranger, 'face to face', from a forum, I will decline your offer.
And before you suggest it, you're right - I'm declining your invite because I've never worked at any major software company and have never written a line of code. You win my friend!
Frankly your snarky attitude and manner of speaking makes it obvious that you aren't really a professional, despite your mockery of people who consider themselves developers but don't share your opinions on tools. Real developers don't speak to one another the way you're speaking to all of us. We generally support and respect each other. We keep things civil even when we disagree. We don't mock people trying to get started in making games no matter what tools they choose. Making games is difficult enough without this kind of petty, childish sniping, and if you bring this kind of attitude to a job in this industry, you won't last long.
I don't use Construct in my day job - I use it for smaller side projects. But that doesn't make "worse" than what I do use on the job (which is Unreal Engine 4 - I've also used Unity and various proprietary engines in my career). Construct is simply a different tool for a different job. It's better suited to smaller, 2D games. "Smaller" doesn't preclude the possibility of a game being very fun or very successful. Construct is much easier to learn than Unreal or Unity, and certainly FAR easier than rolling your own solutions with code, from scratch. Construct is also a helluva lot of fun to use. A person can absolutely be a serious developer and use Construct. It has some technical and workflow issues (just like every engine I've ever used) but fewer than many of them. For example, Unreal crashes for me more often than Construct does. There are no silver bullets out there, "dev level" or otherwise.
So, if you're serious about being a "real dev" yourself, the first thing I'd suggest is to stop assuming you somehow know everything despite having never done any serious work in this field. Stop assuming people who disagree with you are fools. Stop wasting your time picking fights in forums. It might make you feel good to lash out and insult people, but you're not doing yourself any favors. Spend your time mastering a tool of your choosing - pick one and stick with it even when you encounter frustrating problems (which you will, usually in no time flat). Use it every single day anyway. Ask for feedback on your work and consider it carefully, and be respectful towards the people kind enough to give it to you even when you don't like what you're hearing. Read up on your craft (Gamasutra and the GDC vault are great resources). And don't give up. This stuff is difficult, and even with some of the great engines we now have access to, it takes a long, long time to get good at it or to finish anything worth finishing.