Timeline for Is low code quality and lack of testing the norm in B2B software development?
Current License: CC BY-SA 4.0
7 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
S Dec 19, 2023 at 9:11 | history | suggested | Isaiah | CC BY-SA 4.0 |
Corrected capitalization particularly of the word "I". Also fixed a few grammar errors that were making the answer harder to read.
|
Dec 19, 2023 at 3:01 | review | Suggested edits | |||
S Dec 19, 2023 at 9:11 | |||||
Dec 18, 2023 at 19:44 | comment | added | Ewan | a question for #theworkplace, my advice would be to try and implement these things on small projects you can do yourself and remember to ask about that kind of stuff when you interview at other places. "what best practices do you use? Do you do X architecture? what version of Y are you on?" etc You shouldn't hang around too long as without that kind of experience you will be less employable | |
Dec 18, 2023 at 19:15 | comment | added | Jeremaia Scott | Thank you for your comprehensive answer Ewan! It's good feel validation regarding my opinion on code quality, and differences in B2B/B2C. It leaves me one question for the short term. Do I just sit on my hands and wait until a problem appears before I preach about code quality? We've had new hires since I've started, and after conversations with them, it appears that their velocity is hindered by the quality of the codebase. Does this constitute enough of a problem, or does it need to be more apparent/larger? Thanks again! | |
Dec 18, 2023 at 10:17 | history | edited | Ewan | CC BY-SA 4.0 |
added 637 characters in body
|
Dec 18, 2023 at 10:12 | history | edited | Ewan | CC BY-SA 4.0 |
added 637 characters in body
|
Dec 18, 2023 at 10:06 | history | answered | Ewan | CC BY-SA 4.0 |