Have spent the better part of yesterday night writing a Perl script to aid my fiance' in doing some log analysis. And I’m no Perl guru - my biggest Perl program till date wouldn’t have been more than a 100 lines. Here’s my raves and rants on it Raves Most powerful reg ex capabilities with a full programming language to back it up! Large and powerful standard library.
So I managed to get myself a gmail account - raghu dot rajagopalan at gmail dot com :). And I love google groups access. However, wanted to know if there is some way where my posts don’t show my email address. Have posted a query to google feedback - will let you know if something comes of it. Meanwhile have started looking at NUnitForms - have to try out some code to see if it’s as nice as nunit.
Havent really been active on the blog - kind of ignored it till now. Anyway, I’m back, fwiw. There’s been quite a lot of changes here and I guess that’s the thing that’s kept me from blogging - add to it the fact that I’m new to maintaining a journal on the web. These days am looking for some generous person to invite me to Gmail. Haven’t really done much on the programming front - other than digging around to find out if I can launch an executable on the client from a web page without the warning pop ups.
Anti patterns - What not to do Pitfalls to avoid However, an equal number of implementations that run into rough weather are also because they lack strong engineering leadership. Especially in a corporate/enterprise environment, you need strong engineering leadership who can push for good engineering hygiene. Now, none of these are very special to microservices so it’s Lack focus on the domain - The easiest way to mess up a microservices implementation is to not structure your domain well.