Posts

Showing posts with the label a day in the life of a dev

A Programmer’s Oath - Part 01

Here’s a recap of a talk by Uncle Bob on a programmer’s oath: “ Programming, as a profession, is of great importance to society. Other professions with similar importance have oaths and codes of conduct to guide the professionals in their field, like M.D’s and lawyers. This has benefitted their professions in many ways, like taking the lead in the creation of legislature.” ( Read my extended summary of Uncle Bob’s presentation ). The oath Uncle Bob proposed in the talk seems to be comprised of code centric points (five out of nine literally mention code). At many points it seems to be more of an opinionated work instruction, than oath aspiring to higher goals.  In my opinion it mainly shows how unfamiliar our profession is with oaths (and probably ethics). Still, other fields have been swearing oaths for millennia. Like any good coder, we should build on the work of others. This should allow us to skip a few millennia... more on this tomorrow.

IT; how we see each other

Image
As developers, many of us work together with colleagues from other disciplines. It's good to realize that both disciplines and developers can have a wide range of views on software development. Here are some graphic examples. source: https://www.reddit.com/r/ProgrammerHumor/comments/6brjkt/how_it_people_see_each_other/ source: https://www.pinterest.com/pin/43769427601903092/ source: https://www.pinterest.com/pin/43769427601903092/

Confusion of terms

At my present assignment I work with a seasoned senior. One of my current tickets will have some impact on the @Controller layer of the application, so I casually stated that I wanted to redo the DTO's (data transfer objects). In the application that I'm working on DTO's are used to transfer data from clients to the application. After which we got into a discussion, which ended up being more a case of miscommunication than an actual arguments. Question marks were put to my idea of adjusting the DTO's. At that moment he thought I wanted to adjust the objects responsible for representing data in our data source (db). Apparently it's also common practice to call these objects DTO's in some applications, especially if you work with a DAO (Data Access Object) pattern. To confuse the matter even further, I said that I didn't want to adjust the models too much. In the application that I was talking about models (also) represent data to be saved in the database....