.NET Conf 2020.

Here are some notes on the Microsoft .NET Conf.

Here the link of the event: https://focus.dotnetconf.net/

Here the full list of youtube videos: 

youtube videos on .net conf

Some microservices tutorials:

https://dotnet.microsoft.com/learn/aspnet/microservice-tutorial/intro

ref for videos: 

https://www.youtube.com/playlist?list=PLdo4fOcmZ0oUc2ShrReCS7KoBbPEONE0p

on iA as a developer and the some cool tools.

I started this year as a software developper for Morneau Shepell. Good company with some flaws like everywhere but with a good work environnement.

Now after 5 months as a software dev for Industrielle Alliance I realize that not everything that shines is gold. Good things in this new position but also many small details that I do not necessarily like.

I had to understand how this teams uses Kanban and agile with a team who is still working on his mission** and the scope of their tasks.


**

Anyways here some cool features:



- Azure DevOps: This is of course the widely used tool for agile teams with Microsoft.

- Microsoft Whiteboard. I like this tool, very creative.

- Classic Teams, Microsoft Teams. I say classic with reserve cause Teams is a recent tool added to the office Microsoft toolbox.

- Workday. Great RH tool, user friendly.

There are a few more tools  but these were the ones I got more use of in my daily tasks.


And here some Agile notes that got me thinking on a certain point.

asp.net web API & simple data-driven CRUD microservice

here some interesting articles on .net to create a web API and a CRUD microservice,

just to keep updated my knowledge on current trends and technologies.

Get Started with ASP.NET Web API 2 (C#)

https://docs.microsoft.com/en-us/aspnet/web-api/overview/getting-started-with-aspnet-web-api/tutorial-your-first-web-api

Creating a simple data-driven CRUD microservice

https://docs.microsoft.com/en-us/dotnet/architecture/microservices/multi-container-microservice-net-applications/data-driven-crud-microservice

I found today a list of things that might hit programming productivity. I liked the list and even though that is a not a fully analyzed and formal study on how these things happen, I agree with them to a certain extent and seems to be a pretty good observation of the environment that we as developers, experience.

Here:

The 15 worst ways to kill programming productivity

Meetings, know-nothing managers, productivity metrics -- here's what's threatening to slay the next generation of great software

By Peter Wayner, Contributing Editor, InfoWorld | Nov 25, 2013

 1. Meetings.

 3. Trying to measure productivity.

 4. Prima donna developers.

 5. fix it later aka "technical debt".

 6. Nonprogrammer managers.

 7. Programmer managers.

 8. Macho programmers.

 9. Selfish  or cowboy coders.

10. Poor documentation.

11. Slavish devotion to documentation.

12. Distraction-rich environment. 

13. Cultural fit. 

14. Clinging to legacy tech.

15. Lust for the latest and greatest.