peterbozso

SEEKING WORK | Europe | Remote

I am a freelance consultant, specialized in Microsoft technologies, especially the application development parts of Azure.

I help my customers by providing valuable technical and architectural guidance as well as hands-on help with the implementation of their projects targeting many different client-side technologies (React, ASP.NET Core, Microsoft Bot Framework) and the underlying infrastructure for all of them: Azure. I also support my customers transforming their software development process to follow Agile best practices by utilizing Azure DevOps.

LinkedIn: https://www.linkedin.com/in/peterbozso/

Blog: https://peterbozso.com/

GitHub: https://github.com/peterbozso

Location: Europe (UTC + 1) - other reasonable timezones work as well

Remote: yes, exclusively

Willing to relocate: no

Technologies: React, ASP.NET Core, Microsoft Bot Framework, Azure DevOps, Azure

Résumé/CV: https://1drv.ms/b/s!AtBCTTIe2cmFh8Am4ZN6-GYDRWN-Lg

Email: peter.bozso@outlook.com

Exactly this.

Ex-MS employee, Azure consultant here. I don't have any experience with AWS or GCP other than some very trivial, getting started stuff. But I really don't think what you say is true. While most of the stuff in Azure has a very familiar feel and intuitive interface (either on the UI or the API level) if you are coming from a MS background, there are still glaring exceptions and you certainly need experienced/certified people to build something that's ready for serious production usage. I agree though that Azure has a very nice and happy path for most enterprise cloud migration and hybrid cloud stories.

Absolutely! But that's another topic, namely "How much time should I wait after the release of a new version before updating?" :) That highly depends on the kind of software you are working on and the supplier of the given dependencies (trust/experience/ability and willingness to self-test new versions).

You get more benefits from updating your dependencies than "just" bugfixes. There can be performance improvements or security updates in new releases. If you have a proper CI/CD pipeline and test environment(s) in place, it shouldn't be too much work. (Of course it highly depends on your domain.) Then the benefits clearly outweight the extra effort.

I was in similar shoes as you. I even had my notes scattered all over the place, some on paper, some in different softwares. Now I use only OneNote both personally and professionally and I cannot be happier. It has a lot of features, which helps because I can keep every idea/info/todo in one place. It has apps for everything (except Linux, but the web app works great in that case), so I can access my data anywhere. I even had a client where we all used it and we were easily able to make it work like a wiki for that project. It might seem obvious, but what really helped me with keeping my notes organized (and my browser bookmarks too, because I have a ton of those as well) is revising them periodically, in my case weekly. If you do it frequently enough, then it's really just a couple of minutes of reorganizing each time and you can keep everything nice and tidy.

As a consultant I work almost exclusively with enterprise customers using Azure. When moving to the cloud for some of them the most regular reasons to keep stuff on-prem are:

* Regulation: it's mostly about data can't leave the given country's border. There's usually not much you can do about it. Offload stuff to the cloud what you can (computing), keep on-prem what you must (data). In these cases the integration between the two environments can be a real challenge sometimes. But Azure is quite strong on that front.

* Stupid company policies set up during the last century or recently, but by people stuck in the last century. In some cases these can either be worked around or changed if you know the right people. But there's a lot of cases when it's hopeless from the start. Totally depends on company culture.

Azure AD B2C https://azure.microsoft.com/en-us/services/active-directory-...

The Microsoft Bot Framework is a code-first bot creation tool: https://dev.botframework.com/ The learning curve is steeper than other similar solutions', because you actually need to write code, but if you are familiar with C# or JS, the possibilities are much wider than with the others. The official docs are pretty good, in the design section it also explains some base concepts of conversation design, not just how to use the SDK-s: https://docs.microsoft.com/en-us/azure/bot-service/bot-servi...

Same here. And actually you can make really nice money with it (maybe not top level engineer/manager, but certainly enough for a decent living), so it's not even entirely a matter of income. ;)

Most of the important points have already been raised by others (version control, CI/CD, etc.).

I would only like to recommend one specific tool, which you can integrate into your CI/CD pipeline: SonarCloud (https://sonarcloud.io/about)

The on-prem version is called SonarQube (https://www.sonarqube.org/) which you can easily host yourself if you need/want to, but the cloud version is dirt cheap.

This single tool can bring tremendous value into your work life, especially if you have a team full of junior/inexperienced people. It has saved me countless hours on different projects by providing actionable insights on their code bases.

Disclaimer: I have no ties to the company making SonarQube, I am just really thankful that this tool exists. :)

World of Warcraft. :)

FireChat: https://www.opengarden.com/firechat/ It's great for the communication scenario you described.

+1 for the Logitech.

These small, simple things are the reason why I truly love technology.

I wanted to write almost the exact same list. :) Such an awesome product, highly recommended!

PowerShell is also cross-platform now: https://github.com/powershell/powershell