Tom McFarlin

Software, Development, and WordPress

Page 2 of 398

Resources, Week of 27 June 2021

As I’ve shared in the last few articles for this category, I started sharing stuff on Twitter pretty regularly. But I don’t that much more either. So, given that I’ve started keeping a list of things in Apple Notes that I find useful, I thought I might as well return to form and share them here.

They will probably have a much longer shelf-life and maybe reach more people between subscribers and tweeting out a link to the post.

Continue reading

Resources, Week of 20 June 2021

As I’ve shared in the last few articles for this category, I started sharing stuff on Twitter pretty regularly. But I don’t that much more either. So, given that I’ve started keeping a list of things in Apple Notes that I find useful, I thought I might as well return to form and share them here.

They will probably have a much longer shelf-life and maybe reach more people between subscribers and tweeting out a link to the post.

Continue reading

Resources, Week of 13 June 2021

As I’ve shared in the last few articles for this category, I started sharing stuff on Twitter pretty regularly. But I don’t that much more either. So, given that I’ve started keeping a list of things in Apple Notes that I find useful, I thought I might as well return to form and share them here.

They will probably have a much longer shelf-life and maybe reach more people between subscribers and tweeting out a link to the post.

Continue reading

Resources, Week of 6 June 2021

Note long ago, I started sharing stuff on Twitter pretty regularly. But I don’t that much more either. So, given that I’ve started keeping a list of things in Apple Notes that I find useful, I thought I might as well return to form and share them here.

They will probably have a much longer shelf-life and maybe reach more people between subscribers and tweeting out a link to the post.

Continue reading

Don’t Over-Architect Your Blog Posts

At some point, I lost the motivation to write about anything that would include too much code because of the amount of time it would take to:

  • put a functioning solution together,
  • architect it in such a way that’d fit with best practices (at least for OOP),
  • explain the various features about OOP that the reader may not know,
  • then explain the problem.

This is too complex.

I’m not saying that articles shouldn’t be written that explain the concepts of object-oriented programming or shouldn’t talk about certain rationale for why something was done.

Continue reading
« Older posts Newer posts »

© 2021 Tom McFarlin

Theme by Anders NorenUp ↑