Doubling Down: My Specific Strategy

Doubling Down: The Quick Background I recently wrote about how and why I'm looking to double down on my strength to improve a weakness, and I figured it would be a great follow up to try and explain the specifics in my strategy. It's an interesting learning opportunity for me, so why not share it with those that are interested? The format of this post is really just to call out the specifics of some strategies I'm looking at exploring when building the brand for my vehicle to help with sponsorship opportunities. Reach Outside Core Audiences This one shouldn't be a shock to you if you're familiar with this blog already. It's primarily aimed at programming, leadership in a tech environment, and self reflecting as a means to improve. One of my goals is to explore attracting other audiences that…

1 Comment

API: Don’t Forget About The Non-Public API!

Background From an¬†object oriented programming perspective, an application programming interface (API) is often referred to as the way other developers can interact with the public members of your class(es) and interface(s). Of course, API can be used to describe how one interacts with a web service (or other types of services), but for this discussion I'm limiting the scope to that of interfaces and classes. Limiting the definition of API to public members (or the equivalent of C#'s "public" in other languages) is omitting one huge part of what it encompasses. The purpose of this post is to clarify, in my opinion, why I think forgetting about the non-public API can lead to bad framework and API designs. API And The Audience I've written before about what I think makes a good API, and I had some comments on Code…

4 Comments

End of content

No more pages to load