Monday, 22 May 2017
போகர்......
மழையில் நனையாதிருக்க போகர்.......மந்திரங்கள்
விடத்தலை கற்பம்....போகர்......
ஓரிதல் தாமரை.....கற்பம்
போகர் ரகசியம்....
இரும்பை செம்பாக்கும் ரசவாதம்......
போகர் அருளிய கருநெல்லி......
அஷ்டமாசித்துக்கள்........
அஷ்டமாசித்துக்கள்...
அணிமா:
பெரிய ஒரு பொருளை தோற்றத்தில் சிறியதாகக் காட்டுவது/ஆக்குவது. ப்ரிங்கி முனிவர் முத்தேவர்களை மட்டும் வலம் வருவதற்காக சிறு வண்டாக உருமாறினார் என்ற செய்தி அணிமா என்ற சித்தைக் குறிக்கும்.
மஹிமா:
சிறிய பொருளைப் பெரிய பொருளாக்குவது. வாமன அவதாரத்தில் திருமால் இரண்டடியால் மூவுலகை அளந்ததும், க்ருஷ்ணன் அர்ஜூனனுக்கு உயர்ந்த வடிவம் காட்டி உலகமே தன்னுள் அடக்கம் என்று காட்டியதும் மஹிமா என்னும் சித்தாகும்.
லஹிமா:
கனமான பொருளை இலேசான பொருளாக ஆக்குவது. திருநாவுக்கரசரை சமயப் பகை காரணமாக கல்லில் கட்டி கடலில் போட்டபோது கல் மிதவையாகி கடலில் மிதந்தது லஹிமா ஆகும்.
கரிமா:
இலேசான பொருளை மிகவும் கனமான பொருளாக ஆக்குவது. அமர்நீதி நாயனாரிடம் கோவணம் பெறுவதற்காக இறைவன் வந்தபோது, ஒரு கோவணத்தின் எடைக்கு தன்னிடமுள்ள எல்லா பொருட்களை வைத்தும் தராசுத் தட்டு சரியாகாமல் கடைசியாக தானும் தன் மனைவியும் ஏறி அமர்ந்து சரி செய்த சித்தி கரிமா.
பிராத்தி:
எவ்விடத்திலும் தடையின்றி சஞ்சாரம் செய்வது. திருவிளையாடற்புராணத்தில் "எல்லாம்வல்ல சித்தரான படலம்" என்னும் பகுதியில் சிவன் ஒரே சமயத்தில் நான்கு திசைகளிலும் காட்சியளித்ததாக வரும் சித்தி பிராத்தி.
பிரகாமியம்:
வேண்டிய உடலை எடுத்து நினைத்தவரிடத்தில் அப்போதே தோன்றுதல். அவ்வையார் இளவயதிலேயே முதுமை வடிவத்தைப் பெற்றதும், காரைக்கால் அம்மையார் தன்னுடைய அழகான பெண்வடிவத்தை மாற்றி பேய் வடிவம் பெற்றதும் பிரகாமியம் என்னும் சித்தாகும்.
ஈசத்துவம்:
ஐந்து தொழில்களை நடத்துதல். திருஞானசம்பந்தர் பூம்பாவைக்கு உயிர் கொடுத்து எழுப்பியமை ஈசத்துவம் எனும் சித்தாகும்.
வசித்துவம்:
ஏழுவகைத் தோற்றமாகிய தேவ, மானிட, நரக, மிருக, பறப்பன, ஊர்வன, மரம் முதலியவற்றைத் தம்வசப் படுத்துதல். திருநாவுக்கரசர் தம்மைக் கொல்வதற்காக வந்த யானையை நிறுத்தியதும், ராமர் ஆலமரத்திலிருந்து ஒலி செய்து கொண்டிருந்த பறவைகளின் ஓசையை நிறுத்தியதும் வசித்துவம் எனும் சித்தாகும்.
Sunday, 14 May 2017
Happy Birthday Mark Zuckerberg, Facebook CEO Turns 33 today!
"Happy Birthday Mark Zuckerberg, Facebook CEO Turns 33 today! Laughing Colours 14 May.
2017 21:04 Mark Zuckerberg, the man who revolutionalised Social Media with creating Facebook has turned 33 years old today. He is known as the “Father of Social Media” and few people even thank him for gifting us with such a platform to connect with people. Facebook was started 13yrs back when he was roughly 20yrs old and since then, he never had to look back.
The journey was a bit tough but he came so long crossing all the hurdles and we just wish to see his glory in the coming years too. He was always different from normal kids or humans.
For example, at the age of thirteen, when most people worry about homework, Zuckerberg created Zucknet — a basic computer network for his family that allowed computers in his father’s office to send messages to the computer at home. Something that even the professionals had to think about before creating back in the days. This young guy is so amazing that As per the Forbes Global Rich List 2017, Facebook founder Mark Zuckerberg moved up to number five for the first time in the richest people on the planet list, after his fortune rose 11.4 billion USD in 12 months.
Mark Zuckerberg’s total net worth is over 62 billion USD. He even became the youngest billionaire in 2008 when he was just 23yrs old.
Such Achievements yet no showoff!
We Wish Mark Zuckerberg a very happy and prosperous Birthday and we are greateful to Mark for giving us Facebook, if it didn’t existed then nor Laughing Colours would be existing! :) Thanks again Mark, Stay Gold!" - Happy Birthday Mark Zuckerberg, Facebook CEO Turns 33 today!
Sunday, 7 May 2017
How to be a Good programmers
How to be a good programmer...
My tips By Sandip Dev on Aug 15, 2009
This article has been cross posted from my personal blog : http://www.itsallpartoftheplan.wordpress.com At the very onset, let me make it clear that I DO NOT consider myself a good programmer. I rate my coding skills as average and I am still learning and have a long way to go before I am even slightly pleased with my programming skills. Yes I am better than quite a few people when it comes to programming, but thats merely because they are lazy and like to sit on idly all day and never bother about programming. Their horrible skills make my less horrible skills look marvellous. I have performed abysmally in ICPC and have never done well in any coding contest worth mentioning (I DO NOT consider college level contests worth mentioning). I havent succeeded yet in Google Summer of Code and my Imagine Cup moderate success (and glorious failure) isn't much to write home about. So most of the tips I will mention below are lessons learnt from failed endeavours, they are what I have wanted to be and I am not. So lets dive in. 1.Decide why you want to become a good programmer: Is it because you want a job, preferably in a high paying software firm? Great. Then you are set to reach NOWHERE. All good programmers I know are good because they loved what they did. Develop interest in programming. See, programming is the only branch in engineering where you can straightway apply what you learn. Your dad may have a car but he certainly wont allow you to tweak the V2 or swap it for a v6 just to see what happens. But with computers you can do whatever you want. You want to simulate a virus? Cool. Install a virtual OS and run it. Then, when you are done, remove the virtual hard disk. If you are good at what you do, you will get paid and surely get that dream job. Yes, even I want to work in a big software company. But thats not because of the fat paycheck. Its because of the work they do. Because of the exposure I will have. Have you ever bothered to find out what all these companies do and the enabling technologies behind their products or the kind of R&D they do? Jobs will come. Dont make yourself a sucker for one. Sachin is not a great cricketer today because he decided to play cricket to earn money and get dozens of endoresements.
2. Programming languages: Very often people equate good coding skills with number of programming langauges known. Thats just damn untrue. While knowing a lot of programming language is good and sometimes, even, essential; it is more important that you know one or two lanugages very well. I 'know' and have used more than a dozen programming languages and yet C and Java are the ones I am truly comfortable at. Thats sad of course. I really wanted to be good at Assembly and Lisp as well. Never got the time or chance to develop those skills. To be good at a language takes years (at least 2 years). Being good at a language means, you understand where it is best used and where using that language makes no damn sense. On the other hand, knowing a language takes anywhere from 3 days to a week. If you are a beginner, learn C first. Don't buy Yashawant Kanetkar. Buy the book "The C Programming Language" by Brian W Kernighan and Dennis M Ritchie (If you don't know who they are, do this
1. Slap yourself
2. Google their names). This book is not the easiest but is the best. Its a small book but it is the most powerful. Generations of programmers have been brought up on it. And if you think this book is tough for you, please do not harbour any misplaced desires of being a good programmer and do not waste your time by reading this post further. Programming is an art (not a science. Yes you read it correctly), and like any art it requires painstaking effort. Some people suggest Python as the first language to be learnt. Python is certainly a good language and is easy too. But you will have to rely mostly on the internet for help as not many around you would know Python. Also C has the broadest usage among all programming languages. Also please DO NOT use Turbo C. Its so damn outdated. Use GCC. If you are in Windows download Dev C++. It has GCC Read this (small) essay by Peter Norvig Teach yourself programming in 10 years . Again, do a Google [ ]search and find out who Peter Norvig is.
3. Algorithms: Any good programmer has a good understanding of algorithms. Its not necessary that you know each algo by heart (in fact good programmers never learn things by rote) but you must understand when to use what. Algos will broaden your understanding and give you new ways to tackle problems. Another important thing is Data Structures. Its more important than algo. Once you have chosen (or developed) the correct data structure, the algorithm becomes self evident. For algo, read the book "Introduction to Algorithm" by Thomas H Cormen et al. You may also refer Andy Tanenbaum's "Data Structures in C and C++". Also if you have desires to participate in coding contests (the respectable ones), "The Art of Programming Vol I to V" by Donald E Knuth are mandatory. Also may be "Concrete Mathematics" by Donald Knuth. Again reading does not mean remembering everything. Just try and understand whats written.
4. Coding contests: Coding contests are good for developing your algorithmic skills and they make you think fast. Its a good idea to participate in ACM ICPC or Topcoder.com. Then there are coding contests (like Sun's Code for Freedom, Google's Summer of Code, Microsoft's Imagine Cup) where you develop a complete software. Such contests are spread over many months. Both require different sort of skills. You may be good in one and bad in another and yet you could be a good programmer. Contests like ICPC require lot of practice, fast thinking and you are expected to keep algos at the back of your mind. CFF, GSoC, on the other hand, requires creativity and focus spread over a long period of time. You dont have to come up with solutions too fast and you dont have to mug up algos. ICPC is like T10 while CFF,GSoc and Imagine Cup are like Test Matches. I would suggest you to participate in both types and then decide if you want to focus on either or both. 5. Participating in FOSS projects: You MUST participate in some free software projects. There are just too many. I am working on SCALASCA right now and then I will move on to Sun Grid Engine and Sun xVM Hypervisor and contribute code there. You learn a lot from these. You get to see a lot of code and learn the best practices. And did I mention, it looks good on your CV too. Most people catch cold feet when they go through some of the prerequities of such projects. Take Thunderbird for example. You would need to know a lot of C/C++ and Javascript (for developing modules). Now don't wait till the day you are an expert in these languages before contributing. Programming is an art, don't waste time sharpening your pencil when you should be drawing. You can ask me for directions. 6. Design Patterns: Any art is learnt by emulating. And therefore, you must emulate the best. Design Patterns are tried and tested architectural (of the software kind) solutions to some commonly encountered software design issues. And therefore, a basic knowledge of some common design patters in needed if you are planning to develop something that is even moderately complex. I suggest "Head First Design Patterns" from Oreilly as the first step. 7. Learning by emulation: Emulate the best. And this is possible by reading books written by the best and/or going through code from some of the best free software projects. I would urge anyone serious about programming to read the book "The Art of Unix Programming" by Eric S Raymond (dont forget to first slap yourself for not knowing who Eric Raymond is and then googling his name). You are not a programmer if you have not read that book. Period. Now let me address a few common grouses a. I dont find any interest in computers and want to do an MBA:Mainly a statement often repeated by Second Year(sophomore) students. Thats really your problem. I did not ask you to take Computers or even to join Engineering. You did not know, or bothered to find out, what you were getting into when you took up this branch of engineering and I am pretty sure you have NOT bothered to find out what awaits you in a MBA course either. I am also quite sure that 2 years after an MBA (if not earlier) you will also say pretty much the same thing about your job. Well what can I say. All the best b. I dont like reading the books (or any books for that matter) that you mentioned above: Well this is not yet the world of Matrix where I can just feed in programming skills to your brain. Dont force yourself to read them. You can't . Do it only if you want to. And if you don't, please forget about being a good programmer. May be its time for you to use the excuse mentioned above (point a). c. Give me one programming language that does all: There is none. Each has a different purpose. And thats how things are gonna remain buddy. d. I want to a 'real' project: Thats great. You can do two things:1. Start one of your own 2. Join a FOSS project. But most people are not happy with this. They expect me to 'give' them a project, one thats easy (read, should not involve anything other than C and the only files you need to include should be stdio.h, conio.h (yes people here still use Turbo C) and may be string.h and math.h) and I should tell them what to learn. When people say this,they expect to go on a Autopilot ride. e. I will learn X programming language by this sem/year/decade :There is no way you can sit with a book and learn a language. You need to do some real work with it, develop some real software and not just do those exercises in the book (that is necessary of course but not sufficient). Most of the languages I have learnt are because I was forced to do so as part of some project. Just pick up the basics in a day or two and then apply it to a real life project. Need ideas? Come to me. Finally as Larry Wall says in Programming Perl : "We will encourage you to develop the three great virtues of a programmer: laziness, impatience, and hubris." Laziness:So that you go to great effort to reduce overall energy expenditure. It makes you write labor-saving programs that other people will find useful, and document what you wrote so you don't have to answer so many questions about it. Hence, the first great virtue of a programmer Impatience: The anger you feel when the computer is being lazy. This makes you write programs that don't just react to your needs, but actually anticipate them. Or at least pretend to. Hence, the second great virtue of a programmer Hubris: Excessive pride, the sort of thing Zeus zaps you for. Also the quality that makes you write (and maintain) programs that other people won't want to say bad things about. Hence, the third great virtue of a programmer. So get set on your way to become a great programmer, the likes of Richard Stallman, Rithcie, Brian, Raymond, Torvalds. All the best.
Friday, 31 March 2017
Windows 7 Ultimate Product Key
J783Y-JKQWR-677Q8-KCXTF-BHWGC
C4M9W-WPRDG-QBB3F-VM9K8-KDQ9Y
2VCGQ-BRVJ4-2HGJ2-K36X9-J66JG
D8BMB-BVGMF-M9PTV-HWDQW-HPCXX
THHH2-RKK9T-FX6HM-QXT86-MGBCP
MGX79-TPQB9-KQ248-KXR2V-DHRTD
V2KHD-CXKRG-VQB7C-GXCX3-K9B6K
TFP9Y-VCY3P-VVH3T-8XXCC-MF4YK
CMBJC-VHBMB-C4H3F-QCXGM-X48JP
J9GR3-BG6D8-BDTWB-HTW6M-9MF4C
CR8D2-XCB3Q-MH2XG-4FFYY-DKJ6P
HXJC9-DYFJ8-4R2TV-2X4FK-Y2JBH
BHGRJ-VC4PK-7JJ4H-6X476-MJ28B
GMY2P-RBX7P-TQGX8-C8B9B-BGXFF
BF9J7-HKCFK-D2TCB-TPH7R-43CD8
PVMYG-HQDP7-PHHFT-X2PBD-6VDX4
J3MPD-MX97W-MM34H-RYR23-C2MGX
9D7WR-JB2Q4-9G6W9-B9327-28H4R
4FMW9-MXPRT-3KQ3C-63D3T-X9JTH
GQ6JK-GQXQV-WJJ87-R4MKB-FKQGF
VT4PJ-KTF64-JYWB8-QV9YQ-2PTGG
J78FT-J48BQ-HH2M7-CYVTM-MXRHY
FJHWT-KDGHY-K2384-93CT7-323RC
KJYJB-GDCGX-2DKYQ-XY3YF-TF3FW
9BP77-QHMM6-RKYF7-CKVYY-YCRXF
GGH2V-X4V32-G7G7Q-KC7H6-3T228
VM2RB-GH8PH-38DTP-M3WFT-GG2Q9
PTJCK-DPFYX-73W7B-GMMKC-RB6CJ
BJH3H-B776D-P26TW-J3K3F-FF24Y
GQ3P9-26XW6-YP398-9DHT2-8BHR2
2VQ2W-WKW6B-X47XG-48JXY-H3CGK
V7RHR-P7JXH-P69TF-HDJXF-8FWFB
MGV6C-PBMDF-T497W-YK8F4-CD4W4
9FP3F-DKD8H-PRYD3-YFCRY-TFW6R
342DG-6YJR8-X92GV-V7DCV-P4K27
FJGCP-4DFJD-GJY49-VJBQ7-HYRR2
49PB6-6BJ6Y-KHGCQ-7DDY6-TF7CD
2Y4WT-DHTBF-Q6MMK-KYK6X-VKM6G
2XPWB-Q64BJ-W8CT3-WJTWT-4DQ99
39QDH-D7MHH-WDMTD-TM2R9-KM7DB
TTJQ7-4PFJC-6JFJ8-B22VD-VXW88
V3Y2W-CMF9W-PGT9C-777KD-32W74
7K377-DVP2Q-YGWJG-3M3G7-RBCDP
83K3W-QH8JT-T7KBY-9FQB6-V9R8H
C23T3-9F2T2-FPWBM-XYMW2-272J9
3743C-T6892-B4PHM-JHFKY-4BB7W
8YDX9-B7MMG-82XD9-V88G9-MR92T
BVQFP-FKQGV-J82F3-2JTVV-733D2
BQVFY-KWH4H-77C6M-WWCX7-YR3DP
XH7KY-9YP9X-G9M34-JJH66-HXK9C
4JQJJ-JHBC9-FWXH9-8JD4P-DFC6Q
CVMJC-RFXWY-WT37Q-DF8R4-QTPVR
6HWKG-GFF2D-CK9V8-VRPKV-K866B
MV8X8-97W7G-DYXKX-J7M8Q-F6PWJ
XB8VY-MWGCF-XM8QY-TWXF7-WFVQD
BXVYJ-YG8KF-Q663H-8TDMF-3K37H
J6H7Y-8W4WC-XXRVM-PWBBG-4BB7T
BPRDM-38BX4-P9XJT-7Q3RQ-D6JDM
TRXW8-YQDCY-P866Y-J6RDF-GMK7Y
4HDB9-DQHDQ-6D82P-PRPPK-67T78
6Q4JV-JW3MX-MTDTJ-R6F2T-6P2R7
MPK6X-PBFYM-J22TB-C2KCW-3CYBK
BR2KH-T22XP-Q4JH7-TCF9T-C2MYF
3YRVC-6TB8V-4GDQT-C993J-8CGPG
9G39K-WDXBV-XQ27Y-GB6RP-JXJ37
TJYHH-VCQW3-CP7Q9-J3C7W-MDJXB
YB23W-PHMBY-TGHHC-DDM8Q-4GBW2
88FB7-VJJ4W-YRKWF-GFY97-XBDGY
Tuesday, 21 March 2017
7 importent to skills developing
1. Be curious :
Curiosity is essential because it makes the process of developing skills much more enjoyable. If you are curious, you will naturally want to know more simply because it’s fun. You will go further and deeper than those who develop their skills because they must. Here are some things you can do to build curiosity: Don’t say that something is boring Saying that something is boring is killing curiosity since it closes door of possibilities. Make asking a habit Often we take things for granted and accept them as they are. Don’t. Build the habit of digging deeper below the surface. Your tool to do that is questions. Make things fun Don’t just look at the serious side of things. Look at their fun side too.
2. Develop your learning skill:
Learning skill should be the first skill you develop because it greatly helps you develop other skills. An essential ingredient to have good learning skill is motivation. If you are motivated to learn about a subject, it will be much easier for you to learn it. Again, curiosity plays an important role here because a curious person is naturally motivated. There are many books that can help you hone your learning skill but two that I recommend are Accelerated Learning for the 21st Century and Learn More Study Less.
3. Be a versatilist:
A versatilist is someone who can easily adapt to new situations and quickly develop the skills necessary to excel. Being a versatilist essentially means being a smart learner who knows what to learn and how to quickly learn it. To know what to learn, a versatilist should anticipate the future. That way he will get a sense of what new skills will be in demand and prepare himself before most people do. Here are two posts that further discuss this topic: Be a Winner by Being a Versatilist: What, Why and How 6 Things You Should Do to Anticipate the Future
4. Find your role models:
It will be easier for you to grow if you have concrete examples of what you want to be. That’s why it’s important to find your role models. Your role models give you a standard to achieve so that you know where and how far you should go in developing your skills. It will also motivate you since you know that someone has already achieved such high standard.
5. Find your mentors :
While having role models is good, in many cases you can’t connect directly with them. But developing skills will be much easier if you work with those who have gone through it. That’s why you should find not just role models but also mentors. Ideally your mentors are also your role models but at least they are those who are more experienced than you. These people can teach you what to do and what not to do so that you don’t have to find them yourself the hard way. You can save a lot of time. Finding mentors, of course, is not easy. Often you should give first before someone is willing to become your mentor. Try to be useful to them by helping them in whatever way you can. Give them a reason to invest their time in you.
6. Get feedback through real projects :
The best way to develop your skills is through real projects. Why? Because real projects give you the much needed feedback to hone your skills. While many people prefer to wait until everything is well-prepared before working on real projects, you will learn faster by working on something real. You may face failures in the process but they are your stepping stones to success since they give you precious lessons.
7. Shorten your learning cycle :
The speed of your skill development depends on the length of your learning cycle. The shorter your learning cycle, the faster you will develop your skills. Here are some ideas to shorten your learning cycle: Make quality effort I already mentioned that you should work on real projects since they give you important feedback. But having feedback alone won’t help you much. You must have quality feedback. To have it, ensure that your effort is quality effort. Prepare yourself as good as you can (without being over prepared) before launching an initiative. This way the feedback you get will be of higher quality. Measure comprehensively The feedback you get should also cover as many dimensions as possible. You can achieve it by measuring your performance comprehensively. The more metrics you measure, the better feedback you will get. Of course, the metrics should be chosen carefully so that you don’t waste your resources on measuring. Act upon the feedback After getting the feedback, you should act diligently upon it. Learn as much as possible from the feedback to get the most possible points for improvements. Then choose the most potential ones and do your best to improve them before launching your next initiative.