r/programming • • Jul 30 '18

Announcing TypeScript 3.0

https://blogs.msdn.microsoft.com/typescript/2018/07/30/announcing-typescript-3-0/
1.5k Upvotes

357 comments sorted by

View all comments

Show parent comments

31

u/[deleted] Jul 30 '18

No, that's Agile done poorly.

An implementation change should include documentation updates, and the code review should catch that. Ideally, there will be an automated test (included in the change request) that proves that the implementation matches the spec.

In an agile process, making these changes as part of the process is essential.

19

u/13steinj Jul 30 '18

An implementation change should include documentation updates, and the code review should catch that. Ideally, there will be an automated test (included in the change request) that proves that the implementation matches the spec.

In an agile process, making these changes as part of the process is essential.

What you call "essential", managers call "useless, time wasting bullshit that I don't pay you for. Just do agile cause its the new buzzword of the month".

10

u/[deleted] Jul 30 '18

I get that at work too, which is why devs need to push back. Unit tests and documentation often save time in the long run.

4

u/13steinj Jul 30 '18

Except many won't risk getting reprimanded/fired.

I'm not saying this is a good thing. Just that it unfortunately happens quite a lot.

11

u/[deleted] Jul 31 '18

I guess you'd have to be senior to throw your weight around. That's what I do, and I'm the most senior on my team, so I tend to get what I want :)

2

u/13steinj Jul 31 '18

Lucky you?

11

u/[deleted] Jul 31 '18

I guess?

I think it's up to the more senior devs to make sure the correct dev process is being followed because it helps reduce work later. Managers often don't understand those types of things, so you need to earn their trust first.

-8

u/ProFalseIdol Jul 31 '18

Maybe put a dollar sign on the cost of not doing it. For this case, it's actually costly. A miscommunication in a language spec can incur big rework. Not just on Micro$oft side. But on client side. Regular users or tool developers. I mean... this is a major release of the language..

Say 30 Million dollars (my wild guess), provide a breakdown of it in bullet points.

Maybe also argue that a language should have a spec, not having it would reflect badly on Micro$0ft's image; and the marketing damage (then bring in the marketing lead to explain).

19

u/MAINFRAME_USER Jul 31 '18

> Micro$0ft's

WTF is this? Are you 14?

4

u/13steinj Jul 31 '18

Some people on reddit are gnu fanboys that hate MS no matter what they do.

1

u/ProFalseIdol Aug 01 '18

Lol, why are you so triggered.

-4

u/scaleable Jul 30 '18 edited Jul 31 '18

Actually they have mostly them all:

  • The code reviews

  • the design meetings

  • documentation updates

  • An extensive testing base

Yeah, the docs are actually updated, only the specification is not. (specification = cascaded dev)

Maybe if they hired 15 more engineers and made their team an ENTERPRISEY team they could keep up on maitaining those specs balmey.

5

u/[deleted] Jul 31 '18

Or just slow development a little to make sure everything is correct before moving on.