GET What I learned from C # /. Net developers at Go # conference / GeekFamily's blog / Sudo Null IT News FREE

I myself am a C # developer and did the conference for the number one time. I'll tell you how I filled the cones and got a lot of pleasance.

This is the GoSharpMoscow C # Developer Personal Effectiveness League.
She went on Saturday November 15th. IT was my "front pancake chunky" operating theatre, as they say abroad, MVP (Minimum Workable Intersection). I report what I managed to do:

• fill the room 100%
• make the conference reusable for 95% of participants
• meet the expectations of 70% of participants.

But the most valuable thing I standard from the conference was the feedback. In practice, IT was a TDD with initialize and networking experiments. Now our team knows what the participants like and what are the bottlenecks in organizing the conference.

A bit of history and introduction

For those who get a line around Go # for the first metre, a small introduction.

I am developing in C #. I old to work on order, then remotely in a western company, and immediately I am writing for my projects. I always wanted to public lecture with colleagues, but I was lost by the yearn reports, the lack of mechanics for meeting people and the price of events. I wanted to go to a conference to broaden my horizons and communicating, sol I was ready to give only a small amount of money. The theme of ​​the conference and the description of the format I presented earlier on Habré here .

The preparation of the conference took three months and began with the choice of position and the invitation of speakers. Many people supported me when there was null but an idea. And I am very thankful to them for such backup. Time passed, the program evolved.
The concept was this: one track, short reports, a lot of communication and an affordable price.

The first day of Go # loomed like this: these are topics of personal effectivity, tools for writing code, mobile development UI and a developer's career. It turned out 10 reports and 15 speakers / experts. In that respect are more speakers since ii reports are paired and there are still experts for discussion in sections. Many saw the conference announcements (from DevExpress , TCS Bank and Luxoft ).

And and so, together with VioletTape and a enceinte team, and with the help of industry colleagues (@ 23derevo with DotNext , sidristij with CLRium), we managed to hold so much an event.

Satisfaction Statistics

I'll start with a pleasant one. 370 participants came. This is the physical bound of the site and each additional chair had to be obtained with a fight.

Already during the very day of the conference, we began to receive feedback from friends and whom we invited in person. Merely after the consequence, we equanimous questionnaires and rating reports. Another part of the feedback we conventional in correspondence with the participants subsequently the conference. Here is what we learned.

The conference was useful for 96% (and useless for 4%). 15% knowing "a lot of definitely usable things", for 43% it was "quite useful", 37% found something useful for themselves. Developers at the beginning of their careers and those World Health Organization rested connected vocation ceilings and thought about changing course got the most benefit. At the same time, 26% expected more, but for 74%, the impressions of the conference met expectations or exceeded them.

Oral polls and survey results revealed a surprise. The most functional section was "Career .Net Developer" , although during registration, participants were mainly interested in "Effective Code Writing".

What 70% say - satisfied participants

Just to quote a few:

• "The program is excellent, quite rich."
• "A good equalise of reports between technology and ethnical."
• "I liked the format itself - no need to run across and split, trying to catch all the gripping reports. Badge tagging is as wel a good idea. Recovered, I likable the food. "
• "I liked the teemingness and diversity of information, the informal atmosphere, the relevance of those covered at the group discussion. I can lonesome advise you to continue in the same mineral vein. "
• "I likable the theme of the conference. Liked the tags. I liked the informal atmosphere. "
• "I am a novice developer. Accordingly, I did not lie with often. Attending the league, I received a large amount of new information, which is to be processed in person past myself and to increase the volume of knowledge. "
• "All likable it. If the format does not change, I will continue to see "

So, everything is fine here, so let's move back on.

Who wants to know immediately what to expect soon on the December 12th team loss leader's day ( program and registration ) and what are our following plans for 2015 narrow-topic conferences (Asp.Net, Desktop / Business applications, C # Highload, Backend &adenylic acid; API, C # Clean Cipher) , click on the links and scroll to the end of the article.

And then there will be a small debriefing.

Critique - where we missed

30% expected more from the conference. Only this part of the participants taught U.S.A a lot. Some tips and tricks are know-how. Therefore, I will not conduct them Hera :). Realizing their wishes is many an hours and days of work.

Just share negative and directional reviews:

• "The speakers did non have time to delve into the topic, and gave only if general info."
• "Less general words, more specifics. Rough speaking, I already knew about the fact that CodeRush (reSharper, etc.) exists, I would suchlike to see how they make, to see the most interesting chips live. About AOP and PostSharp, you could generally allocate 2-3 times more fourth dimension, the subject is rather complicated, and once more, likewise the example from the postsharp.com main page, I would like to see more code. In general, to realize the direction of further development, Eastern Samoa a developer, information technology was a wonderful league. "
• "1. A lot of advertising bullshit in the section on fast code writing.
  2. The third region (approximately Hour) was the most informative and useful.
  3. In ecumenical, DevExpress ran into ads. "
• "Too much dealing information from JetBrains and DevExpress. As for the direct development, grammatical construction of architecture, surgery interesting cases - on that point was little information. "

It was really difficult for us to go bad a draw of technical inwardness in a short time of reports. 30% is the format overhead, but 70% is barely a blemish. In preparation, we gathered a batch of useful information from experts connected productivity tips, but did not submit it in the most eatable conformation.

The conference was held without sponsors and we merely did not control that DevExpress and JetBrains in the early section went into marketing! As the participants told America, it was necessity to make live coding obligatory. This was practicable by the corresponding DevExpress, but in the mobile development segment. What to do, participants allege:

"I liked the loaded show of work, additionally to presentations - an application for a mobile phone in 5 minutes :-) We need to put in standardized moments to other speakers, they truly push us to do it myself."

Format and length of reports

2/3 of the audience liked the short reports, but 1/3 would like the reports to be longer:

• "The duration of the report was best, in general, the conference did not fatigue, although it lasted a whole day."
• "Convenient format, everything is perceived without wear."
• "The format of the conference is superior, it may take a little yearner for the subject area reports."

Technical presentations need more time. To bosom the technical "meat" in 15 minutes is a challenge for the speaker. We tried to avoid lengthy presentations, as this would hit the full general public utility company of time for a fanlike audience. But for a to a greater extent consistent audience, we can allow long reports. And if you deman several hours for a deep study of the topic, you can take it tabu to the preparation, when 2-3 speakers spend one day.

Conclusions on the length and social system of reports:

1. Make the report clip circumscribe spinnbar. Technical reports should be given more time (30 minutes) compared with review reports (10-15 minutes).
2. At the end of for each one write up is a section with recommendations.
3. Required live coding for reports about tools.

Organization of discussions

We atomic number 75-complex our discussion preparation litigate, and because of this, it was Sir Thomas More difficult for us to process the content. We collected the answers in school tex form, then to assemble a presentation from them. And you just had to collect the slides right away.

The opinion of experts in the treatment on represent was difficult to perceive exclusive by ear. As an idea for the future - include a miniskirt-demonstration from an expert on 2-3 slides when he begins to speak for the first time. And then in that location will be a visual image of what he wanted to say.

We should likewise collect questions for the speakers via Chirrup broadcast (you can see here , tag # goshap14). The circularise had to be not just announced at the beginning of the day, but also periodically displayed on the block out.

Tags, plates and networking

The previously announced estimation with tablets worked 20%. And the tags are unexpectedly 100% - everyone liked it.

• "Badge tags are a great theme.
  "The tables along the tables are abstractly interesting, but it can solitary mold if thither are 2-3 times more places at the tables than there are masses willing to."
• "The idea with the tables is excellent, but you had to deliver lunch separately and you needed more tables."
• "Information technology's really great to go to a table with the engineering science you are interested in, find like-minded people close to it, and speak the same speech"
  

For example, when asked about networking, one participant writes:

"I likeable sticking the" PHP "tag onto a friend's badge :) Seriously, organizing tables for informal communicating is a selfsame exact idea, but they should own been usurped out of the intellectual nourishment zone and the interview-answer session in some places more stimulating than the reports themselves."

Nutrition

The most difficult matter was to balance the amount of food for thought, feed rate and cost. We had time with coffee and drinks, but with luncheon it turned out like this:

• "The Feast of the Vegan was all displeased. On the other hand the food successful more than than. Coffee is the best I've well-tried in my living. Now I spit on the worker :) "
• "The render points were clearly not enough, specially during lunchtime."

Other problems

The hardest part is Exceptions. The cartridge has run out, the printer has broken, etc. We uncovered the accounting "bug": accounting companies do not like when an individual entrepreneur is without a cachet and makes a mark along the business spark off as a receiving party only with a signature tune. What other? For instance:

• League branding: didn't answer rollups and set back logs in the tea break
• TK for the photographer: speakers were not distant against the screen backgroun of the hearing
• pricing policy: a big col between early and deep price
• contests: underestimated the complexity of accounting and debriefing.

What's next

We centerin on creating measure for the middle class of developers, team leaders and managers, rather than top developers (but more demanding and clarifying feedback). The product we want to develop is inexpensive and patronise professional communicating.

In 2015, we will make narrow-topic conferences (Asp.Net income, Desktop / Line of work applications, C # Highload, Backend &A; API, C # Clean Codification).
If you are curious in social activities and make a sentence budget, we invite you to join. About the benefits (free tickets and meals, talent licenses, etc.) to be a report applicant, speaker and team member - here .

Team up leader day December 12, Fri

The next effect of 2014 is a team leader day .

If you are a leader (team loss leader in C # or a project manager) or plan to become one, past this is the best measure for immersing yourself in context and monitoring trends in development direction.

You will find out 4 reports happening computer architecture, 3 reports on ALM and TFS, 2 reports on root code management without TFS and DevOps tools. And also - 2 reports connected specialization of labor in .Net teams. Namely, how decisions are made about group people into teams and dividing tasks between them.

Initialize - unrivalled track, 10 reports, many breaks, earlier ending and Afterparty.

Tulskaya metro sounds far away, but acquiring to it is very convenient (only 3 metro stations from the very center of Moscow and 4 minutes on foot). We adjusted the schedule and format supported the feedback of the firstborn daylight. And you will find good nutrition (link). Lunch and Afterparty wish be held in the OM cafe, so you fundament chat while sitting in comfortable chairs.

The course of study and registration are here .

// If I took someone's remark from readers in an article, you can write out to me, I will pass you.

DOWNLOAD HERE

GET What I learned from C # /. Net developers at Go # conference / GeekFamily's blog / Sudo Null IT News FREE

Posted by: rollinsnowlielinuld81.blogspot.com

Share this post