HNHacker News
TopNewBestAskShowJobs

waterlink

314 karma · joined October 11, 2014

Alex has been programming for more than 20 years, and had a commercial experience in variety of business domains and in both product and consulting companies of different stages.
submissionscomments
waterlink··on Ask HN: As a CTO, what is your most frustrating problem with technical debt?
It seems like:

“rewrite” is in sense of “I don’t even want to understand it, going to just delete it, and implement anew”,

VS

“refactor” is in sense of “I had to spend quite a while trying to understand this code, and I think it can be improved, so that the next developer doesn’t have to spend this time.”

waterlink··on Ask HN: As a CTO, what is your most frustrating problem with technical debt?
> Repaying during good times and taking on debt in projects with high stakes and fixed deadlines.

I agree this is an amazing strategy when you can do it!

> None is willing to take on the risks associated with technical debt repayment.

What do you think they are afraid of? What risks are there? Is it possible to mitigate these risks in some way?

waterlink··on Ask HN: As a CTO, what is your most frustrating problem with technical debt?
Technical debt is very similar to financial debt.

Don’t get fooled. There is very small, and very important difference:

With financial debt, the business takes on it in hopes of delivering more value quicker that will pay for interest and principal, and have a lot of (monetary) value left after.

Financial debt, if anything, is speeding the process of delivery of value up.

On the other hand, technical debt is slowing the delivery down. And this delivery is what business hopes to speed up.

Well, maybe it makes this one iteration/release quicker, but it slows down the next one, and next one after that, and so on.

So, it seems that they are deceivingly similar, but you need to adapt the tactics and strategies.

waterlink··on Ask HN: As a CTO, what is your most frustrating problem with technical debt?
> pretending to be a victim of the system you’ve built

Nicely put! I haven’t thought of it this way.

> Are you improving your measurement system after each failure to further understand the system?

Oh my god. Yes. This is a quote that made my day.

So far, it feels like we need to:

1. Have a concept of area (and maybe sub-area) of the code-base

2. Do frequent checks how painful it is to work with a certain area. Maybe, after every feature (ticket, what have you), make developers record how they felt about the areas that they’ve touched, and why. For example, this was really painful because this class is just too coupled to this other one or something like that. Track this information.

3. Track frequency and size of changes required to different areas in the code right now (+ anticipation in the next period, whatever it is).

4. Regularly have a technical retro, where you look at the areas, and prioritize areas that:

  * give the most pain AND
  * need to be frequently changed now and in the future
5. Then go through the list of problems and choose the most horrible ones to resolve

6. Schedule time to resolve these, just like we do with features/tickets/what have you.

This is just a draft of what comes to my mind.

waterlink··on How Kotlin Calamity Devours Your Java Apps Like Cancer?
I've fixed the title to be less negative.

Probably, that is even better metaphor: "... Like Lightning?"

waterlink··on How Kotlin Calamity Devours Your Java Apps Like Cancer?
Exactly my sentiment!
waterlink··on How Kotlin Calamity Devours Your Java Apps Like Cancer?
Ok. Got you.
waterlink··on How Kotlin Calamity Devours Your Java Apps Like Cancer?
Hey, so what would be the better way to say it?
waterlink··on I Almost Left Tech Today
Why would I want to talk about these parts in the bar? Or why would I want to hear about them from someone else?

I can't talk about these parts at the bar. And I'll feel very uncomfortable and will have to ask that person in the group to stop if they were to do that.

I hold a belief that one needs to maintain professional (or at least semi-professional) conduct in the bar too. Otherwise, it is just too immature.

waterlink··on I Almost Left Tech Today
From a straight-man point of view (me) it is also not acceptable.
waterlink··on I Almost Left Tech Today
The video "We don't give a fuck" was shared as a response to the author sharing a link to "an article on why so many women leave engineering".
waterlink··on Sometimes Not Working Is Work, Too
I agree. "Click bait" is probably best used for headlines that are catchy, but don't really represent the content of the article (so they're basically lies, like fishing baits, but for clicks).

As long as the title is catchy AND represents what you get in the article, then it is a good title and I see no reason to call it "bait" because it is not a "bait", it is real (knowledge) food.

waterlink··on The Acceleration of Addictiveness (2010)
I'm using the technique called "Productive Meditation" described in the "Deep Work" book.

In its core, you choose to walk outside for one Pomodoro, while using focused meditation, where the focus is not on the breath (or any other part of the body), but rather on a specific question that you need to find an answer for.

Also, I use the same technique when I'm commuting by the public transport from work to home and home to work.

For the technique to work, it is important to be proficient with focused meditation. So one needs to train first to be able to consistently focus on something simpler than a question (breath, or feet, or your surroundings, or food you eat).

waterlink··on The Acceleration of Addictiveness (2010)
That is an amazing approach. Thank you! I'll try the plugin.
waterlink··on The Acceleration of Addictiveness (2010)
That reminds me of an amazing book "Thinking in Systems: A Primer." It is probably on my list of must-read books for software developers and other roles around them.
waterlink··on The Acceleration of Addictiveness (2010)
I see one alternative: design things around "value."

On the other hand, as users are already trained to choose products based on "engagement," it would be important to have a certain level of "engagement" with these products no matter how "valuable" they are. Otherwise, users just won't notice the product and its "value."

waterlink··on Ask HN: What books had the greatest effect on how you structure your code?
> * Bob Martin - Working Effectively with Legacy Code

Author is Michael C. Feathers

waterlink··on Writing code with multiple overlapping side effects with a straight face
Depends on what kind of pride we are talking about. I know developers who hold a lot of pride in how readable and understandable their code is. It is a pleasure to work with them and said code.
waterlink··on Build Your Testing Framework. Part 5: all tests should run and exit code
Did you notice, that out testing framework quits on the first failure? It probably should run all tests, collect all failures and present them nicely. This is what we are going to accomplish today.

