I woke up today and realized that I want to update my old app “Irregural Verbs Trainer” to Windows 10. This is a bit strange because I am currently working on Piano 3D. There is no way I will release Piano 3D in the following month though, and I want to ship smth. Smth = Irregural Verbs Trainer in this case.
Irregural Verbs Trainer is a great app, but users do not use it. I have got only about 400 downloads of this app which is basically nothing. The reason: I made the app not free, although there is an unlimited trial version. So, 95% of the app is bascially free, but in the store it is listed in the “Paid apps” category. It is silly if you think about it. Never ever make a small app not free from the beginning. You don’t have marketing budget and users hardly ever buy an unknown app, especially such a small one. Much better option is a free app with IAP (in-app purchase), at least it will not scary users away.
So I decided to switch from Piano 3D development and other thoughts in my head and ship a new version of Irregural Verbs Trainer in short period of time (no more than 2 days).
There is one small problem though: I do not have Windows PC, only MacBook with MacOS.
I decided to write a post about skills IMHO a person should have to get a job as a .NET web developer.
Well, the mindmap above contains everything I wanted to say, so let’s just review it. I also will try to
give some recommendations about resources and books you can use to improve your knowledge in particular area.
It’s obvious that each .NET develop should know .NET fundamentals (CLR, CTS, JIT). I don’t say you have to know
internals of JIT compiler, but it’s essential to have high-level understanding of this concepts.
Logging is a really important system if you care about your users. Not only should it give you errors details, but also notify you that something is wrong before users start complaining
or submitting bug reports.
There are probably dozens of logging solution, and I’m sure there are hundreds thousands of self-written loggers on various projects. But I wouldn’t recommend writing your own logging since
you probably won’t be able to do it right the first time (and the second, and the third etc). It’s better to use existing solution, like ELMAH (Scot Hanselman’s blog post about it)