Richard Wysocki

Today's activities: One-on-Ones Part 3 https://www.manager-tools.com/2005/07/the-single-most-effective-management-tool-part-3 After Employee, you talk about whatever you want.   Shouldn’t/doesn't just talk about Work.  That is fine too but not a requirement. This is a meeting about how you and I working well together. This can be about you asking for a raise, another job, how to get better.  Talk about what you want to talk about. Don’t make them feel like this is JUST a meeting about work.   What is the Future Piece… Where do you see yourself in 1 year. Doesn’t have to be completely private.

Today's activities: One-on-Ones Part 2 https://www.manager-tools.com/2005/07/the-single-most-effective-management-tool-part-2 One of the Most or the Most Important meeting per week Always keep it that week.  Can move it up. Most likely to cancel/get off of topic appears to be Monday mornings. Always start your One on One with the same question i.e. How’s it going…, The floor is yours… Turning it to them first.. You will get to what is important for them. Building open relationship to get them to bring up topics Don’t cut them off.  You might need to work on getting them to 10-10-10 but if they talk for a long period of time, it’s because they want to tell you stuff 10 for them, 10 for you, 10 for future The first 10 minutes is for them.  They get to talk about what is important to THEM.  It can be about anything they want. – About work or outside….

Are you someone that wants to Grow, Learn, Share and Improve.  I do try...  Everyday or everyday is a great opportunity to improve. I might use my blog as more of a list of activities I'm doing but I'll attempt to push that forward into how you can grow, learn, share and improve yourself. --------- Today's activities: Manager Tools:  One-On-Ones Part 1 https://www.manager-tools.com/2005/07/the-single-most-effective-management-tool-part-1 Talk at least once a week 30 minutes (10 minutes - them, 10 minutes - you, 10 minutes - future) Know each individual  Don't throw them a vague question  Have individual go first Primary focus is about the Individual/Team Member  Scheduling is very important.  OK, if need to move it but it must be Done Should be done weekly.  Monthly doesn't do it because you forget and doesn't show you care. Going to event:  Philly.net Azure event

Really nice sample I found on the web that Explains the Given-When-Then Syntax style. The Given When Then style correlates closely to the Arrange Act Assert style for unit testing. Here's an example: [Test] public void RotateAngle_Given27Degress_Returns64Degrees() { //Arrange or Given var someAngleClass = new Angle(); //Act or When var result = someAngleClass.Rotate(27); //Assert or Then Assert.That(result, Is.EqualTo(64)); } Thanks:  http://stackoverflow.com/users/445105/joseph

ReSharper Succinctly By Peter Shaw This overview is not intended to replace the ReSharper Succinctly Series at all.  These were my personal Highlights of the book.  I recommend that everyone fully read the full book to experience and get these personal highlights from the eBook.  Thank you to Succinctly and Peter Shaw for putting this together.  This is first eBook that explains what ReSharper is vs. just saying you should have it.  It still really is a TON of memorization of all of the key combinations.  Its important to just learn them!! Resharper -> R# Recommend to keep on Show tips on Startup (if disabled, Listed under ReSharper Options: Environment -> General Tab) R#'s Action Bar:  Way of showing you the points in your source code that it believes needs your attention.  Action Bar is listed to the left of your Editor Window.  It will show small icons. R#'s Marker Bar:  Shows Colored dashes that sh...

 Probably can't show too much from this Pluralsight course but check it out before you write any emails.  Great course to get you in the right mood to send emails.  Responsive HTML Email Design http://app.pluralsight.com/courses/responsive-html-email-design By Justine Jordan and Jason Rodriguez Slides / Worksheets http://litmus.com/lp/frontendmasters https://litmus.com/builder/5320ab5 - Completed Design https://www.campaignmonitor.com/css/

The Clean Coder A Code of Conduct for Professional Programmers I hope I don't get in trouble for posting my notes as I recommend all developers to read The Clean Coder book.  These are just some of MY personal highlights from the book.  I'm sure you will get a lot out of it reading it for yourself vs. my notes.  I wrote this up so I can read over this daily and keep focusing on what I enjoy about coding and enjoying my profession.   Author:   Robert C Martin (Uncle Bob)     First Rule:   Do no harm QA should find nothing Test, Test, Test Every Line of Code should be tested! Design your solution to be easily tested Best way is to Write Tests first – i.e. TDD (Test Driven Development) Merciless refactoring:   Always check in a module cleaner than when you checked it out. Why do most developers fear to make continuous changes to their code:   They are afraid to break it.   Why, t...