JavaRush /Java Blog /Random EN /Coffee break #59. Text editor or IDE: which is better for...

Coffee break #59. Text editor or IDE: which is better for beginner programmers? How to get your first developer job - conclusions from resume review

Published in the Random EN group

Text editor or IDE: which is better for beginner programmers?

Source: Hackernoon There are two questions that often confuse new programmers: which programming language to start with, and which is better to use for coding: a text editor or an IDE? Coffee break #59.  Text editor or IDE: which is better for beginner programmers?  How to get your first developer job - conclusions from resume review - 1If you are a beginner, then you may be wondering which platform you should use to code and execute your program. The choice is between a text editor + terminal combination and a development environment (IDE) with both functions. This can also include the use of an online IDE to run programs.

Text editor

The formal definition of a word processor is that it is a type of program used for editing text. Essentially, a text editor is a program on your computer that allows you to create and edit files in different programming languages. In other words, this is the place where you write your code. Features and benefits of the text editor:
  • Syntax highlighting;
  • Code formatting;
  • Editing;
  • File division;
  • Quick switching between projects;
  • Selecting (highlighting) several elements;
  • Cross-platform support.
The text editor works well with programming languages ​​that don't require code to be executed in the console. It's also a great tool for easily editing source code without making a lot of changes.

Integrated Development Environment (IDE)

An IDE is a software application that provides developers and programmers with a comprehensive environment for writing code and developing applications. IDE features and benefits:
  • Syntax highlighting;
  • Code formatting;
  • Code completion;
  • Automation;
  • Version management;
  • Debugging;
  • Code execution;
  • Testing.
An IDE has an advantage when you want the program to run directly in the console. In general, when writing code, we only need to do debugging and testing. There is no strict requirement for choosing an IDE.

What should be in our system?

Now that we know what a text editor and an IDE are, you may have questions about what should be in our system (computer). The answer depends on the programming language you use and what features you want from the platform. The specifications of your system and the amount of disk space will also influence your choice. Let's say you started coding in Java. If you use a text editor, you write fixed lines of code, except for a few parts. Then you use the terminal or command line to run your program. If you're working with an IDE, it will provide you with a template so you don't have to write those fixed lines of code, and you'll also get a console so you don't have to search for anything to run your program. If you have an old computer or low RAM, the IDE will not run faster than a text editor because the IDE requires more resources. If you choose an IDE, you'll need a separate development environment for each programming language you use.

Conclusion

For a newbie in programming, using a text editor would be preferable because with it we will learn many things - from file extension to debugging. An IDE makes it easy to write and run programs, but we don't know how things work. There's one more thing: many new programmers get frustrated when they discover that 10 out of 20 lines of code in each program are the same. Because of this, they no longer want to manually write these lines. In this case, they can either use the IDE or save a file with these lines of code and copy and paste from there if necessary.

How to get your first developer job - conclusions from resume review

Source: Free Code Camp When applying for jobs, everyone says they are passionate about programming and development. As an employer, I am looking for confirmation of this . This week I looked at several resumes of people who were changing careers or looking for their first developer job. I spent about 2-5 minutes per person before deciding if they would be a good fit. Not much time to impress a stranger! Here's a short list of what I was looking for:
  • Regular commits on GitHub;
  • Individual projects;
  • Evidence of good writing skills.
Coffee break #59.  Text editor or IDE: which is better for beginner programmers?  How to get your first developer job - conclusions from resume review - 2

Regular commits on GitHub

What does your GitHub contribution history look like? If you are passionate about coding, then I assume you do programming regularly. The easiest way to demonstrate your passion is to code publicly. Create a GitHub repository, learn how to make atomic commits, and contribute them to your projects. This will send a good signal to employers that you write code every day and that you really mean it when you say you're passionate about coding. Let's look at this person's public contribution history on GitHub: Coffee break #59.  Text editor or IDE: which is better for beginner programmers?  How to get your first developer job - conclusions from resume review - 3We see that the person only codes publicly during certain times of the year: November, December, March, and July. I suspect that they coincide with bootcamp projects - in other words, projects that were mandatory. Looking at candidates from the same boot camp group, where each person has the same commit schedule, it is difficult to single out just one. To me as an employer, this is not a strong signal of passion. After all, the chart shows several months that are completely empty. This person could write code every day on his personal laptop, but as an employer I don't see him putting in the effort. Let's look at another person's commit history: Coffee break #59.  Text editor or IDE: which is better for beginner programmers?  How to get your first developer job - conclusions from resume review - 4Here we see almost daily commits on GitHub. This is a very strong signal that the person is interested in coding and has been coding daily for the last twelve months. This is fantastic, especially if this person is not a programmer by his main profession. I'd love to talk to him and find out what exactly he's working on! Even if the bulk of his commits are editing text in the README file, it's still a great sign of commitment and consistency.

Personal projects

Start your own projects and support them regularly! Simple steps are enough:
  • Create real content.
  • Add your own personality to it. Find images that mean something to you.
  • Take pride in your work: it doesn't need to be beautifully designed - I'm looking for a developer, not a visual designer. But remember the basic requirements. If it is a web project, then the project should be cross-browser compatible, be compatible with mobile devices, elements should not overlap each other, and so on.
Common errors I've noticed:
  • No links to projects.
  • Create a typical classroom project or with lorem ipsum (nonsense text). When 20 graduates of the same boot camp send me resumes, it gets boring very quickly. If you haven't bothered to personalize your portfolio, it certainly doesn't indicate that "you're passionate about coding."
  • Links to projects that no longer work. Make sure you test all the projects you mention.
  • Links to projects that require customization. Make it easier! Create a great README file with details on how to set it up. Insert some screenshots, UX flows, sequence diagrams, and so on. It's unlikely that the employer will check all of this, but screenshots, UX processes and other elements demonstrate that you were really involved in your project.

Evidence of good written communication skills

I believe every technical job has a requirement for writing skills. There is documentation in your code (though ideally your code should be self-documenting). There's also Slack and pull requests as part of your daily work. Another simple thing to include on your resume: “excellent communication skills.” This is indicated on every resume. As an employer, I don't pay attention to this point because it is difficult to assess with a resume. However, if you supplement this statement with links to well-structured README files; on articles you've written or on your personal blog, then bingo! As an employer, I will definitely follow these links. They help me evaluate your personality, your communication style, the amount of detail and effort you put into structuring your thoughts, and much more.

Let's sum it up

If you've decided to become a developer, finding your first job can seem like a daunting task. But don't give up! I hope this article will help you make your resume more unique so you can stand out from the crowd of other candidates. As a result, this will make your first job easier.
Comments
TO VIEW ALL COMMENTS OR TO MAKE A COMMENT,
GO TO FULL VERSION