4 answers
1
Question
Asked
922 views
What are the things you like and dislike about being a software engineer?
I am 16 years old and interested in a computer science career.
Login to comment
4 answers
Updated
Rafael’s Answer
Being a software engineer has its perks! Many enjoy the thrill of problem-solving and the creative freedom that comes with designing and building software. Continuous learning is a big part of the job, keeping engineers on their toes with new technologies and trends. Collaboration with diverse teams and the flexibility to work remotely are also appealing aspects. On the flip side, long hours and tight deadlines can be challenging, as well as the sometimes frustrating task of debugging and troubleshooting. The need to constantly learn and keep up with technology can be demanding, and sitting for long periods may not suit everyone. It's a dynamic and ever-evolving field that offers both excitement and challenges!
James Constantine Frangos
Consultant Dietitian & Software Developer since 1972 => Nutrition Education => Health & Longevity => Self-Actualization.
6342
Answers
Updated
James Constantine’s Answer
Dear ff,
Here are the things I appreciate:
Since 1972, I've been a self-learner, mastering ten different computer languages. I've built extensive platforms in areas such as medical report generation, nutrition education, and dietary software. I cherish the flexibility of setting my own work hours. I've found my niche with the Microsoft Visual Studio 2017 Professional Version. In addition to this, I also work as a dietitian-nutritionist during the day and spend my nights programming.
However, there are certain aspects I'm not fond of:
The intensity of my work has led to warnings about potential burnout. The health department's executive officer has even suggested I take a break.
I also believe that AI is not the best fit for administrative tasks like politics, parole decisions, judicial rulings, and management. Its strengths lie in service-oriented roles.
Stay blessed!
James Constantine.
Here are the things I appreciate:
Since 1972, I've been a self-learner, mastering ten different computer languages. I've built extensive platforms in areas such as medical report generation, nutrition education, and dietary software. I cherish the flexibility of setting my own work hours. I've found my niche with the Microsoft Visual Studio 2017 Professional Version. In addition to this, I also work as a dietitian-nutritionist during the day and spend my nights programming.
However, there are certain aspects I'm not fond of:
The intensity of my work has led to warnings about potential burnout. The health department's executive officer has even suggested I take a break.
I also believe that AI is not the best fit for administrative tasks like politics, parole decisions, judicial rulings, and management. Its strengths lie in service-oriented roles.
Stay blessed!
James Constantine.
Updated
Rollan’s Answer
In my 39 years as a software engineer, I've witnessed a multitude of technological transformations, making my career journey quite an adventure. I've only experienced unemployment twice in my tenure, with the most recent one nudging me towards retirement.
There are several aspects of software engineering that I find rewarding:
- The opportunity to work across diverse industries such as engineering, medical, biotech, and the semiconductor sector. This has allowed me to understand the varying needs and capabilities of different end-users.
- The flexibility offered by technology to work remotely or freelance, with some roles even providing the liberty to choose your working hours. This is particularly beneficial when you need to accomplish tasks during regular business hours.
- The constant stream of challenges ensures that there's never a dull moment in the job.
- International travel is another perk, especially when dealing with global clients. Over the years, I've had the chance to visit Japan, England, Germany, South Korea, and several U.S states.
- The advent of AI is revolutionizing the field. Engineers who adapt to this change are likely to thrive, while those who resist may face difficulties.
However, there are a few aspects of software engineering that I find less appealing:
- Often, software development is the final stage, following hardware design. This can lead to making 'hacks' to compensate for hardware shortcomings, which can result in less optimal code. It's usually more cost-effective to implement a software solution for a hardware issue, which happens quite often.
- If hardware schedules are adversely affected, you might find yourself under pressure to deliver functional software within a limited timeframe. This could mean that some features may not be fully developed or tested, potentially causing issues down the line.
- The ever-evolving nature of technology necessitates staying updated with the latest trends to remain competitive. This can be challenging, especially when working for a company that prefers older technology and is resistant to innovation.
- The risk of burnout is real, as the job can sometimes demand long working hours.
- Software engineers are often roped into customer support roles, which can be a love-hate situation for many. When a hardware system encounters an issue, software is usually the first to be blamed. Consequently, a software engineer often ends up identifying the actual problem, which may or may not be related to software.
There are several aspects of software engineering that I find rewarding:
- The opportunity to work across diverse industries such as engineering, medical, biotech, and the semiconductor sector. This has allowed me to understand the varying needs and capabilities of different end-users.
- The flexibility offered by technology to work remotely or freelance, with some roles even providing the liberty to choose your working hours. This is particularly beneficial when you need to accomplish tasks during regular business hours.
- The constant stream of challenges ensures that there's never a dull moment in the job.
- International travel is another perk, especially when dealing with global clients. Over the years, I've had the chance to visit Japan, England, Germany, South Korea, and several U.S states.
- The advent of AI is revolutionizing the field. Engineers who adapt to this change are likely to thrive, while those who resist may face difficulties.
However, there are a few aspects of software engineering that I find less appealing:
- Often, software development is the final stage, following hardware design. This can lead to making 'hacks' to compensate for hardware shortcomings, which can result in less optimal code. It's usually more cost-effective to implement a software solution for a hardware issue, which happens quite often.
- If hardware schedules are adversely affected, you might find yourself under pressure to deliver functional software within a limited timeframe. This could mean that some features may not be fully developed or tested, potentially causing issues down the line.
- The ever-evolving nature of technology necessitates staying updated with the latest trends to remain competitive. This can be challenging, especially when working for a company that prefers older technology and is resistant to innovation.
- The risk of burnout is real, as the job can sometimes demand long working hours.
- Software engineers are often roped into customer support roles, which can be a love-hate situation for many. When a hardware system encounters an issue, software is usually the first to be blamed. Consequently, a software engineer often ends up identifying the actual problem, which may or may not be related to software.
Updated
Sanja’s Answer
Hi there, I spoke to one of our software engineers and here is what his response was:
I worked both as an individual freelancer and as operator of a small company that provided software development and general IT managed services to startups and other small and medium businesses. For software development, I either worked as a lone full-stack developer or as part of a very small team (typically 2-4). I don't have any insight into what it was like working for a big company as a full-time employee developer, which I imagine is a different experience.
Things I loved about the dev work: getting to fix problems, building cool stuff, seeing my ideas go out and make things happen, always learning new tools and languages, building working relationships with good clients, agile teams that cared about their products.
Things I didn't love (as a contractor/freelancer): chasing new business/business development, administrative bookwork to keep the business running, bidding jobs, clients who didn't understand what they were asking for and were never satisfied, Java.
I worked both as an individual freelancer and as operator of a small company that provided software development and general IT managed services to startups and other small and medium businesses. For software development, I either worked as a lone full-stack developer or as part of a very small team (typically 2-4). I don't have any insight into what it was like working for a big company as a full-time employee developer, which I imagine is a different experience.
Things I loved about the dev work: getting to fix problems, building cool stuff, seeing my ideas go out and make things happen, always learning new tools and languages, building working relationships with good clients, agile teams that cared about their products.
Things I didn't love (as a contractor/freelancer): chasing new business/business development, administrative bookwork to keep the business running, bidding jobs, clients who didn't understand what they were asking for and were never satisfied, Java.