Nishanth' tech rambles

Something I spend 2 days re-learning from my MCA days!! Man am i forgetfull.. dont even know if my understanding is correct now.. Generating the Hamming code parity bits First thing to understand about Hamming code is the following Step1: Convert data into bits D0, D1, D2…. Dn-1, Dn where n is divisable by 2 E.g.: N=8 1 0 0 1 0 1 0 0 Step2: Next thing is called grouping. Group Bits in sequence of powers of 2 – call them group index [D0] [D1]…. [Dn] is grouped on power of 0 è[G0_0],[G0_1]…[G0_n] [D0,D1] [D2, D3].. [Dn-1, Dn] is grouped on Power of 1 è[G1_0],[G1_1]…[G1_n] [D0,D1, D2, D3].. [Dn-3, Dn-2,Dn-1, Dn] is grouped on Power of 2 è[G2_0],[G2_1]…[G2_n] Max such groups possible is possible is n/2 è [D0,.., Dn/2], [Dn/2+1,.., Dn] è[Gn/2_1][Gn/2_2] E.g: Groups= Group index 0: [1], [0], [0], [1], [0], [1], [0], [0] Group index 1: [1, 0], [0, 1], [0, 1], [0, 0] Group index 2: [1, 0, 0, 1], [0, 1, 0, 0] Step 3: Each Group has parity generated for all the data bits of each [Gx_y] using XOR...

am sleepy waiting for a t-con to happen that never seems to get finalized.. so here it goes.. From what i learnt (relearnt?) in the past couple of months: Why have my modules created least issues? 1. Be clear on what u need to do - fight with requirements teams if required. I love our requirement guys - they are good! 2. Estimate within reason - dont over budget/underbudget. But *spend time* on estimates - always be prepared for unexpected hardware/tools issues-estimate for it!! - I use a 3 point estimate as of now, till i get something better at least. 3. read a lot on the subject - TRMs, functional specs, similar implementation, irc logs, mailing list archives, other OS, validation code, what ever I can lay my hands on - the idea is know how the hardware works - thoroughly before touching s/w. 4. As a driver writer I need to know my users, so i talk to them.. in person, over emails, the final user is the best teacher.. (next to the requirements blokes). meetings.. over all architectu...