DEV Community: Simon Rabuogi

Tough Times, Tough Men...

Simon Rabuogi — Tue, 29 Oct 2024 13:18:55 +0000

Hello Devs! I have a message for Junior Devs and those looking forward to joining Tech. This is meant to share my thoughts on the look of the current Tech Jobs industry and my projections within the next 5 YEARS.

A little about myself

I have been in Tech for some time now. I discovered my passion in Tech back in 2007. At about this time, Dad brought home a Personal computer, a Dell Optiplex (I can't remember the model) but it was running on Windows XP. I tried it and the rest is history... Don't take me very seriously though, as I haven't done so much with my life in tech since then :)

Artificial Intelligence

I am sure that I am not alone in this. Every dev has their fears with the current rise of AI in Software Engineering. My take is that AI is still not mature enough to write perfect code as would be defined in the prompts. Hence the need for an Engineer to shape the codebase as needed. I also feel like AI will replace some developers, (which should be yours to choose, whether to be sent home or stay in the game)

The Job Market

Right now, I feel like it is very hard to be hired in Tech and the situation is worsening. Lay-offs are rampant and tech companies are closing down. With these taking place, most job positions require mid-level to senior-level expertise. Junior devs are disadvantaged.

Skill Acquisition and Growth in Tech

Becoming a developer has become harder in recent years. There are millions of resources, both Videos and articles on the internet teaching Software development. Landing on the right one for your learning needs could be hell. You will end up jumping between resources before you find what works for you. I am sorry about this but I also had to deal with it. You are likely to learn and speak Hindu while trying to learn web development from your favorite YouTube channel. :)

As for those who are already in the industry, there is a problem. With AI in our Integrated Development Environment, we are likely to stop thinking. We will find it easy to just push the TAB button so that Copilot completes the rest of the code. Following this in most cases, would be to UNDO everything after the 10th round of debugging. On the web, ChatGPT also does all the thinking for us.

Good News

Here is one rule of nature that I believe in: Tough times will create tough men. Tough men will create an easy time. An easy time will then create weak men who create tough times.
Put this rule in a loop, before we continue.
Ever wondered how software engineers wrote code in pure Commandline Interfaces? At a time when even Notepad was luxurious. How did they debug?

I feel like Software engineers in this era had a lot of quality skills that we might never achieve today. Skills like mastering huge code syntax and scripts and then applying that to problem-solving and debugging are just but to mention. These were the tough days that created tough men.
These tough men worked tirelessly to change the situation for themselves.
Then came the beautiful modern IDEs, new and better programming languages, and frameworks. Artificial Intelligence is not forgotten. Doesn't this sound like an easy era?

Coding became easy and enjoyable with pleasing colors, code autocomplete, syntax highlighting, and error checks as well us several debugging features. The comfort that came with all these amazing features became the birth of the lazy devs. This generation of developers cannot even read and understand error logs. How can one become crafty around something they don't even understand?

This generation of lazy developers is going to create more problems in the software industry, a tough time. The solution here must be tough men. Developers who understand their craft. This becomes where serious junior developers will jump on the train. This will call for being more passionate about software development, understanding the basics, and upskilling to become good professionals.
Isn't this a good thing? Doesn't it bring some hope for young talents? Tell me what you think.

The Importance of Eye Care for Software Developers: Protecting Your Vision for Optimal Productivity

Simon Rabuogi — Fri, 12 May 2023 13:28:52 +0000

Health is wealth.

Intro()

In today's technology-driven world, software developers spend countless hours staring at computer screens, coding, debugging, and testing software applications. While the work is intellectually stimulating, it can take a toll on their eyes. Eye care is a crucial aspect of maintaining the long-term well-being of software developers. In this article, I will explore what eye care means for developers, why it is important, and how to incorporate it into your routine. Additionally, we will introduce "Gammy," one of my favorite eye care utility tool and suggest alternatives for different operating systems.

Understanding Eye Care for Developers

Eye care for software developers refers to a set of practices and precautions aimed at reducing eye strain, preventing eye-related discomfort, and preserving optimal vision. Continuous exposure to computer screens and artificial lighting can lead to a condition known as Computer Vision Syndrome (CVS) or Digital Eye Strain. Symptoms may include dry eyes, blurred vision, eye fatigue, headaches, and neck or shoulder pain. Prioritizing eye care can help minimize these issues and ensure developers can perform at their best.

The Importance of Eye Care

Reducing Eye Strain:
By following proper eye care practices, developers can minimize eye strain and discomfort. This, in turn, improves productivity and prevents potential long-term vision problems.
Preserving Vision:
Consistently staring at screens for prolonged periods may contribute to vision deterioration. Taking proactive steps to care for your eyes can help preserve your vision over time and avoid complications such as myopia (nearsightedness).
Promoting Overall Health:
Eye care is not only beneficial for vision but also contributes to your overall health and well-being. By practicing eye care, developers can minimize the risk of associated issues like headaches, fatigue, and musculoskeletal discomfort.

