221 karma · joined July 11, 2017
Depends on the definition of 'software' also. Strictly speaking, every npm package is someone else's code running on your machine. Often with quite wide ranging permissions.
If you need approval from IT to add a package or increment a version then your development process is going to be slow for sure.
Web Components predate React as an idea, don't they? Admittedly it too hella long to get them properly standardised.
How would you know if the poor commercial performance was due to tech debt or not though? It's the intangibility of tech debt that makes it so insidious.
This is mentioned as a drawback at towards the end of the blogpost, isn't it? It does seem it would make deployments rather awkward.
It makes it really hard to offer good autocompletions too.
I think you skipped a few years there! AJAX, Mootools, prototype, JQuery, etc.
I have no idea what an Okta support engineer can or can't do but I know that a regular account administrator can set an arbitrary password for a given user via the Okta UI.
Because Amazon force their staff to keep working?
I'm looking forward to this landing too. In the meantime, though, checking out the repository that contains the Actions and referencing a local path works fine so this hasn't really been a blocker for us.
Edit: per sibling comment, it seems that this feature became available in the last few days. Nice!
100% agree with 37 & 38:
> 37. AsciiDoc rocks!
> 38. PlantUML rocks!
It's like the article says:
> At some point in time, this idea has been so widely misunderstood that the wrong definition of DevOps became the right one.
See also: 'agile'.
Why not, out of interest?
It's not even just the police - the goons on the doors of JB Hi-Fi will demand to root through your bags on your way out of the shop. Nobody even seems to question it.
People say that every time though and they always do.
[1] https://www.theguardian.com/world/2001/jun/06/uselections200...