15 Matching Annotations
  1. Apr 2023
    1. Start writing code every day

      This highlighted section states one of the tips the author mentions which would aid becoming a software engineer. It mentions to "start writing code every day." I think this is true because to become a good software engineer, it takes a lot of time and practice. If someone takes time out of their daily lives to write some code, their knowledge of the subject will stay sharp and there will be a less likely chance that the author forgets some of the rules of coding. This interests me because if I am teaching this to a class, it would be great for the students to understand this fact so they know how much time and practice it takes to become a software engineer.

    2. Learn to communicate well

      This highlighted section states one of the tips the author mentions which would aid becoming a software engineer. It mentions to "learn to communicate well." I think this is true because without good communication in a software development team, ideas wouldn't be able to be shared which would become a negative aspect when developing software.

    3. Find a great mentor

      This highlighted section states one of the tips the author mentions which would aid becoming a software engineer. It mentions to "find a great mentor." I think this is true because even though someone may be able to learn coding individually by themselves without any help, it would be so much easier to have a mentor around helping out because if the learner faces any errors, the mentor can be there to help them face it and ultimately solve the issue.

    4. Starting a new career in software development is both exciting and frightening. There is a lot to learn, and it takes years of practice to become really good at it, like with other crafts.

      This highlighted section states that becoming a software engineer can be both exciting and frightening due to the fact that it potentially takes years of practice to become good at. This section interests me because even though I am not an expert in the software engineer field just yet, I know that the process isn't easy and will take a lot of perseverance to master the craft of software engineering. This will aid my project because if I am teaching this to a class, the students would need to understand this fact before continuing to learn the process in class.

    5. How to Become a Great Software Developer

      Based off of the title, I can assume that the article is going to talk about tips of becoming a software engineer. I am interested to keep reading because it also mentions "actionable tips" which someone can use to aid the process of becoming a software engineer.

    1. What no one told me is just how much red tape there could be to developing. Just because something sounds simple doesn't necessarily mean that is the case. Honestly, I love what I do. Sure, there are parts that are unexpectedly complex or dull but they are outweighed by the challenges that I get to solve. Software engineering is a constantly evolving field as well. I love to learn so it is nice to constantly have new things to know.

      This last part overviews his overall experience in software engineering. He mentions how "software engineering is a constantly evolving field." I agree with this because new things are discovered and advances are always being made in the current age of technology.

    2. Finally, after the database had the correct fields and the back end supported it I was ready to make changes to the UI. This involved adding fields to various forms. JavaScript was needed to load the data into several different locations. ASPX files were updated to reflect the changes. Even some manual HTML was needed.

      In this part, he mentions how he "was ready to make changes to the UI." This interests me because in general, corrections and changes are needed a lot of times when interacting with computer software and developing it.

    3. For the last three months I have been working on a project for our business. I was asked to add a nickname feature to our software.

      In this part, he mentions his last 3 months and how he has "been working on a project for our business." This project contributes to his software development skills and his level.

    4. I have been working as a professional software engineer for just around 4 years as I write this article. I love it. There are always new challenges and technologies which really keep me on my toes.

      In this part, he mentions how "There are always new challenges and technologies which really keep me on my toes." I think this contributes to his love and initial inspiration into becoming a software engineer.

    5. What it’s like to be a Software Engineer

      Based off of the title, I assume that the article is going to explain what it's like to be a software engineer from the experience of one already. Due to this, I am interested to keep reading on.

    1. As I’ve grown older, it’s hard not to notice how the increasing reality of my mortality has shaped my perspective. At its worst, my job is just to help companies make more money. At its best, my job is to alleviate frustration of real people and help them lead more enjoyable and productive lives. I definitely nerd out on technical innovation and learning new skills, but when I die I want to have made a positive, lasting impact on humanity. In the end, I may not accomplish this through code; it may be a different journey altogether.

      This ending part overviews his perspective as a software engineer. He mentions how "my job is to alleviate frustration of real people and help them lead more enjoyable and productive lives." He also mentions a goal and what he wants to accomplish after he's all done with his career.

    2. My internship project was an ASP.NET (Visual Basic) application called the ISUB (Internet Site Unblock and Block) system.

      This highlighted section mentions his internship project and what it was. He mentioned how it was an ASP.NET application called ISUB. This gives the reader insight on how his internship gave him experience into his journey as a software engineer.

    3. Through an online community, I managed to talk a business in Seattle into paying me to use my newly acquired Flash skills to create a virtual tour of a house as well as a 360 degree interactive view of a watch. This was the first time I got paid for anything computer-related. I was elated, but inside I felt like I had just tricked someone into believing I was a professional. I guess I kind of did. I also designed a small graphic for another stranger online who sent me an FM radio audio card for my efforts. I had absolutely no need for an FM radio audio card, but was more than happy to do something I enjoyed for any sort of tangible reward.

      This explains his initial time earning money by an online community paying him to use his Flash skills to create "a virtual tour of a house" and also getting paid to design "a small graphic for another stranger online who sent me an FM radio audio card." He also mentioned how he would rather do this than other jobs such as working at a farm, as technology is more of his hobby than other work.

    4. The fact I could create anything I wanted and immediately publish it to the whole world blew my mind. I started learning how to build more complex websites, complete with horribly aliased (jagged edges) animated flames, 3D construction signs, and links across pages.

      How the author initially got hooked into computer software. This basically began his journey as a software engineer.