Its perfectly understandable IMO for people to get upset when someone says their entire profession “is over”.
-
-
Replying to @hal9zillion @yoshuawuyts
And when author of said piece apparently wrote their 1st line of code barely a year ago it doesn’t make it much more palatable.
2 replies 0 retweets 0 likes -
Replying to @hal9zillion
oh, I wrote my first line less than three years ago, and think this person is making a lot of sense - we DO repeat ourselves
2 replies 0 retweets 1 like -
Replying to @yoshuawuyts
the general idea that we, individually & as an industry, repeat ourselves a lot is definitely something i agree with.
1 reply 0 retweets 0 likes -
Replying to @hal9zillion @yoshuawuyts
But then following “Coding is dead” & then marvelling how GraphQL is much better than REST is an obvious logical fail given:
1 reply 0 retweets 0 likes -
Replying to @hal9zillion @yoshuawuyts
a) it was first announced last year b) this would mean lots of devs will be changing from REST 2 GQL i.e. doing the same thing
2 replies 0 retweets 0 likes -
Replying to @hal9zillion
I wouldn't get stuck on that one detail; the idea is right tho - better tooling > less errors > devs working on actual problems
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
Totally agree with u on this. But even here there were mixed messages - improved code tooling is bad:pic.twitter.com/SbY8LNxoN1
1 reply 0 retweets 0 likes -
Replying to @hal9zillion
I read it as: "coding takes a lot of time, and we spend it on xyz; let's aim to spend less time coding"
2 replies 0 retweets 1 like -
Replying to @yoshuawuyts
Thats fair Seems like people r taking different messages from the article itself At any rate i think we agree on the basics :-)
1 reply 0 retweets 1 like
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.