Skip to content

Today's Card

Software engineering and other thoughts.

Monthly Archives: May 2020

A variable’s name should correlate to the size of its scope.

The larger the scope, the harder it is to fully understand.

Posted byfooyayMay 29, 2020May 10, 2020Posted inUncategorizedTags:clean codeLeave a comment on A variable’s name should correlate to the size of its scope.

Kanban in three easy steps.

There’s not a lot to Kanban, which is one reason it is desirable.

Posted byfooyayMay 28, 2020May 10, 2020Posted inUncategorizedTags:kanbanLeave a comment on Kanban in three easy steps.

Keep the build clean.

Don’t accept failed tests.

Posted byfooyayMay 27, 2020May 10, 2020Posted inUncategorizedTags:build, testingLeave a comment on Keep the build clean.

Don’t create God classes.

These monsters try to do too much.

Posted byfooyayMay 26, 2020May 10, 2020Posted inUncategorizedTags:god class, simplicity, single responsibility principleLeave a comment on Don’t create God classes.

Avoid paralysis by analysis.

It can halt your progress.

Posted byfooyayMay 22, 2020May 10, 2020Posted inUncategorizedTags:analysisLeave a comment on Avoid paralysis by analysis.

Beware bikeshedding.

Some decisions don’t get the consideration they deserve.

Posted byfooyayMay 21, 2020May 10, 2020Posted inUncategorizedTags:bikesheddingLeave a comment on Beware bikeshedding.

Avoid premature optimization.

There’s a time and a place for this and it’s not at the beginning.

Posted byfooyayMay 20, 2020May 10, 2020Posted inUncategorizedTags:optimization, performanceLeave a comment on Avoid premature optimization.

Observe single test cases in your IDE.

It’s a powerful tool, extremely useful in examining code coverage.

Posted byfooyayMay 19, 2020May 10, 2020Posted inUncategorizedTags:coverage, IDE, testingLeave a comment on Observe single test cases in your IDE.

Do not introduce extra logic for tests.

All logic should serve a business purpose.

Posted byfooyayMay 18, 2020May 10, 2020Posted inUncategorizedTags:TDD, testingLeave a comment on Do not introduce extra logic for tests.

An object should not have more than one trigger.

The trigger should have one job.

Posted byfooyayMay 15, 2020April 26, 2020Posted inUncategorizedTags:single responsibility principle, triggerLeave a comment on An object should not have more than one trigger.

Posts navigation

1 2 Older posts
Today's Card, Create a website or blog at WordPress.com
  • Follow Following
    • Today's Card
    • Join 40 other followers
    • Already have a WordPress.com account? Log in now.
    • Today's Card
    • Customize
    • Follow Following
    • Sign up
    • Log in
    • Report this content
    • View site in Reader
    • Manage subscriptions
    • Collapse this bar