up-skilling software engineers

Photo by Julia M Cameron on Pexels.com
Photo by Julia M Cameron on Pexels.com
 

When you asked the leaders in any software companies about delivering great and innovative products, they'll tell you that they are working hard to bring in talented software engineers, and providing them with all the tools required to deliver such products.

We need talented software engineers because

  1. They have the capacity and ability to learn. It may be attending some conferences to understand the latest trends and technologies. It may also be spending some time to hack. Hacking (or trying new things) brings new perspectives to software development.
  2. They are innovative. Usually, this involves looking at things at different angles (or even turn the world upside down - an impressive talk by Cafer Tosun, Senior Vice President of SAP), and provide intelligent solutions.
  3. They understand the limitations and opportunities. Most of the time, there are important decisions to be made, and they are able to provide detailed information on what works and what not. And, they also view limitations as opportunities. There are limitations because nobody have good solutions yet, hence they like to tackle them.

With over 25 years of professional software development experience, I conclude that writing code is the easiest things to do. It is not hard once the coding environment and test frameworks are setup. The most difficult part is to understand the problem domains and provide elegant solutions. These solutions translate to software design, architecture and implementations.

Unlearn, relearn, rethinking, reimaginating, innovating and growth mindset are important to the survive of any software companies. One of the biggest mistakes that software companies made is NOT (or unable) to invest in up-skilling. They want to bring in talented software engineers, and they should also provide time for up-skilling.

I believe that FANNG provide their employees time to hack and learn new things. Unfortunately, for some companies, software engineers are always on tight schedules hence do not have time for hacking. I believe that there are crunch time, and there should be time for engineers to pick up new skills.

I am fortunate to be with Microsoft. I am given time to hack in between projects. My organization also provides materials for hacking, and there are continuous efforts to create new contents. These contents are basically challenges. We tackle one challenge at a time until we complete the entire hack. A new employee (like myself) can work on these hacks for up-skilling.

It is important to provide time for software engineers to try new things. The talented engineers love challenges and opportunities to hack. Companies are likely to lose these engineers if they are not challenged, and they move on to another companies to acquire new skills.



Comments

Post a Comment

Popular posts from this blog

OpenAI: Functions Feature in 2023-07-01-preview API version

Image
  Image from https://www.pexels.com/@pavel-danilyuk/ One of the cool features of OpenAI version 2023-07-01 is its custom Functions feature. This feature is close to me because I am working on a project where we require OpenAI to generate JSON responses. We always want the generated JSON to be consistent, otherwise, we need to do some post-processing tasks to get the JSON object in the correct schema. In the blog, we observe the completion with and without this new feature. Development Setup python -m venv .venv poetry init poetry shell poetry add openai poetry add python-dotenv poetry add pydantic I am using Python version 3.11 Create .env file OPENAI_API_TYPE="azure" OPENAI_API_BASE="<OpenAI endpoint>" OPENAI_API_KEY="<OpenAI secret>" OPENAI_API_VERSION="2023-07-01-preview" OPENAI_DEPLOYMENT_ID="<deployment identifier>" Without OpenAI functions feature We use two sample texts for experimentation. We want to get the na
Read more

Storing embedding in Azure Database for PostgreSQL

Image
  Image from https://www.pexels.com/@tara-winstead/ There are many options to store text embeddings. In this blog, we shall look at storing embedding in Azure Database for PostgreSQL. Installing Azure Database for PostgreSQL Install Azure Database for PostgreSQL Flexible Server.  Once it is deployed, enable two extensions. Install Python modules python -m venv .venv poetry init poetry shell poetry add openai[datalib] poetry add python-dotenv poetry add psycopg2-binary My Python version is 3.10. Create .env OPENAI_API_TYPE="azure" OPENAI_API_BASE="<HTTP endpoint to Azure OpenAI Service>" OPENAI_API_KEY="<secret to Azure OpenAI Service>" OPENAI_API_VERSION="2023-05-15" TEXT_MODEL="<deployment id of text embedding model>" PGHOST="<my-service>.postgres.database.azure.com" PGUSER="<user name>" PGPASSWORD="<secret>" PGPORT="5432" PGDATABASE="< database name
Read more

Happy New Year, 2024 from DALL-E

Image
generated by DALL-E Wishing everyone a happy new year. Year 2023 is great for me because I learned much about OpenAI. I am involved in a live deployment with it, and involved in a handful of interesting user scenarios around it. On top of this, a copilot hackathon. The image above is generated by DALL-E and following is the code. 1. Dependencies python = "^3.10" pydantic-settings = "^2.1.0" openai = "^1.3.8" 2. Environment Parameters OPENAI_AZURE_ENDPOINT="<your azure openai endpoint>" AZURE_OPENAI_API_KEY="<your azure openai secret>" OPENAI_API_VERSION="2023-12-01-preview" OPENAI_DALLE_MODEL="dalle" Note: OPENAI_API_VERSION has to be 2023-12-01-preview otherwise you will get an exception openai.NotFoundError: Error code: 404 - {'error': {'code': '404', 'message': 'Resource not found'}} dalle  is the name of my dall-e-3 deployment model. You need to change it to
Read more