When you are learning IL you might wonder why some directives even exists. They can do a lot of harm when used incorrectly. I’ll shed some light about one of them. Let’s check .emitbyte Read More
I deal a lot with communities. It started very early. As a teenager I was promoted to a moderator function on one of the online forums – binboy.org (anyone recognizes the name?). Currently I deal with online community (dotnetomaniak.pl) as well as online/offline – http://wrocnet.org. As I wanted to learn more and more about communities I turn my attention to books as the source of new knowledge. This post is my review of the book entitled “Buzzing Communities“.
For the last two days I was attending the .NET Developers Poland conference in Warsaw. It was my first time at this conference (I was there as a media patronage from dotnetomaniak.pl) and due to the fact that this year I’ve attend a lot of different sort of conferences (considering my usual average of 1/yr) I’ve decided to write short review about it. So here are the session I’ve attended Read More
The very first dev-warsztaty in Wrocław are over. Time to do some post-mortem analysis :). There a few lessons learnt (at least for me) from it.
There’s a little story that goes like this…
This is a little story about four people named Everybody, Somebody, Anybody, and Nobody.
There was an important job to be done and Everybody was sure that Somebody would do it.
Anybody could have done it, but Nobody did it.
Somebody got angry about that because it was Everybody’s job.
Everybody thought that Anybody could do it, but Nobody realized that Everybody wouldn’t do it.
It ended up that Everybody blamed Somebody when Nobody did what Anybody could have done
And this describes very well quite a lot of situations. And it can be very well used for describing what happened this week before the very first devWarsztaty in Wrocław. It’s about a hotel. Everybody was sure that somebody would do book a room and of course nobody did :). Good that we found out this soon enough that there was still the time to book a decent place for Konrad to stay. I think the reason for this was that there was no clear owner for this task and the responsibility just was blurry.
Always be sure that a task has a clear owner.
Also be prepared that people will RSVPed ‘No’ at the very late point. I mean very late. Our workshop was scheduled to start at 9 a.m. and we got a ‘No’ RSVP at 12.20 a.m. And as always 4 people didn’t show up at all.
People will cancel. Even at the latest moment.
Can can be prepare for every problem than you think may arise and still something unexpected will happen. Today, I think we were quite prepared but unfortunately the MS symbol server was serving us timeouts all the time. We needed to distribute symbols via pendrives or download them from google drive. Honestly MS could do better when we do host our workshop 🙂
There will be problems no matter how well you will be prepared. Don’t worry and deal with them one by one.
I’m quite happy about this first workshop. Few things we need to fix. Stay tuned for the next workshops.
Tomorrow is a very special day. Tomorrow we start something new in Wrocław. What would that be? Read on.
I don’t like to write about conferences. The opinions about them are highly subjective and they are valid for a very short time. I also don’t like to write my opinions about the sessions (in some rare cases I do write them anyway). And yet here I’m writing about #programistok 2016. Why?
A few posts back I wrote about an Application Insights, Azure based solution for tracking application data. Yesterday I realised it has a feature that I wanted to use it even more. I think you will want to use it too. Read More
Did you ever wondered what it would be like if you are not limited to static Main(string[] args) as your entrypoint? Did you ever wanted more freedom over where your app starts? Actually you can have that.
Read More
Did you ever needed to modify the source code to return some value for the testing purpose? Or you needed to alter the code as so to stimulate some flow? If your answer is yes then I guess you also forgot (from time to time) to revert your change back and such temporary fix went into to repository. If you want to prevent those keep reading
Everyone knows how to enhance Visual Studio’s debugging experience by applying DebuggerDisplay attribute (in polish). If not – read Piotr’s post here. That’s debugging 101. Here’s how to improve your experience even more. Read More