1,032 karma · joined January 6, 2017
Inputting code with voice is generally difficult, often due to variable names, casing, punctuation etc being hard to get right in voice-to-text. I think this might help quite a lot with that.
_However_, some of the hardest things in voice coding isn't necessarily just the input. Navigating large codebases is hard, and particularly editing existing code can be extremely difficult, probably much more difficult than just inputting new code.
I have my doubt that with the demonstration shown here, that it's able to make complex editing tasks simple, but if it does - I cannot overstate how huge of a leap forward it is.
[0]: https://www.gustavwengel.dk/state-of-voice-coding-2017/ [1]: https://www.gustavwengel.dk/state-of-voice-coding-2019/
Sure, it might be relevant if all variables were named "x", "xx", "xx", - but they're not.
If you check out these two emission factors from the UK government, one taking radiative forcing and contrails into effect and one not:
https://www.climatiq.io/explorer/emission-factor/domestic-fl...
https://www.climatiq.io/explorer/emission-factor/domestic-fl...
You'll see a noticeable difference, (almost a doubling)
Full disclaimer: Work at Climatiq, but the emission factors are not from us directly.
Currently I work at Climatiq making carbon estimation API's (we're hiring!), but previously I worked with wind turbines for several years, which are massive beasts and generate crazy amount of data, requiring large teams of software developers to efficiently manage. Perhaps solar management is similar.
Care to elaborate on this? Preferably with sources.
It's unfortunate, but some languages require you to do at least some re-architecting so it's easy to test your code.