How to Incorporate Eye Care into Your Routine

Follow the 20-20-20 rule:
Every 20 minutes, take a 20-second break to focus on an object at least 20 feet away. This exercise helps relax the eye muscles and reduces eye strain.
Blink frequently:
Remind yourself to blink regularly (like you just did).. ;) to keep your eyes moist and prevent dryness.
Adjust screen settings:
Optimize your screen's brightness, contrast, and font size to reduce eye strain. Avoid excessive brightness or glare.
Maintain proper posture:
Sit at an appropriate distance from your screen, ensuring your eyes are level with the top of the monitor. Position the monitor to minimize glare and reflections.

Introducing Gammy: An Eye Care Utility Tool

Gammy is my favorite eye care utility tool designed to automatically adjust the brightness and temperature of your screen based on the ambient lighting conditions. It helps reduce eye strain and ensures a comfortable viewing experience. While Gammy is primarily available for Linux, there are alternative tools for other operating systems:

Linux Alternative: Redshift is a popular alternative to Gammy for Linux users. It adjusts the color temperature of the screen based on the time of day to reduce eye strain.

Windows Alternative: F.lux is a widely-used eye care tool for Windows. It adapts the color temperature of your screen to match the time of day and reduces blue light emissions.

Windows 10 & 11 have Night mode as an in-built functionality that could help with eye-care needs. Unfortunately, many developers I know don't even utilize it.

macOS Alternative: Night Shift is a built-in feature on macOS that adjusts the color temperature of your screen to a warmer tone, reducing blue light exposure during evening hours.

Finally()

As software developers, prioritizing eye care is essential to protect your vision, reduce eye strain, and maintain optimal productivity. By incorporating simple practices into your routine, such as taking regular breaks, adjusting screen settings, and following proper ergonomics, you can promote long-term eye health. Also utilize the already available tools like Gammy, f.lux, and the others to achieve the same goals.

The Crucial Role of Technical Writing for Software Engineers

Simon Rabuogi — Tue, 09 May 2023 08:30:10 +0000

Ever wondered what Technical writing is all about, Why it is even necessary, why you would look into it and such questions? If you ever asked yourself such questions, the read this article.

In the fast-paced world of software development, effective communication is essential. Technical writing serves as a bridge between software engineers and end-users, ensuring that complex technical concepts are conveyed in a clear and concise manner. In this article, I will explore what technical writing is, why it is important, and how software engineers can get started in this vital role.

What is Technical Writing?
Technical writing involves the creation of documentation, guides, tutorials, and other written materials that explain complex technical concepts to a non-technical audience. It encompasses a range of formats, including user manuals, API documentation, system requirements, release notes, and online help documentation. The goal of technical writing is to provide users with the knowledge and resources they need to effectively use a software product.

What Benefits come with learning Technical Writing?

Becoming a technical writer offers numerous benefits, including:

Communication Skills: Technical writing enhances your communication skills, allowing you to effectively convey complex technical information to a non-technical audience. This skill is valuable in various professional settings.
Career Opportunities: Technical writing opens up a range of career opportunities. You can work in software development companies, IT firms, technology consulting, or even freelance as a technical writer. (This has always been my dream) :)
Problem-Solving: Technical writing requires a deep understanding of technical concepts and their practical applications. This enhances your problem-solving abilities as you break down complex information into easily understandable pieces.
Collaboration: As a technical writer, you collaborate closely with software engineers and other professionals, fostering teamwork and collaboration. This interaction improves your understanding of software development processes and enhances your ability to work in cross-functional teams.
Knowledge Transfer: By documenting code, project insights, and best practices, you contribute to knowledge transfer within your organization. This ensures that critical information is preserved and can be accessed by current and future team members.
Personal Development: Technical writing promotes personal growth by honing your research skills, attention to detail, and organizational abilities. These skills are transferable and can be applied in various aspects of your life.
User Empowerment: Technical writers empower users by providing them with clear, concise, and user-friendly documentation. Users can better understand and utilize software products, resulting in enhanced user experience and reduced support requests.
Continuous Learning: Technical writing requires staying updated with the latest technologies, tools, and industry trends. This fosters a culture of continuous learning, enabling you to remain at the forefront of the ever-evolving software landscape.
Flexibility and Independence: Technical writing offers flexibility in terms of work arrangements. You can choose to work remotely, freelance, or even start your own technical writing business, providing independence and control over your career.
Professional Growth: As you gain experience and expertise in technical writing, you can take on more challenging projects, work on diverse software applications, and even progress into leadership roles within the technical writing field.

Importance of Technical Writing?

