Timeline for answer to How to test a programmer's ability to handle a large code base? by Steve
Current License: CC BY-SA 4.0
Post Revisions
2 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 4, 2024 at 17:12 | comment | added | shortQuestion | I worked on something like that for 3 years it took about 6 months to really be able to get an raw overview the problem is as a guy under 50 you should jump better somewhen, even if you get ok with the codebase and the company. Cause most of the experience will just be applicable on that codebase. Its good to feel it somewhen but not good to stick to long. I have to say after I jump I felt reall, how much time I used only for analyzing and how less for actualy write new features or fixes. Its most of the time really just understanding, get business requirements and than tweak small things. | |
| Dec 4, 2024 at 11:55 | history | answered | Steve | CC BY-SA 4.0 |