2014-11-14 Documentation for the module Azure in Python
I did find any documentation for the module azure-sdk-for-python so I generated it with Sphinx: azure-sdk-for-python (documentation).
2014-08-01 Un livre sur Javascript
Je suis tombé là-dessus aujourd'hui : Eloquent JavaScript. Pas mal du tout.
2014-06-30 Machine Learning with Python
Two very interesting blogs which illustrate how to do machine learning with Python:
I suggest the two following blog posts:
- Data Science in Python
- Using Python's sci-packages to prepare data for Machine Learning tasks and other data analyses
- Implementing simple sequential feature selection algorithms in Python
2013-07-29 Starting a coding projet
When I was young, I was writing code, running, fixing bugs and going on to something else to code. After I joined my first company, I realized many people were doing that. There were very different styles of coding, spaces anywhere, indentation not following a single rule and always some resistance to follow one set of rules. I started to work in a company with various cultures and styles. People usually write code following the style which is the clearest for them, the easiest to understand for them. I'm usually skeptical when somebody explains everybody should do this or this because it makes more sense. As a teacher, I saw too many different logics, each of them writing in their own style. And if you do different, it is because it is more simple that way for you. For example, I usually choose small variables name for a loop (n, i, t, u) because I read it as a mathematical loop (\sigma_{i=1}^n ...). I add a space before semicolon because you do this in French. One rule I follow is when I modify something written by somebody else: I try to follow the same style. I remember some code review which came back with many comments because my spaces were not good. I think there should be a tool for that.
Anyway, when you work on a big project, I'm not sure about the importance of the style but I know some tools and practice are unavoidables:
- unit tests: that should be the first thing you write,
- source repository: Git seemed to be one of the best choices,
- code review: they make it easy to share pieces of code (see ReviewBoard).
- automated help generation: it can be useful if it is started soon enough
|
Xavier Dupré
|
