His thesis is that Legacy Code is code without tests. So to make it not Legacy you need to add tests then refactor safely. Then he explains the very complex patterns that can arise and how to deal with them.
This book is one of a few that changed my career.
https://www.amazon.com/Working-Effectively-Legacy-Michael-Fe...
The general process is assessment and understanding the system, refactoring and improving code without program changes, and re-achitecting key pieces to enable the testing, then getting test coverage to where it gives you the required confidence to make the change.
For example:
const userdata = [ { name: "Emma", age: 21, hobby: { reading: true, gaming: false, sport: "tennis" }, class: ["Java", "Go", "Nginx"] }, { name: "John", age: 22, hobby: { reading: true, gaming: false, sport: "football" }, class: ["JavaScript", "HTML", "CSS"] }, ]
const newdata = { knitting: true }
And then, the task is to make a utility function to find "name: John", then "hobby" and append newdata in the "hobby"object. Try to apply immutability. Try to do without the overhead of JSON string conversion.
const newobj = insertIntoObject( obj, ["name:John", "hobby:*"], newdata )
Have you tried to run the API examples or connect to IBKR using the API.
My last job was game dev but I'd rather do things I previously was doing, Python/perl/C/Matlab scientific computing.
In general I need help launching.
https://www.debugandrelease.com/how-i-gained-1k-stars-on-my-...