I have not failed 1,000 times. I have successfully discovered 1,000 ways to NOT make a light bulb - Thomas Edison
Over the past year I have been involved in a lean e-commerce startup that in the end didn't make it. Even though the company failed the team learned some valuable lessons which will help in the next venture and in our day jobs.
This is a panel discussion with some of the team members to share what we learned so you don't make the same errors we had.
I got my first programming job 15 years ago. It doesn't seem like that long ago, but in the world of IT that is a long time. I have spent all of that time in the Nashville Healthcare heavy IT scene. There was no SCRUM, no Test Driven development, no Agile, and not much off shore development. Microsoft was the only development platform for "real" developers. We did waterfall, we made a butt load of .dlls, and we liked it. IT in Nashville has changed. Join our distinguished panel of developers to discuss things that have changed for the better, and current trends that just aren't working.
I love using, developing and (where I can) contributing to open source software. What about you? It has changed my entire outlook on life, the universe and everything. Okay, maybe not that far, but I believe it has changed the world and working with it has certainly made me a better developer. I believe we are only seeing the tip of the iceberg. It has grown to more than just software. Health, science, and geological industries, just to name a few, are all benefiting from the open source movement.
This will be a panel discussion about the triumphs and hazards of being a female developer in a male-dominated industry.
- What happens when you introduce feeks to the geek cave?
- What are the problems you have to overcome as a female manager of an all-male dev team?
- How can you grow and earn respect if you're not let into the cave?
- Why are women pushed by the tech industry into social media versus more advanced roles?
"Make it Pretty." When many people think about User Experience, typically the first thing they consider is the visual design. While that is a part of the experience, to reduce UX to being equal with visual design sells UX very short. Other aspects include performance, interaction design, and overall, meeting user expectations for how an app or site should work.
The good news: You finally browbeat everyone on your team into adopting best practices.
The bad news: It may or may not be making a difference. I mean, how can you even tell?