My two cents on software development

The support for rich typographic features for Web is increasing continuously. Support for web fonts with @font-face rules and open type features was a big leap forward. For some beautiful examples see  Awwwards  typography section: https://www.awwwards.com/websites/typography/ But its still well behind the high end capabilities of page layout design and publishing desktop applications such as QuarkXPress , Adobe InDesign , Scribus , Serif PagePlus/Upcoming Affinity Publisher etc. Text with rich typographic control provided in these kind of applications cannot be represented on Web with simple mapping of objects to html elements and properties/attributes to css styles. So I was tasked with a similar requirement: The rich typographic contents of the page layout and designs of the application must appear pixel-perfect in html browser and different e-readers. The analysis narrowed down to a couple of ways Having usual <p> and <span> elements and controlling their po

In this post, I intend to compile a list of links to resouces on What everyone should know about different technologies and concepts. So reader, please suggest topics and the article/book/video link in comments, I'll update the list attributing you as contributor. Thanks Updated: 01-Mar-2019 (Added Memory entry) Updated: 17-Jan-2019 (Added DBMS entry) Unicode The Absolute Minimum Every Software Developer Absolutely, Positively Must Know About Unicode and Character Sets (No Excuses!) - An eassy by  JoelSpolsky . Floating Point What Every Computer Scientist Should Know About Floating-Point Arithmetic  - IEEE 754 article by David Goldberg What Every Programmer Should Know About Floating-Point Arithmetic - Explains concepts of above paper, making it accessible to novices. Memory What Every Programmer Should Know About Memory - By Ulrich Drepper .NET What Great .NET Developers Ought To Know - Article by  Scott Hanselman .

If you are a developer or a member of a team developing & maintaining desktop applications, you are inevitably going to face application crash issues. More the legacy and large application, the more sophisticatedly you have to handle them. From developer point of view, application crashes can be categorized as: Non-reproducible crash, Always Reproducible crash, Reproducible Crash only on customer machine, Random crash. To be able to find out the reason of crash, the crash log or Stack Trace is your true friend in need. As it happens on some really bad days, you may be facing some crash issue without crash log . The steps below may help you in those times. So read on to know how to get the crash log when Application crashes without any crash log. Prerequisites : WinDbg - The Windows Debugger Download link: https://go.microsoft.com/fwlink/p/?LinkId=845298 Link may change over time, so here is the main page link:  https://developer.microsoft.com/en-us/windows/hardware/dow

Recently I successfully published a couple of ePubs on iBooks Store as free books. Second one took 15 minutes to submit. Yes only 15 minutes. However thats because I had spent 3-4 hrs in submitting first book and that experience helped me. The steps are clearly illustrated with screenshots at: https://www.aquafadas.com/documentation/calenco/en/Publish_an_ePub/content/ However its easier said than done for the first timers so I suggest you go through above once and follow steps listed below to avoid common mistakes. What all you need - A Checklist Apple ID [Can be created on  https://appleid.apple.com/ ] ePub you wish to upload ePubCheck [ https://github.com/IDPF/epubcheck/releases  or  http://validator.idpf.org/ ] Cover image for the book iTunes Producer [ http://itunespartner.apple.com/en/books/tools ] Optional screenshots of the book Steps to submit book on iBook Store Validate the ePub So you have your to-be-bestseller book as ePub file with you (say one g