devnull3

We humans have to be exact about the word exact. This is my point really. Same with AI.

> will do exactly what they are told

If you have to encode the exact if-else conditions, then how it is different than regular software development.

We want AI to be as intelligent as Humans. This is the holy grail. But humans are also whimsical, irrational and slave to emotions. So we are attempting to design a system which is replicate this nature as well.

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.

> a visually appealing GUI

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.

If there is a such a breakthrough then the hackers or even spy agencies will not reveal it. They will instead silently make use of it. It will be essentially a backdoor for them.

This demonstrates why it can be hard to be intuitive with large numbers and exponential in nature.

C-interop while certainly more involved in Rust compared to Zig, it is generally a one-off effort (for most projects). wards it's generally an incremental effort to map additional C code. I am not sure I would make this an important factor but to each his own.

> old Italian city

Try traffic in India [1][2] If it were a game, then India will be the last boss fight in ultra-hard mode.

[1] https://www.youtube.com/watch?v=KnPiP9PkLAs

[2] https://youtu.be/WC2FUEmKEu8?t=412

Any idea how many years away Zig is from v1.0?

As someone sold on Rust, I really want Zig to succeed.

That is the reason AWS & Azure are much more successful when it comes to enterprise customers. This is where the real money is.

Also AI (as promised) will deliver a customized solution to an extent that for a human to even solve the problems in it will need a lot of context. This in itself makes it dependent on humans. Also you have to factor in knowledge redundancy, non-availability of your personnel. So you will always have to account for more people than AI promises.

Atheism is an accepted school of thought in Hinduism [1]

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...

I don't think so AI will replace SW jobs. It will definitely change the way engineers work.

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)

"A Better Way of Reading" -> in what way? All I see is teleprompter like text on screen when I click one of the links.

I don't think so AI will replace SW jobs. It will definitely change the way engineers work.

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)

See the issue with AI or (AGI) is that it is trying to model or imitate a system which is irrational, whimsical and inconsistent i.e. human. So the o/p of an AI system will be subjected to bias by humans especially when there is no universal right & wrong.

OMG! I had a flashback. Do any of you remember HP Quality Center?. Its early versions had entire UI in activeX and I remember a bunch of progress bars installing DLLs.

I could not understand and hence I asked the question. The thing I understood was that this broke some peoples flow.

I am a Vim guy. Can someone explain what exactly is broken?

You can start with Go's standard library: https://github.com/golang/go/tree/master/src

I know, though lot of major religions do not think so.

> so it isn't new

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.

These things have suddenly going mainstream and lot of ppl (including me) are having existential question: what does it mean to be a human?

PS: It will be fun to do in "damn nature u r scary" voice & style [1]

[1] https://www.youtube.com/watch?v=-vlFHlSm1r4

Reminds me of a dialogue from the movie: "The Pursuit of Happyness"

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!

I had a look at https://racket-lang.org. Where we can download this build? [1]

[1] Assuming that the merge has happened since the announcement was on Oct 16

Yeah, I never understood why the lane markings are not above the head and in advance instead of on the road.

> drivers unfamiliar with the layout People familiar with the layout drive even when the markings are completely faded. It causes lot of anxiety if you are not familiar. It happened to me once where I was in a wrong lane. I continued on it as it was the most safest thing to do but the next exit was onto a motorway :). I was so angry with myself.

Driving schools in UK teach that changing lanes on a roundabout is unsafe. Infact, in a driving test doing so will result into a failure because most people will not follow safety checks and signalling.

If you are in a wrong lane, the safest thing is to continue on it, exit the roundabout and comeback again or go around the roundabout.

There is a sign board which tells whether to take the middle road or left [1]

This is the round-about layout [2]

None of the above tell the precise lane to take. Only when you enter the roundabout you will know. See.[3]. Imagine cars waiting on these markings. This is what frustrates me the most.

[1] https://www.google.com/maps/@51.5066257,-0.5789164,3a,75y,32...

[2] https://www.google.com/maps/@51.506316,-0.5784722,3a,37.5y,2...

[3] https://www.google.com/maps/@51.5076664,-0.5804344,3a,75y,29...

Simple roundabouts are definitely good but in UK I have found spiral roundabouts error prone if you have not driven on it before Example: [1]

When visiting for the first time on a specific spiral roundabout:

1. Lane markings are faded

2. You do not know the specific lane unless you come very close to it and have to make a quick decision

3. Often due to queued traffic you cannot even see the lane marking until its too late.

Because of this I have seen people change lanes on a roundabout because they made a mistake and its dangerous.

[1] https://www.google.com/maps/place/Sainsbury's/@51.5080462,-0...

This will impact the driving tests as well. A typical practical driving test lasts for 35-40 min. But with 20mph it will cover less distance. Interesting to see how the DVSA (the body which conducts these tests) handle this.

Increasing test duration means the backlog (which is already huge) will increase. Keeping same will mean less road features will be tested.