IgorShare Thoughts and Ideas

Consulting and Training

Archive for July, 2008

Pheww… Two more will not tip the bucket.

Posted by Igor Moochnick on 07/28/2008



This is how it looks like on the paper:


Posted in C#, Community, Thoughts, Visual Studio | Leave a Comment »

Design Coding rap – hilarious

Posted by Igor Moochnick on 07/08/2008

Posted in Thoughts | Leave a Comment »

Handy Sketchup library

Posted by Igor Moochnick on 07/08/2008


Started to play with Sketchup and found a very handy collection of the different computer components @ http://scc.jezmckean.com/

Posted in Tutorials | 1 Comment »

Welcome to my new electronics blog

Posted by Igor Moochnick on 07/07/2008

I’ve decided to take my tutorials, thoughts and rants about all electronics-related topics into a separate blog: igorbits.wordpress.com.

Welcome to my new blog!

Posted in Community, Electronics, Hardware, Presentations, Thoughts, Tutorials | Leave a Comment »

Events notifications for community guys

Posted by Igor Moochnick on 07/07/2008

For those who are involved in the community life – check out the new site that gathers different event notifications: Gary’s Guide.

Posted in Community, Thoughts, Tutorials | Leave a Comment »

Upcoming Northeast developer events and talks

Posted by Igor Moochnick on 07/07/2008

Hartford, CT CodeCamp – August 16

I’m planning to bring an agile-development-related presentation. I think it’s a time to start razing a bar for the community’s developer skills level.

Let me know if there are any other requests for the presentations.

I’ve never been to Hatford, CT – what are the favorite places and to-do things there?

For more Northeast developer events see Chris Bowen’s post.

Posted in Alt.Net, Community, Software, Thoughts, Tutorials | Leave a Comment »

Programmer Insecurity

Posted by Igor Moochnick on 07/07/2008

While discussing with co-mentors of GSoC (Google Summer of Code) the communication channels and practices a “Programmer Insecurity” blog post was mentioned – great article and right to the point.

[Short comment:] The problem is that at the beginning of the project when a developer (mainly if he works alone) is still discovering the play field and is not really sure what is he doing. In this case he works on a proof of concept. In many cases the proof of concept becomes an “alpha” version of a product. Yes, it is very dangerous (if the code originally was poorly designed and badly written), but it happens a lot. This leads me that there are certain cases when “reset” of the history becomes handy, but, I do strongly agree, that in most cases, the “programmer insecurity” kill the communication of the ideas and intentions which lead to bad designs, poorly written code and a lot of cleaning work.

  Don’t be shy to hear the feedback and either accept or decline – but do it openly in the open-source world.

Posted in Thoughts, Tutorials | Leave a Comment »

%d bloggers like this: