Tell the engineers what you need, what you like, what you don't like. Know who does what in the company, so you can email them directly with problems to get a quick answer. Talk to the developers writing your tool. For self employed developers, it may be good to present yourself and maybe someone will hire you in future. For example in a forum, or as contractor or employee. It is always good to have contacts to people which may at some day help you. Ask what they do, what they think about the news at the keynote and how they enjoy the conference. Simple rule: Try to talk to everyone a few minutes. And later on the conference ask all the questions you may have. You depend on our development tools and if something is going to change soon, you should know it first hand. This way you have more things to learn about.īe sure to visit the keynotes to learn what is new and coming soon. Try to pick sessions with new topics you are not familiar with or at least some which have a different view on something you know. If some sessions are recorded, go into the others who aren't. Don't go to topics where you know most already as that could be a waste of time. The title often doesn't tell whether this will be interesting or not. But for next year's FileMaker DevCon in Phoenix, I may get a flight to Los Angeles or Denver.)Īt the conference, go and visit a few sessions. (Last year's Xojo conference was in Austin. And even the accounting will not complain if I show them the cost for short stay (expensive) vs. With the savings on airfare, I can easily pay a few extra hotel nights. And Frankfurt Dallas would be a direct flight. Often it can be much cheaper to fly to another city, enjoy a few more days there and drive to the conference city.Īs far as I see my ticket price to Dallas is about half of the cost to flight to Austin. Stay at least a day before and after the conference to relax a bit, join any before/after activity with other attendees and enjoy a bit of sight seeing.Įspecially when I fly internationally I often need a day to do the work left on the desk while I was in the airplane. When you decide to visit a conference, please add a few extra days. Get a different point of view on your development workflow. Meet other people who may have the same problems and give you conceptions to solve them. A little bit travel may make a difference to your normal work week. So please use the conference as a chance to get out of office and meet others. Some have no colleagues to talk with or don't participate in the forums. Some developers have not much contacts to other developers. So lets think about reasons why you should go: Some developers love to go to conferences and others are skeptical whether the cost is worth it. Thoughts about visiting Conferences Recently I visited developers in Switzerland and we discussed visiting conferences. If you are interested, please contact us.
The contract defines rates and availability. On the month end, we send an invoice for development time. If you need help with using a plugin, your support requests gets priority and of course billed.
#Xojo pro priority support license
We would send license keys and invoice for initial purchase or when old keys expire. This gives you a subscription for the plugins you need.
#Xojo pro priority support software
Second, we can setup a software maintenance contract. This way you don't need to come back every year for a license update. So instead of going through specifications, offer, purchase order, invoice and license delivery, we can offer alternatives.įirst, you can order license with updates for several years included. For some organizations it can take a year between someone needing a license an the delivery of a license key! The bigger the organization the longer orders may take due to bureaucracy. If you need our plugins for a bigger organization, it may be difficult to order each license or consulting service on it's own. Software maintenance contract (Softwarewartungsvertrag)
0 kommentar(er)