Feedback and shares are super welcome. Also, tell me if you would like to see a screencast of me implementing that :) (even in different language)

waterlink··on Getting Stuck While Doing TDD, Part 3: Triangulation to the Rescue
I would never write such an if statement. In the article it was an example of the Specific/Generic Rule violation.

Implementation evolution is as following (backed up by respective test):

Sum(a,b): 4

Sum(a,b): a+2

Sum(a,b): a+b

1 example test for the requirement and 2 iteration of triangulation with transformation priority premise.

I hope that makes sense. Sorry for not being clear enough in the article about the example being a violation of the rule, that you shouldn't do.

waterlink··on Getting Stuck While Doing TDD, Part 3: Triangulation to the Rescue
And thanks for the warm words! :)
waterlink··on Getting Stuck While Doing TDD, Part 3: Triangulation to the Rescue
Additionally I would like to stress that RED step is ultimately important - we have to see the test fail in an expected manner, otherwise we would never know that test is actually working as we expect it to. (for example it does not have any assertions, or they do not execute for some reason).
waterlink··on Getting Stuck While Doing TDD, Part 3: Triangulation to the Rescue
While this is true, using this technique all the time makes me damn effective with it and I very rarely get stuck (only when I actually violate one of the rules).

And I like the BabySteps feel that it produces, it is so nice to evolve your code bit by bit one test at a time and without harming Semantic Stability (you can read about it here: http://blog.cleancoder.com/uncle-bob/2016/06/10/MutationTest... )

waterlink··on Getting Stuck While Doing TDD, Part 3: Triangulation to the Rescue
To reassure: I do use this technique on a daily basis. And I have teached it to my team and we are happily applying it. It works well on big complex projects and makes sure you didn't miss any test case, so that Semantic Stability of the test suite is up high.
waterlink··on Getting Stuck While Doing TDD, Part 3: Triangulation to the Rescue
If the production code does something by happenstance I will consider it a bug and fix it (unless in Legacy Code, where a bug could mean hidden super-valuable-for-customers feature). I.e.: I will make sure that this test fail and all other tests pass.

Production code doing something, that is not defined by tests is generally not a good idea, because this is clearly an untested functionality. And it has to be eradicated if nobody needs it (business and customers) or it should be covered with a test, and I want to see this test fail (by applying Mutational Testing).

waterlink··on Getting Stuck While Doing TDD, Part 3: Triangulation to the Rescue
I definitely am using these techniques on real projects with huge complexities to them. Quite successfully. Without bugs. Continuously Integrating and Continuously Deploying to Production.

I'm pretty sure, that the case study of such project will take up the whole book, not just 3 blog posts ;)

waterlink··on Getting Stuck While Doing TDD, Part 3: Triangulation to the Rescue
Thank you for your feedback. I'm encouraging you to read the whole article, better, whole series.

Because sum method was used to quickly explain Specific/Generic rule on the simplest example. Then it follows through with real-ish (a bit modified) business case, that has gotten me stuck in the past.

I know that readers on the internet have limited attention span, so I shouldn't have put a sum method example at the beginning, rather I should have started with the main case study and made a detour before applying this rule to the sum example.

Thanks for the feedback again, next time I will try to not make this mistake.

waterlink··on Getting Stuck While Doing TDD, Part 3: Triangulation to the Rescue
Yes, they do, and pretty good.

Because it is actually faster and less error-prone once you get familiar with Evolutionary Design.

A good read from M. Fowler: http://martinfowler.com/articles/designDead.html - this talks, why a lot of Extreme Programming practices come into the synergy to make Evolutional Design effective (and not only). Drop enough of these practices, indeed, it will stop being effective.

waterlink··on Getting Stuck While Doing TDD, Part 3: Triangulation to the Rescue
Interestingly, enough, my OO code, when I refactor it well, mostly consists of tiny little (one-public-methods) classes, 99% of them are stateless, and, usually, 3-5 are composed to accomplish any sort of task at any level of the detail. I started writing OO code this way only after learning Haskell and having production experience with Clojure. Basically, immutable objects are very similar to pure functions and easier to reason about.

Even in pure functional environments I do use TDD, because it gives me enough confidence to know, that I know what I am doing. Maybe it is just a mindset, or my brain is wired this way. For any change to the production code I require a proof, that system needs to be changed in a form of failing test.

waterlink··on Getting Stuck While Doing TDD, Part 3: Triangulation to the Rescue
This is a pretty interesting process you have there. I usually use throw-away Prototypes/Spikes, when I do not know how to write my first test or I feel uncomfortable test-driving the problem. Once I reach enough confidence, I remove spike's code and start test-driving it.

I let the design of the system emerge on its own, while I'm listening to how hard it is to write tests and steering the wheel using Red-Green-Refactor (2nd cycle of TDD) and while I'm following Specific/Generic rule (applying Triangulation together with Transformation Priority Premise) (this is the 3rd cycle of TDD).

Red-Green-Refactor on its own indeed is very well known for leading quickly to the local maximum of the solution and its design. 3rd Cycle of TDD breaks out of the local maximum of the solution to the problem. 4th cycle of TDD breaks out of the design maximum (4th cycle of TDD - Hourly, we step back and look at the overall design and architecture of the system, taking a careful look at the architectural boundaries and seeing if we are about to cross any of them with our efforts, we proceed with informed decisions steering to the right design we want for the next hour).

Here is the Robert C. Martin's blog post on the cycles of TDD: http://blog.cleancoder.com/uncle-bob/2014/12/17/TheCyclesOfT...

← PreviousPage 3 of 4Next →