Too many guys like this are what makes software dev hard. Too many yahoos who think its just about code. Code is only an implementation detail of how most dev is done today. Even today, code isn't about the code. It's about explaining your program, your process, wtf you where thing when designed this thing to the next guy/gal.

Sadly, what too much code tells us is "Design? That's what gui people do, right? I just kept typing stuff until it worked enough for non-technical person to think it was OK or we ran out of money/time."

So much this. My cohorts and I aren't spending hours talking about why we should use es2015 or typescript or whatever else. We're spending hours nearly coming to blows over how to properly implement a Flux architecture.

Too many sentences like, "you where thing when designed this thing to the next guy/gal" make reading hard. Slow down dude, wtf?

Really? Just a syntax? No inherent complexities of the real world problems, no need to invent, evolve or imagine heuristics to cover the otherwise NP-complete problems? No painful semantic mismatch between the real world and available models? No issues with arbitrarily complex performance, latency and throughput constraints?

Ah, I see that you stopped reading the article after the first paragraph, before getting to the section on "additional constraints".

> I know C, C++ , Java and Phyton. It is all about logics and the only thing that differs is the syntax.

Those are all basically the same language; if you think only syntax differs, you haven't tried enough languages that are actually different. Try a Lisp, a Smalltalk, and a Haskell and you'll learn they're semantically different, not just syntactic.

All conventional imperative languages? Open your mind. Try Prolog. Try Clojure. Try Verilog.

how big was the largest project you've ever worked on?

> Phyton

if you're trolling, that's a good one.