marți, 15 noiembrie 2011

tECHNORATI DIN NOU

Leave a Comment
38U4YMAGKC4Y
Read More...

Adopting a tool

1 comment
Introducing a tool in an organization of software developers is not an easy thing.You need money, you need a detailed plan, but overall you need to see the new tool working and producing for your organization.

Get a sponsor or support from all shareholders!
So before announcing the change, get the support of the shareholders in your organization. 
Not all of them are fans of changes, so try to have a sponsor with enough influence to make this change happen. I dont know if the guy should be the big boss, the most respected technical guy, a manager just promoted in a new position eager to change things. Decide for your self.
But don't start without enough support from shareholders.

Get some profit!
Nothing works without a profit.
A new tools should bring with it some profit, either financial or in quality. No tool will be adopted if the costs for adoption are extremely high. The financial controller is constantly looking to figures, if you don't. No tool adoption should have as a result a red bottom line.
If the costs of work are higher, than it should result at least an improvement of the quality.

Ensure a nice journey
Every new tools involves an effort of learning. It's not possible to learn it over night, even Steve Jobs would demand so.
Invest in trainings and track the progress in know-how improvement. A good plan is not enough if you are not following it.
Sometimes the tool is not enough.People need practice, sometimes in a controlled environment where they are allowed to fail big time. Make this possible. Programmers need a sandbox to improve their skills, to make happen their learning curve.
Practice together with your team and note down the feedback. Don't overreact when the new shiny tool is not perceived the same as you do.


Make the tool loveable!
People genuinely have different interests, hobbies, tastes. They are different. And they have to use the same approach. Even more, programmers are geeks and they like their own tool. Not necessary their own implementation, but
Before going to announce the change in the organization, you have to know what is the general mood. For instance, if you have very creative people, oriented to fashionable tools, please think a detailed approach about how to introduce a tool with a dusty interface.
If this is possible, let them propose the tool. You, as a manager, just define the main constraints, the objective that you need to reach with this new tool. Team will solve the problem and they will adopt easier the tool.
Doing this definition of the constraints, you need to be sure that you understand the needs. Double check with team members if the new way of doing things is solving the problem or is just changing the layout of activities.
Having this done, create the urge of adoption. Evangelize the benefits of changing the tool and underline hard the disadvantages in current situation. Get as many supporters as possible.
People don't necessary love what they understand, but what is having a decent degree of charisma. Take iPhone and tell me what is understandable in the effect iPhone generated in sales. It's more about what the user feels. Remember, we are speaking here about a tool. Tools needs nowadays charisma.
Read More...

miercuri, 9 noiembrie 2011

iPlan - planificare strategica de business

Leave a Comment
M-am inscris in programul iPlan, menit sa imbunatateasca comportamentele de planificare strategica.
Impresia pe care o am pana acum este excelenta si va recomand celor interesati sa va inscrieti.
Chestionarele folosite si feedback-ul pe care l-am primit pana acum sunt foarte "profi" si se bazeaza pe instrumente recunoscute (Strategic driver, Markstrat). Puteti gasi descrierea programului aici.

Va recomand sa va inscrieti. Puteti afla lucruri foarte interesante.
Este organizat de The Network, o firma de consultanta in management si marketing care aduna manageri romani experimentati.

Proiectul isi propune sa ofere instrumentul de diagnoza catre 3300 de manageri romani, iar cca 1000 dintre ei vor participa la 2 zile de seminar. Totul este gratuit, prin finantarea Uniunii Europene. Pentru mine, proiectul este unul care arata cum ar trebui cheltuiti bani europeni cu folos pentru Romania. Voi reveni cu impresii dupa intoarcerea de la seminar, in decembrie, chiar inainte de sarbatori.
Read More...

duminică, 6 noiembrie 2011

New adress of blog // Adresa noua a blogului

Leave a Comment
Hey, readers!
I am moving to a new domain.
WWW.CARTENOUA.COM.
Soon, a new logo and new posts.
Also, a short newsletter on weekly basis, if someone is interested. I will start only if I can get 15 interested persons.

Starting with Monday, 6th of November.


=============================================================================
Dragii mei,
Am achizitionat un nou domeniu pentru blogul meu.
WWW.CARTENOUA.COM
In curand, un nou logo si postari noi pe teme de programare si angajari.
Planuiesc si un newsletter saptamanal, daca voi aduna macar 15 adrese de email ale unor persoane interesate.


Incepand de luni, 6 noiembrie pe diversele ecrane (laptop, iPhone, iPad, smartphone).
Read More...

sâmbătă, 5 noiembrie 2011

Estimations (not agile)

Leave a Comment

Why are needed?
Simply because you also need a deadline from your builder when the house is finished. And for sure, you ask for a delivery date when you go to your tailor. Plus, you ask for a price. No deal is closed without a price indication and a delivery date.

Simple tricks to make it better:
1. Read down what you have to do
2. Understand it
3. Split it in pieces.
4. Write down the pieces and think how much would you spend for each.
4.a. You have do in it and can look back in the history. Put the figures there.
4.b. This is the first time you have to do this. Split it in more pieces and go back to step 4.
4.c You cannot escape from step 4.b. Use your intuition. How complicated does it seems?
                        Same other task : put the same effort as for that, plus the learning effort
                        Twice as complicated: twice the effort plus the learning effort.
                        Five time as complicated than what you did so far: ask for another task.
5. Think a little about risks: what can happen to prevent you for completing the task. Put some effort there (not for all risk you identify, only for half of the big ones).
If the risks are to high, ask for another task or tell this to manager.
6. Sum it up and see if you can reach the deadline.
If this is not possible, then see what is the delta missing: can you speed up and delivery in time or is basically impossible and should tell this to the guy who requested this.


Read More...

UML in embedded (I)

Leave a Comment
I say now a truism. Model based development will be the new quantum leap in software development in terms of productivity.
It surely takes more years to adopt UML in the development, but there is a clear path to this.

Some directions:
  • code generation (hard constraints) and documentation.
  • UML meta models are the basis of AUTOSAR standards. AUTOSAR is heavily supported by most of car manufacturers.
  • UML and re-use of software should be good friends.
  • Round trip engineering tools are more and more available for embedded and ease the re-use, as the design documents are more readable.
More post on this in the near future.
Read More...