devnull3
If any one API of a struct/enum has '&mut self' then its instance cannot be shared across threads without using a mutex (which brings its own friend along i.e Arc). This led me to structure the code in my mind much in advance to prevent borrow checker issues.
Another use of this is while embedding an object in a struct. When I realized that '&mut self' infects everything up the call chain it was a big learning moment. That is the embedding struct also needs a mutable borrow as well.
1. Only one solution (or path in this case) should exist
2. No loops (meaning the valid solution does not cross it-self)
3. The length of false path from correct path should not be more than 4
I was rejected with lean-no-hire (or weak-no-hire .. I don't remember the exact term but basically not a strong reject).
If you have to encode the exact if-else conditions, then how it is different than regular software development.
So we want a system which we want it to behave in just about "perfect" manner (i.e. intelligent but not going astray). What passes as "perfect" is subjective and there will be different definitions of it.
Now to control this you want a capability to precisely define the allowed and dis-allowed behaviour. At this point we are essentially circling back to the software systems before the AI.
I think it requires a combination of things: a good taste, a sense of visual design and programming. The first two is more of art form.
Most of the developers on these projects are really good at programming but its rare to get a good combination mentioned above AND willing to work on open source over multiple years consistently.
Update: Also someone in the decision making hierarchy needs to have a keen sense of design. Example: Steve Jobs learnt calligraphy and even though he did not actually designed it he would certainly veto and pass feedback to the developers.
Try traffic in India [1][2] If it were a game, then India will be the last boss fight in ultra-hard mode.
As someone sold on Rust, I really want Zig to succeed.
Indian philosophy is diverse and vast. See the comparison of these philosophies [2]
[1] https://en.wikipedia.org/wiki/Charvaka
[2] https://en.wikipedia.org/wiki/Indian_philosophy#Comparison_o...
Software development involves:
1. Understanding the requirement
2. Solving the problem with given constraints (and thereby innovate)
3. Talking to stakeholders
4. Code (& unit tests)
5. Review #4
6. Troubleshoot in testing
7. Troubleshoot in prod, both perf & subtle issues (this is hard)
8. Take the input from #6 & #7 and use it as a feedback back to #2
9. Answering questions from users/support which involve suggesting workarounds and not just factual answers. Suggesting a workaround itself is a mini-problem solving which is an intersection of domain knowledge, knowing code at hand, understanding customer's situation, etc.
Coding is hardly taxing and time consuming when there is clarity what needs to be done and how it needs to be done.
Point #4 itself has sub-dimensions like performance, maintainability, test-ability, security, etc and it involves lot of subjective calls. Sometimes you have to deal with undocumented behavior of an API which is a tribal knowledge.
To troubleshoot in prod (esp subtle issues) require deep knowledge of the code at hand. This itself is a challenge when you are dealing with generated code and something you have not written yourself. Think about a human dealing with an existing large code-base when joining a team.
I understand all of the above is a spectrum and there are jobs in SWE which do not require so much rigor.
Key ability for breakthrough and the rest will fall in place: Code generated by AI is consistently put to production without human intervention for a sufficiently complex problem considering all good attributes (like backward compatibility, performance, etc)
Software development involves:
1. Understanding the requirement
2. Solving the problem with given constraints (and thereby innovate)
3. Talking to stakeholders
4. Code (& unit tests)
5. Review #4
6. Troubleshoot in testing
7. Troubleshoot in prod, both perf & subtle issues (this is hard)
8. Take the input from #6 & #7 and use it as a feedback back to #2
9. Answering questions from users/support which involve suggesting workarounds and not just factual answers. Suggesting a workaround itself is a mini-problem solving which is an intersection of domain knowledge, knowing code at hand, understanding customer's situation, etc.
Coding is hardly taxing and time consuming when there is clarity what needs to be done and how it needs to be done.
Point #4 itself has sub-dimensions like performance, maintainability, test-ability, security, etc and it involves lot of subjective calls. Sometimes you have to deal with undocumented behavior of an API which is a tribal knowledge.
To troubleshoot in prod (esp subtle issues) require deep knowledge of the code at hand. This itself is a challenge when you are dealing with generated code and something you have not written yourself. Think about a human dealing with an existing large code-base when joining a team.
I understand all of the above is a spectrum and there are jobs in SWE which do not require so much rigor.
Key ability for breakthrough and the rest will fall in place: Code generated by AI is consistently put to production without human intervention for a sufficiently complex problem considering all good attributes (like backward compatibility, performance, etc)
I agree but so far mainly philosophers & intellectuals used to ponder. With advancement in tech many believed that intellectual or creative work is safe. I think now this is a jolt to a lot of white-collar folks who are looped in with the recent advancements in AI.
Its not that intellectual or creative work will vanish but a lot of the current work will be commoditized.
PS: It will be fun to do in "damn nature u r scary" voice & style [1]
Interviewer: What would you say if man walked in here with no shirt, and I hired him? What would you say?
Will Smith: He must have had on some really nice pants.
Go has some really nice pants i.e Simplicity with good enough performance, backed by big corp.
Simplicity scales!
[1] Assuming that the merge has happened since the announcement was on Oct 16