Anti-Résumé

“People don’t walk around with anti-résumés telling you what they have not studied or experienced (it’s the job of their competitors to do that), but it would be nice if they did.”

— Nassim Nicholas Taleb (from “Why You Should Surround Yourself With More Books Than You’ll Ever Have Time to Read”)

This anti-résumé (together with my résumé) will help me find the best job that fits my current skillset, and it will help you in determining if I am fit for your team or not. That would be win-win for me and you! :blush:


I never experienced being an Algorithmer

In my résumé, I considered myself as an Initiate, based on Terence McGhee’s “Software Ninja Class Hierarchy”. But I never experienced being an Algorithmer, even though it is much lower than the Initiate in that hierarchy — I do not have special knowledge in higher mathematics. My weak mathematics background is the reason why I concentrated on learning how to build what they call line-of-business (LOB) applications (or what is called “representational-transactional systems” here), because these things do not need lots of knowledge in mathematics.

But I can work with an Algorithmer, and I have high respect for an Algorithmer, because I would have liked to experience being an Algorithmer if I had the chance or education to become one when I was younger…

And I believe that working with an Algorithmer will benefit me — I believe that I will learn a lot from an Algorithmer. I’m hoping also that an Algorithmer will learn a lot from me too, if I will be working with one.


I’m not an expert on frameworks

“… Here’s a possible surprise for you. I am not going to recommend that you need to become an Entity Framework guru. Nope, just the opposite in fact. I am going to suggest that you allow the Entity Framework development team to be the gurus, and you just focus on your specific application. After all, your Core Domain is where you want to put your creative energies, not in becoming an expert in Entity Framework.”

— Vaughn Vernon (from “Modeling Aggregates with DDD and Entity Framework”)

You might say, “What! Frameworks are the ones that make us do our work easily and fast! Why are you saying that being an expert on frameworks is not important?”

Wait!… I am not saying that being an expert on frameworks is not important. What I am trying to say is that, in programming, there are more important things to focus on than being an expert on frameworks — such as separating the business rules from the other parts of the system. The business rules in a system are not googleable, so I believe that it is very important to separate them so that it will be very easy to locate them when fixing bugs.

You might ask what my excuse is for not being an expert on frameworks…

My excuse is that frameworks change very often and I do not have all the time to catch up with all the changes. Also, many years ago in our school library, I read this from a book called “The Magic of Thinking Big”:

“It is more important to use your mind to think than use it as a warehouse for facts.”

“The ability to know how to get information is more important than using the mind as a garage for facts”

Today, we already have [the] google [search engine] which can serve as our garage for facts. We have StackOverflow too! And we have documentations for the frameworks we are using that are readily available online.

Because I don’t have all the time in the world, I will have to learn frameworks as I go.

(Related to this is my “Learning Philosophy”)


I’m introverted

… Which means that I might be very silent on my first encounters with a person, but will start to speak up when I get comfortable working with that person. :blush:

But there are times where I tend to be not that silent even with people I do not know when the topic of a conversation is something I’m very interested in, such as programming.


I’m not (yet) very good with my spoken English

English is not my native language. So for me, writing in English is easier than conversing using it. Because when writing I have lots of time to think on what to write. When conversing using English I need to respond quickly and there is very little time to think. :grin: