74 karma · joined August 5, 2014
There will be bugs that the AI cannot fix, especially in the short term, which will mean that code needs to be readable and understandable by a human. Without human review that will likely not be the case.
I'm also intrigued by "see if it works". How is this being evaluated? Are you writing a test suite, manually testing?
Don't get me wrong, this approach will likely work in lower risk software, but I think you'd be brave to go no human review in any non-trivial domain.
As more and more software is generated and the prompt becomes how we define software rather than code i.e. we shift up an abstraction level, how it is implemented will become less and less interesting to people. In the same way that product owners now do not care about technology, they just want a working solution that meets their requirements. Similarly I don't care how the assembly language produced by a compiler looks most of the time.
Anecdotally I find extroverts prefer the office and introverts prefer home. I find that seamless access to people can be really distracting especially when I'm doing focus work.
I think you're correct if people are given a good work environment, are in on the same days and are all in the same office this makes sense. The reality is that in many large organizations this isn't the case.
The "much less likely to get confiscated" is potentially a negative too e.g. confiscation of the profits of crime benefits society. Whether it is more positive or more negative depends upon home much you trust your government to be benevolent.
Hard work buys you more tickets in the game of life, but luck is always there to some degree. How much is luck, who knows :)
The problem is that although people moan about rubbishy software it very rarely physically hurts anybody and can be fixed in future releases. This means people are unwilling to pay the extra cost of software being more mature and 'engineered' on delivery. There's a lot of software that would be not be economically viable if it was to be held to a higher standard. If a bridge failing could be guaranteed not to hurt nobody and could be put right in a day or so but be like 1/10th of the cost structural engineers would be held to a lesser standard to.
That said, the financial cost of poor security that comes from a lower accepted quality may change what is acceptable over time for internet facing software. Even that is seemingly a long way off, look at the actual consequences for recent privacy and security breaches.
Additionally the compensation is so great that I think a lot of people would gladly take that risk given the opportunity. If in a few months you can earn a x years engineer's salary why not take the risk and then worst case is a nice holiday whilst looking for the next company to ruin.
I think your point holds better at middle management level.
SVG export would be nice too, perhaps a paid for extra :)