Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: What big programming productivity gains you see happening in 5-10 yrs?

news.ycombinator.com

Post reply on HN
Print view View original

101–106 of 106 posts

Re: Ask HN: What big programming productivity gains you see happening in 5-10 yrs?

#101

Post by vladimir-y »

yodon wrote: post #28

TypeScript revolutionized the act of writing JavaScript React and JSX revolutionized the act of writing HTML GraphQL revolutionized the act of connecting front end and back end But for CSS... SASS, SCSS, LESS, and such are by comparison pretty pedestrian tweaks on vanilla CSS

> TypeScript revolutionized the act of writing JavaScript

I agree with this point.

> React and JSX revolutionized the act of writing HTML

I see nothing revolutionary in React.

> GraphQL revolutionized the act of connecting front end and back end

OData existed before GraphQL and still does.

Re: Ask HN: What big programming productivity gains you see happening in 5-10 yrs?

#102

Post by bjourne »

sgillen wrote: post #91
bjourne wrote: post #87

Earlier quoted context omitted.

Static typing is in my opinion the lazy language designer's way out. Yes, it allows for some introspection but only because the programmer has to type in all this type information! In 2019, we can do so much better. For example, development consists of typing some code, running it, typing some more, running it again and so on. The run time likely already guesses (correctly) the types of most variables for optimizatio…

As to your last point those variables could be anything, even in the simple examples you list. Size could be a tuple with the shape of some multidimensional thing, it could the the string "Large" temperature could also reasonably be a string "45C".

Yes, it "could" be anything. But in practice it rarely is anything other than one easily guessed thing. Which is why Google's V8 work so well. Variable names is one signal that can be used to enhance the accuracy of these guesses.

Re: Ask HN: What big programming productivity gains you see happening in 5-10 yrs?

#103

Post by tjalfi »

sidcool wrote: post #2

AI powered intellisense and code generation.

Intellicode[0] is an extension that adds AI-powered IntelliSense to Visual Studio. I have used it for the last couple months and it works pretty well.

[0] https://visualstudio.microsoft.com/services/intellicode/

Re: Ask HN: What big programming productivity gains you see happening in 5-10 yrs?

#104

Post by protonimitate »

zitterbewegung wrote: post #14

40 hour max work weeks enforced and 4 day work weeks. Shifts for people that need to monitor ops. Offices for everyone on staff that like to work in a quiet place and pubic areas for people who like to work in those places . Also, the minimization of time spent in meetings .

> Also, the minimization of time spent in meetings

I would argue that this should be "the minimization of unstructured/unguided/unclear meetings".

Tbh I've seen a non-trivial number of instances where engineers have wasted their own time or someone else's by not participating in organizational meetings - either by doing redundant work or having an unclear image of priorities/blockers/help needed.

Nobody want's to waste time in meetings, and most people who call meetings can't run them well. BUT having a well planned and executed meeting (30 mins tops) can save hours if not tens of hours of work time per week.

I also believe that the "just let the devs do dev work and avoid meetings" mantra is border-line meme status and (in my opinion) stems from toxic anti-social behavior, rather than efficiency. However, I also believe that meeting time per week should have an upper-bound (something like 4-6 hours, including a 15-min daily standup) to better enforce efficiency, rather than throwing 1-hour meetings all over the place and hoping they don't use all the time.

Re: Ask HN: What big programming productivity gains you see happening in 5-10 yrs?

#105

Post by quickthrower2 »

softshellack wrote: post #89
bjourne wrote: post #87

Earlier quoted context omitted.

Static typing is in my opinion the lazy language designer's way out. Yes, it allows for some introspection but only because the programmer has to type in all this type information! In 2019, we can do so much better. For example, development consists of typing some code, running it, typing some more, running it again and so on. The run time likely already guesses (correctly) the types of most variables for optimizatio…

You should google "hindley milner"

And refinement types

Re: Ask HN: What big programming productivity gains you see happening in 5-10 yrs?

#106

Post by 3minus1 »

max76 wrote: post #54

The line between programmer and dev ops will be moved with more responsibilities on the developer. Cloud services will continue to decrease the barrier of entry while entering a price war, and every team or individual will have a set budget inside the cloud. Integration with IDEs and improved online UI and CLI tools will make these tasks very easy for everyone. We can also expect better/easier/cheaper support infrast…

As long as developers are graded on their ability to crank out features most will continue to not care about reliability, alerting, etc., and there will be a need for dev ops/sre/etc.
Post reply on HN