I'm passionate about programming, I simply love it.
I like to learn and this industry
brings to me the opportunity to discover new amazing stuff almost every single day.
Constant learner on how to improve writing clean and reliable code.
That’s an easy career improvement goal to give oneself, but “become a kick-ass programmer” is not a simple goal. For one thing, saying, “I want to get better” assumes that you recognize what “better” looks like. Plus, too many people aim for improvement without any sense of how to get there.
Julie Zelenski gives an introduction to the course, recursion, algorithms, dynamic data structures, and data abstraction; she also introduced the significance of programming and gives her opinion of what makes 106B "great;" C++ is introduced, too.
In this module, we kick the course off by looking at the bigger context within which we will be designing and engineering systems in the 21st century.
Writing code is easy. Writing good quality code is an entirely different story. How can we measure the quality of design? How do we know we're doing the right set of things that will lead us to a better design? In this session, we will learn about some core software design principles that help programmers every day. Instead of talking about theory and what we could potentially do, we will take on multiple examples, discuss the solution, pros and cons, and bring out key design principles that have an impact on the outcome.
Dealing with data into Object-Oriented environment
Robert C. Martin explains in his own unique style why professionalism is so important for software development teams and their managers. This event has been recorded live at an event co-hosted by Agile Quebec City and Elapse Technologies in Septembre 2012.
When trying to find a simile that I can use as an example, I thought about a ship's structure used for\n damage control purposes to increase stability. Floodability is reduced by dividing the volume of the\n hull into watertight compartments with decks and bulkheads.
If a ship's hull is divided into watertight compartments, any flooding resulting from a breach of the\n hull can be contained in the compartments where the flooding occurs, avoiding the disaster.
\n Obviously, this is a good measure but isn't enough with that alone, we always must take care about everything.
\n Remember Titanic, folks
MIT 6.006, Fall 2011 This course provides an introduction to mathematical modeling of computational problems. It covers the common algorithms, algorithmic paradigms, and data structures used to solve these problems. The course emphasizes the relationship between algorithms and programming and introduces basic performance measures and analysis techniques for these problems.