Maggie++

Flock is built on the Mozilla Firefox open-source browser, so it has all the features you've come to expect in a high-quality web browser, like intuitive buttons and menus, personal customizability, reliable security, enhanced privacy protections, and automated updating. However, Flock is much more than that! The Flock Social Web Browser has been fully integrated with a wide range of social networking websites and popular blogging tools. So with Flock, you can now keep in touch and share text, links, pictures, video and more with friends, family and co-workers across the entire internet with unparalleled speed and seamless ease.

• People Sidebar allows access to Twitter, Pownce, Facebook, Digg, Flickr and YouTube

• Feeds Sidebar is a built-in feed reader.

• Web Clipboard allows you to drag and drop text, links, and images to save for later use.

• Accounts and Services gives you access to all of the accounts you have configured with Flock and also lists all supported accounts with links so you can explore them.

• Favorite Sites, lists your most recently viewed favorites.

• Favorite Feeds, displays your feeds with the most recent activity and indicates how many unread items are in the feed.

• Friend Activity, lists friends updates from you social networks.

• Favorite Media shows streams from You Tube and Flickr that you subscribe to.

Tags: social, flock, browser

CodeStock's mission is to bring the best and brightest code experts to East Tennessee for a one day conference open to all developers.

Are you among the best and brightest code experts?  If yes, then you are probably already registered.  If not, but you want to be, sign up and join me at CodeStock to learn and keep up with all of the new ways to improve your software skills.

There will be 6 choices of classes during each session and what I'm excited about is there will be Open Spaces all day where you can share and learn about whatever you are interested in. 

Open Space is a way to bring together groups of people interested in a common topic to have an interactive discussion. In an Open Space session, there may be an expert who is passionate about a topic presenting to an audience or there may be a small group of people discussing an idea.

Four principles of Open Space:

1. Whoever comes are the right people to be there
2. Whatever happens is the only thing that could have happened
3. Whenever it starts is the right time
4. When it's over, it's over

This is my kind of conference - a place where I can learn from other developers in a relaxed setting in beautiful Tennessee.  

Hope to meet you there.

maggie++

Gayle Force blogged about Women and the IT community when she was asked what to do to get more women involved in her local  Columbus Ruby Brigade. In reading her response I got to thinking about other experiences I'd had and the fact that a small percentage of attendees to user groups and communities events are women.

There do seem to be less women currently in IT jobs.  This has not always been the case.  I worked as a software engineer at three large corporations in the 80s after I graduated from college. There were actually more female than male programmers at the first and at the other two it seemed 50/50.  However there were no females in the senior/principal technical staff roles, who typically had greater than 10 years experience.

So what happened. Families. Women have children.  Some stay working full-time, some go part-time and some choose to stay home.  The ones that stayed full-time took the management track and became less involved in technical aspects.

The women who went part time were relegated to peripheral roles such as configuration management, source control, bug tracking and QA - these tasks were easier to share on a part time basis.

All of the women I knew who went part time, stayed home full-time after the birth of a second or third child.  None of these women that I know have returned to engineering.  Some have returned to full-time work in other fields.

In 1990 I left software to be a full-time SAH mom.  I loved my job and working on exciting projects, but the job also involved long hours, late nights in the lab and unplanned travel.  I was very dedicated to work and knew that I would have struggled to do both well.  I also knew I really wanted to be home full-time and to just concentrate on being a mom.

I loved being a stay-at-home mom.  During that time I met many extremely talented and creative women who had also left careers to be home.  There seemed to be a consensus that it was ok to take a year off from work, but any more than that would make it impossible to return to the work-force.

It does not need to be this way, a women does not lose her intelligence during this time and she also gathers valuable experience in the activities of being a mom such as organizing , leading, volunteering, coaching, advocating, researching etc.

Companies have noticed the effect of this female brain drain as noted recently in the Wall Street Journal in the article, Female Brain Drain in Science: “Much Has Yet to Happen”, where they discuss the study "The Athena Factor: Reversing the Brain Drain in Science, Engineering, and Technology"   Sylvia Ann Hewlett discusses this in her book "Off-ramps and On-ramps: Keeping Talented Women on the Road to Success".  She states that "corporations have done a dismal job of retaining female talent.  Indeed, they make it very easy for women to depart. When women take a temporary leave of absence to have children or deal with other personal matters, they find it difficult to return to work and contribute as they had previously. In essence, corporations provide women with many career off-ramps, but provide them with few on-ramps. This problem bodes badly for CEOs and top managers who view human resources as a critical asset."  Some steps companies can take are laid out in Flexibility Key to Retaining Women