To Enhanced User Experience: Technical writing helps software engineers create user-centric documentation that empowers users to navigate and utilize software effectively. Clear instructions, concise explanations, and troubleshooting guides can significantly enhance the user experience and reduce support requests.
For Efficient Collaboration: Technical writing serves as a means of effective communication within development teams. Documentation allows engineers to share knowledge, methodologies, and best practices, improving collaboration, and ensuring consistent development standards.
For Knowledge Transfer Documentation acts as a knowledge repository for both current and future software engineers. By documenting code, architectural decisions, and project insights, technical writers help transfer vital knowledge and reduce reliance on individual expertise.

Getting Started as a Technical Writer:

Familiarize Yourself with Documentation Standards:
Start by learning about industry-standard documentation formats and style guides. Familiarize yourself with common tools and technologies used in technical writing, such as markdown, XML, and documentation generators.
Develop Strong Writing Skills:
Sharpen your writing skills by practicing clear and concise communication. Pay attention to grammar, structure, and formatting. Strive for simplicity without sacrificing technical accuracy.
Understand Your Audience:
Gain a deep understanding of your target audience, which may include end-users, developers, or both. Tailor your writing to their level of technical expertise, ensuring that the content is accessible and comprehensible.
Collaborate with Engineers:
Engage with software engineers to gather insights, seek clarifications, and understand the intricacies of the software. Actively participate in code reviews, meetings, and discussions to stay up to date with the project's progress.
Learn Documentation Tools and Processes:
Acquire proficiency in documentation tools such as version control systems, content management systems, and collaborative platforms. Understand the software development life cycle and incorporate documentation tasks into it.
Create a Portfolio:
As you gain experience, build a portfolio that showcases your technical writing skills. Include a variety of samples, such as user guides, API documentation, or tutorial materials, to demonstrate your versatility.

In a nutshell:

Becoming a technical writer offers a multitude of benefits, ranging from improved communication skills and career opportunities to personal growth, knowledge transfer, and user empowerment. It is a rewarding profession that combines technical expertise with effective communication, making it an essential role in the software industry. It plays a crucial role in the software development lifecycle, enabling effective communication, enhancing user experience, and fostering collaboration among software engineers. By mastering technical writing skills, software engineers can empower users, transfer knowledge, and contribute to the overall success of software projects.

I hope this article gives you a reason or more to start your interesting technical writing journey. I will be sharing more tips and insights I have gathered on my experience as a technical writer. So, stay tuned. Also comment and let me know your take on Technical writing and any questions in that line. Adiós :)

Are we all going to have tabs for smartphones?

Simon Rabuogi — Wed, 21 Apr 2021 15:34:43 +0000

Our smartphones have become part of our lives. We want to have them everywhere we go and use them all the time. Today there are almost all applications you could need to achieve whatever task you wish to have done. From studying, body exercises, communication, entertainment, job and earning a living and any other thing just name it. All these could be done from the comfort of your palms. We all agree our smartphones are at the center of our daily lives.
These gadgets have some factors that have led them to get to this level of importance. Some of these features are portability, internet connectivity, multi-functionality, user-friendliness, etc.
Just to discuss some of the above-listed functions;

Internet connectivity - smartphones have their name for the ability to access the internet. This has highly contributed to its adaptability as a technology. Reason being that users want to be connected for the purpose of sharing internet resources.
Multi-functionality - It is a beautiful thing being able to listen to your favorite music, do your calculations, read your novels, watch the news or favorite shows, make calls and send text messages or emails from the same gadget. Smartphones have done this very well.
User-friendliness - Many people are able to handle smartphones without much assistance and if any, google is there to take care of it all. This is another reason smartphones are still widely acquired and are in use.

Main point of concern

Portability - This is a major factor and it is why we are all at ease moving around comfortably wherever we go. Smartphones are handy enough and could fit in your pockets as you move around. However there is a trend that could affect the portability smartphones. This is all about the smartphones' display. There has been a trend with smartphone displays. From the various tech giants who have dominated the smartphone industry like Samsung, Tecno, Infinix or Iphone, latests release come with an increased display size of the screen. As at now, April 2021 Samsung Galaxy S21 ultra has a display size of 6.8-inches, Note 20 ultra has 6.9-inches almost 7 inches. The bad news is that this trend is likely to continue. And as a developer it is worrying. Back to portability as a mojor feature of smartphones, how is it affected? This sitution has even changed the name from smartphone to phablets. Meaning it is a combination of the former smartphone size and the traditional tab size. Question then becomes, are smartphones going to be as handy as they have before? Or are we headed to the tab size direction? Will, they fit comfortably into our pockets as they have bofere or are we going to ask fashion designers to consider phablets sizes as they design our pants? All these questions are worth thinking of, but time will tell the fate of the users and develpers who concern themselves with developing various interface fearures. Personally, I feel we are going to get to a point where the phablets are going to have a standard size beyond which it won't surpass. This is owing to the fact that for userfriendliness as a key factor, a smartphone should be sizable enogh to allow making calls even without headsets, comfortably fit into the pocket unless users will be forced to have bags for carrying their phablets around. With that, I wish to hear your point of view, regarding the smartphone size and how it is going to affect portability. Thanks for reading. Bye!!