NoNameHaveI

So, good news. After a unexpectedly long absence from employment, I am 95% certain that I will receive an offer for a contract job as a product owner. This position will largely involve supervising the development/maintenance of code written in Ada. Even though I have over a decade of experience with C/C++/Assembly, I have ZERO experience with Ada. I doubt I will be writing much Ada myself, but I believe I will need to learn Ada.

So here are my questions:

1. Reading code is usually pretty straightforward. However, all software requires domain knowledge. When starting a new role, how do you bring yourself up on domain knowledge quickly?

2. If you know Ada, what resources to learn Ada do you recommend?

3. What Ada pitfalls do you advise to look out for?

How do you think CompSci education should change in the wake of AI generated code? Keeping in mind that degree programs cannot simply keep adding credit hours, what do you think should be added? What should be subtracted? Thank you for your thoughts.

There’s a local toys for tots drive this weekend. I’m one of “those people” who like to give educational toys, especially those that foster interest in computers and electronics. I have no ties to youngsters so I’m totally out of the loop. What toys do you recommend that foster interest in electronics and computers ?

Title pretty much says it all. Doesn't have to be a software company. Just a company that develops embedded software.

Has anyone gone from Scrum to Kanban? Or vice versa? How was it? Did productivity increase? Was overhead lower, higher, or about the same? If you ended up switching back, why? Sincere thanks for sharing your reflections.