I created my own on-ramp and returned to full-time software development in 2005.  It was not easy and I still have a lot to learn.  In a future post I will detail the steps I took to re-enter the work force.

maggie++

Michael Eaton has requested developers to share stories of how they got started in programming.  I started programming in the dark ages which many of you will not be able to relate to, so bear with me.

First of all, when I was a child no one had computers in their homes.  The only computers I knew about were at the universities and the government.  When I was in junior high, my school decided that it needed to give more focus on math and reading so it established a new format for Fridays.  Half the day was for math and half was for reading - this was set up to ensure everyone knew the basics.  Well those of us who were advanced past the basics got to hang out with the social studies teacher and learn fun things; I think there were about 10 of us.  He taught us Algebra and Geometry, we put on a play, learned about Fibonacci and many other cool things. 

Best of all he had access to a computer as he was taking graduate school classes at the nearby university.  He taught us the BASIC instruction set and had us write out programs on loose leaf.  At night he would go to the computer lab, type in each of our programs and bring us back the results.  This was the most fun I can remember from grade school.  Math was always my favorite subject and I loved puzzles and problem solving.  I don't remember too many specifics about the programs except I recall something with biorhythms and calculating things like how many days we had been alive.

My high school had a teleprinter with a tape in our math center.   I never had a chance to learn how to use it.  I envied my older sister who took an independent study class and got to (that she had a programmable TI calculator is another story).

My chance to program for real was in college.  I majored in Math and started taking computer science classes right away for a minor (at the time the college did not offer a major in CS).  We did not have our own computer, instead we had time-sharing with the mainframes at the University of Maryland. I learned assembler, Fortran, COBOL and Pascal.  Assembler and Fortran were coded with a line editor on a teleprinter; COBOL required punch cards and by the time I took Pascal we had CRT's - The summer before my senior year I had a mathematics summer internship at COMSAT Laboratory where my job was to write a program in Pascal to compute an algorithm for a mathematician.  The first day he gave me a 23 page hand written integral which was my assignment for the summer.  COMSAT was exciting - this is the first place I had ever seen real computers, plus they had a huge (satellite-sized) anechoic chamber, earth stations, library, and tons of special purpose electronics and engineering systems. 

The important things that happened that summer were I discovered that the mathematicians did not use computers at all, there was a lot of money to be made writing software and I met my future husband who was a RF Engineering Co-op.  The first didn't end up being true but the other two were good.

Once I graduated, I started job hunting.  I had success at my first job fair.  I walked around the room and talked to all the men and one asked me if I knew assembler.  I said yes I knew Univac Assembler, he smiled, gave me a business card and set up an interview for me.  I looked up and saw that the company he worked for was Sperry Univac.  I started work right away.  We were a subcontractor for Ford Aerospace on a NASA contract.  I worked on a 16 bit (hex) mini-computer with ASCII and two's complement arithmetic and communicated with a 36 bit (used octal) mainframe that used 6 bit Fieldata and one's complement arithmetic.  Needless to say I learned a ton, met great people and saw a successful large project installation.

The most fun I had at that job was testing in the lab with the mini-computer.  I loved being able to toggle switches to set a breakpoint and look at indicator lights (the only UI) to read the register contents and memory, following along with a printout of the assembler code with addresses and the op-codes.  I liked making up  and applying patches on the fly when I found a bug. A also liked getting a memory dump of the processor and searching through the buffer pool looking for buffers that hadn't been returned and ones that overwrote their boundaries.  I had full control of the machine and yes I am a geek.  I still eally like debugging - yes I know 'm a geek.

At the same job the boss felt it was important not to work through lunch so we played bridge, then when Trivial Pursuit became popular and we had more people we played that.  Some days we just hung out at the terminals and played zork.

Ok, enough with history and back to the questions.

What languages have you used since you started programming?

At least 5 assembler languages, BASIC, meta-assembler, Fortran, Pascal, Smalltalk, Prolog, Lisp, C, Cocoa, Java, C#, and C++.

If you knew then what you know now, would you have started programming?

Absolutely.

If there is one thing you learned along the way that you would tell new developers, what would it be? 

Don't stay at a job you hate with people you don't admire.  You want to be in a group where learning and communications are encouraged and required.

maggie++

Hello, world.  This is a pre-first blog post.  I am completely new to blogging.  I will place real content soon.  Please leave a comment here if you have any good suggestions for improving the look of the page.

maggie++