Will talk about Linux, plants, space, retro games, and anything else I find interesting.

  • 92 Posts
  • 387 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle






  • Sometimes ill do TDD, sometimes ill do the opposite. When I know what something looks like or should function. Im not sure what the technical term of itis, but ive heard someone call it Scaffold testing. Its making sure all the parts work as expected (Unit and integration/e2e) for your future sanity.

    TDD lets you experiment and makes multiple potential solutions to a general problem. IE starting with the end first. Scaffolding lets you create a scaffold around what you already built so its more rigid. Both have their place.


  • Heh yeah. I feel that. Close to 20 now and Im starting to feel the churn. But its still a good feeling to give direction and see people grow. I used to be a team lead in addition to a senior dev…now im just a dev (being an individual contributor is fun again) and the 40 tabs bit resonates with me. I find that AI is good a surface level assignments like build basic CRUD/models…but it Fd up so hard sometimes its hard to come back from. Definition of spaghetti sometimes haha. I just go back to the old stuff that I know works.


  • Im not sure if this helps anyone but I used to tell my jr devs the same thing:

    1. You got the job.
    2. You are now a developer.

    The article somewhat goes over this but: Learning to code is a life long thing. You just keep getting better each day with practice. Im not sure about the phases though. Definitely the “job ready” portion of the article. It seems short sighted to say you need all those things and going through each of the “phases” in order to be successful. Just solve a problem. With software. Congrats!