How do you sell to the company management to send developers to user conferences? For now, lets just assume we'd opt for in-country conferences as a start.
closed as not constructive by Walter, Yannis Rizos♦ Mar 7 '12 at 17:15
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or specific expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, see the FAQ for guidance.
|
If your boss does not understand how important these conferences are (and I think they are more important for keeping devs up-to-date than any tutorial or a book) and you need to "sell" the idea, maybe it's time to move on. |
|||||||||||||||||||
|
|
First thing to do is actually ask. There is a huge number of people just afraid to even ask something to their boss. In many case, if what you ask is reasonable, you will get it. It works for salary increase, new computer, day off, etc. You have much more influence than you think. Like I explain in this answer, your boss must see the value in it for him. If your boss wants you to be more productive, you will have to prove it will make your more productive. If your boss obsession is to make you happy in your work life, you will have to prove it it will be the case.
As I said, the simple fact to ask is enough in most case. |
|||||||
|
|
Every developer should have a more experienced person as their daily mentor to inspire them and show them the way to become better. For senior developers this is frequently not possible, and then conferences come in as a cheap substitute, because the speakers ARE the senior developer mentors. |
|||
|
|
|
The best development happens when the developer is the user. Being your own user is just about the best way to make sure you working on the things that matter and that you give priority to fixing even relatively minor annoyances. That's not always possible, naturally. And so the next best thing is to educate the developer on the user's perspective. Conferences are one way of going this. If I were to pitch such an idea to my manager, I would definitely focus the above angle. |
|||
|
|
|
When developing, i found out the hard way that generally when a client speacks about what he/she needs, it uses terms that generally are quite ambiguos. This could be because they are repeating something they sow or they cant express their ideas just because they dont really know what they need. Keeping up with the latests tecnology and computer science progress opens up our minds and increase the toolkit when dealing with complex clients, and giving the best up to date response. |
|||
|
|
|
There's a bigger picture here: there seems to be an idea firmly established in OOP and XP (and "agile" generally) that the more your design, coders and code itself uses the language of the problem domain (ie the language and concepts of your end users), the more chance of project success because of better communication and mutual understanding between developers and customers. If your organization buys in to that fundamental principle, then going to user-domain conferences is a very natural corollary. As is sending developers to observe users using your (and competitors') products "in the field", getting basic and intermediate-level training courses in the problem domain run in-house for all developers and just generally giving learning in the problem domain field parity with "coder skills" learning. Doesn't need to be the biggest and best user-sphere conference you go to (these are generally very expensive, and overwhelming as a first exposure to the user's world). Keep a look out for local symposium/workshop/seminar/lecture type events of your user's professional organizations and build some basic knowledge first. |
|||
|
|
