The Don’t Clean Code StandUp Comedy episode, make me think about some things. Therefor I just want to save them somewhere. Isn’t a good excuse to write a new blog post? :)
I really agree with this guys interpretation. Big blocks of code are easier to maintain because you don’t lose the Context. and better than that, you don’t need to open 10 other files to understand what many blocks of code do. If sometimes is difficult to detect bugs that are in one single code block, I can imagine how Chaotic can be, if developers need to pay attention to 10 files or more at the same time, to understand the logic behind (links between) all mini-services(blocks of code seperated on different files). I mean, I made that “chaotic approach” when I was defining the documentation(in a global and superficial perspective) of the application we going to build, but then I try to create a single page document, where I define the Flow of user application usage, adding the rules and limits that users will have as their experience. When I made this last document I figure out that maybe I save some Hours of interpretation and organization of the idea, to the developers. 1 Page versus (almost 50) :D
Then I remember that in some comments on Jira, I mention the “name Convention” issue. In my interpretation is easier to identify a particupar function or data, while that is only a “easy to remember” technique to remember the function or some object propriety. Therefor, my comments were not very “happy”, since developers build a Object-Tree of “userProfile”, and all interrnal object Keys, don’t need the “user” name convention to define their own propriety (like for example: userEmail), because “Email” is already a propriety of User.
I feel thankful that developers list all the tasks (or at least the main ones) with a proper Title and a useful and informative description about each Task. But I would like to remember the Team, that Jira “should be useful for developers”, which means, the superficial description is what I expect to read and everything else, that should be described ( the technical notes ) should be there too, while those only serve Developers, not me.
Anyway, since developers don’t connect Jira with some Git platform, we have this kind of “disconnected” sensation of developers activity. Jira can be useful for developers, like git issues are, but they chose to use Jira, instead fo some Git web platform and in that specific case, I continue with that “black box” sensation, where I don’t really know what they are doing.. Is like asking them to make an extra work, because in one point they don’t connect to Git and therefor they don’t push new code to anywhere when coding and using Jira was just a “Estetic” choice, since Jira “Looks Good” if you compare it to a Git Platform… In this particular detail, there is no difference between using any Git Web Platform or using Jira, which they don't use none of them. lol -> The "Closed Source Problem of Companies". You know, since I didn't find someone to help me to build this application, and my coding skills are this ones you can see, HTML and CSS only, to build this application inspired by the Music track Social Tool Kit and The Project Game that is at the same time The Challenge I was willing to pay. So here am, experiencing my days...
It was “funny” that my criticism about their organization method, was pointing about the issue of declaring a Big Task (with several others inside) as “Done”, while all sub-tasks were marked as “To Do”. They could solve the problem by changing each sub-task from “To Do” to the correct state, but what they did, was to create many new single tasks with a minimum of sub-tasks or none at all. In the perspective of “having the list of Tasks needed”, is great, while to monitor dependicies is really bad, because with this last approach, there is no structure that show code dependicies or context links.. Is like designing the product with many modules that are not connected to each others, while they are at the same Time, but since NoSQL is the choice, that chaotic organization will probably work in any way. Adding sub-tasks is something that Git platform don’t have, or maybe they have but I never use them and therefor I don’t know, while if Jira have in a way that I could make them easly, the developers deny to make use of it, and that visual aspect where you see a Tree-Dependecy, is Gone. I see it very useful. (not them)
I already pass throught the Big test of not Becoming Mad with them... I fail few times.. but this days I just laught and make fun of it.