Depends on how the AI is used. If used intelligently, for short, readable code snippets, reviewing and understand is easy.
If used naively, where AI spits out 1000s of lines of code, that is far from perfect, written in a style that might not be what you are used to, it can take longer to parse, than if your colleague of 2 years wrote it.
This is the way. Basically, what determines when to use AI or not is what you enjoy about the creative process. Do you only care about the result, use AI, and then spend hours (or days) fixing errors, tweaking, rewriting, using other AI:s to validate and improve the first AI etc. You get the result, and your activity consist of arguing with AI:s.
If you enjoy the craft and the creative process of actually coming up with new thoughts, instead of relying on the probabilistic combinations of thoughts of others, then you can just as well do it yourself and have full control of the process.
I use AI for low value work with dead lines, where the customers don't really care about the result either. For the golden services and customer engagements were I can tell the customer cares deeply, I use little to no AI, and then get a deep sense of fulfillment due to a job well done.
"You might ask, why can’t you work less? It’s not as easy as that. If I decide to work less, who is going to cover the hospital? If the hospital aren’t employing other doctors, we can’t allow patients to go uncovered. I accept the fact that I have a duty of care to be on call. The intensity and personal damage of these on call periods are often forgotten."
This is a very short sighted and immature way of looking at responsibility and your "calling".
Yes, if you are not there, things will not happen. That is for the long term best. By thinking that it is your duty to be there, despite the state you are in, you are actually contributing to entrenching the situation you are in. That is error nr 1. Error nr 2 is that you are not fit for fight and are risking life and limb of others.
The only sane and long term way to deal with this is to opt out, and let the system crash, so that politicians (or hospital owners in case of private hostpitals) will add more resources. If you refuse this, you are sacrificing yourself for nothing.
Doing this take courage, resolve and maturity.
"Not only that, we are losing control of health care in general. Everyday, there’s a new form, a new guideline, a new protocol, a new health software, a new policy all dictating, restricting and modifying clinician activities. Some of these policies are written by people who do not see patients. There’s a whole paid industry dedicated to restructuring what doctors and nurses do to reduce costs and increase output."
This is just the corporate world. At least in IT. In terms of stupid web based training, it is best handled by dividing up the training and compiling a list of answers. Then the answers are distributed among the entire team. You only need to do one training, and the rest you click straight through to the questions. It used to save me and my team hours and hours every month.
This assumes you are mature and capable enough to identify that the courses are clearly nonsense and only there to please managers and button pushers. This was the case for 99.9% of all web based training I've ever had that I did not choose myself to do.
How can it be unfair? People are free to do what they want with their money. I think it would be unfair if you would be the judge of which projects I am allowed to donat to. That, if anything, is unfair.
If you want equal fame, invent your own programming language that will be used widely, and surely, you will get interest and people investing in your ideas. Just sitting and complaining however, is exactly the behaviour which would signal to me that I will never invest in your projects.
Pinephone is close to useless. Fairphone 5 I think is as good as it gets if you want to avoid android. It is annoying though that fairphone 6 is not working with linux.
We don't, and sadly accept the cost of our principles. What I generally do, is to put on the blinken lights, and try to hurry up. Up to about 20 minutes or so, it generally works alright.
If used naively, where AI spits out 1000s of lines of code, that is far from perfect, written in a style that might not be what you are used to, it can take longer to parse, than if your colleague of 2 years wrote it.
reply