Skip to content

Instantly share code, notes, and snippets.

@johana-star
Created May 11, 2015 18:28
Show Gist options
  • Save johana-star/6cff6ef204b6e08dd08c to your computer and use it in GitHub Desktop.
Save johana-star/6cff6ef204b6e08dd08c to your computer and use it in GitHub Desktop.
Status Report, Mon, May 11th or whatevs

Mondays always start off a but weird, I have no standup, instead there is an afternoon planning meeting. It's a time to do a bit of code review, ramp up, wake up, refocus.

This weekend I drank with friends, worked on building my static site generator some, and celebrated mother's day with Wryly's mom. It went by too quickly.


Friday afternoon after reviewing open and pressing issues and finding them all to be some form of inactionable I began extracting out a piece of duplicated functionality from the model level into a concern, which was a bit of fun and rather relieving to me. I'm realizing that a lot of the challenges I'm facing on a project of this scale are clutter and dischord.

The codebase itself is never as direct as I want it to be, nothing is as organized as it could be, and this is the clutter. It's an after effect of the dischord. I've been advocating for styleguide adoption, as we have a five-year Rails app, and nothing was ever done consistently for long. The code takes a huge amount of time to load into peoples heads because we don't even pretend to write the code in the same voice.

It's frustrating working with people. Certain people. Conway's law states, "organizations which design systems ... are constrained to produce designs which are copies of the communication structures of these organizations." Couple that with treating stupidity and routing around it and we start to create deformed structures to avoid talking to that stubborn guy, or simply to appease them.

I've been pushing for styleguide adoption, stubbornly hoping that we can start to improve at the very least how our code is written… And just as stubbornly people are resisting integrating style into their work, with a chorus of jokes "We have a styleguide?" every time I mention improvements to it

The argument against seems to be that the only reasons to prefer a style are removing syntactic ambiguity or improving performance. Preferring one syntax over another for consistency and readability, is, well, unreasonable. I just wish that it were easier for my org to code in one voice, and to be able to refer to some standard when trying to improve.

I hope that the folks aren't routing around me for this stubbornness.

@krainboltgreene
Copy link

Unasked opinion: Make it very fucking clear that they're treating something you care about as a joke and that it's directly affecting your morale and desire to work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment