Hello, welcome to Overview of Web and Cloud Development. When you’re starting out as a Web Developer, it can be difficult to determine what you need to learn and what order you should learn it in. Understanding how familiar websites are constructed and delivered to you is a good starting point. Let’s review the basics of how you interact with a website. You launch an internet browser – there are lots available: Google Chrome, Microsoft Edge, Mozilla Firefox, and Apple Safari are some of the most popular. The browser has an address bar, into which you enter a URL, like www.IBM.com. The browser then contacts the server with the name and requests the information that makes up the website.
The server then sends a response, which contains the data that the client requires to display the website. For most websites, the server will return: HTML, which defines the structure of the page, but doesn’t look very attractive CSS, which adds style and flair to the page and JavaScript, which adds interactivity and dynamic content. Content displayed by websites can contain elements that are either previously stored on the server (called “static”) or generated each time they are requested by the client (called “dynamic”). Dynamic elements can involve information coming from other systems and applications, such as databases. Most websites contain static and dynamic elements to provide the best user experience. Cloud Applications are similar to Websites in that they request content that a server returns. Cloud Apps are built to work seamlessly with a Cloud-based back-end infrastructure, Cloud-based data storage and data processing, and other Cloud services, making them very scalable and very resilient.
The environment for building websites and Cloud Applications is divided into two primary areas: front-end and back-end. The front-end deals with everything that happens at the client-side – everything the user can see and interact with. You can choose to specialize in front-end coding, using HTML, CSS, JavaScript and related frameworks, libraries, and tools. The back-end deals with everything that happens on the server before the code and data are sent to the client. The back-end coding usually handles the logic and functionality that make the website or app work, and the authentication processes that keep data secure. Back-end developers may also work with relational or noSQL databases, even collaborating with database administrators in bigger projects. Full-stack developers have skills, knowledge, and experience in both front-end and back-end environments.
Whichever way you choose to specialize, you will need the appropriate tools to help you work. The first tool most developers add to their resources is a code editor. Developers also need tools to integrate, build, compile, and debug code. Integrated Development Environments or IDEs incorporate some of these additional capabilities beyond just code editing and make it easier to build and manage your code. Good IDEs support multiple languages and integrate with management and storage tools like Git and GitHub. Other useful features are custom extensions and themes for supporting your working style and environment. Examples for code editors and IDEs include Sublime Text, Atom, Vim, VS Code, Visual Studio, Eclipse and NetBeans.
In this brief overview, you learned about: The basic communication between client and servers. How websites are built and displayed. Front-end development is about what happens on the client side. Back-end development is about what happens on the server. Full-stack development includes both front-end and back-end development. IDEs will help you create and manage your code.
Internet websites offer lots of different services, one of the most popular being online shopping. When you explore an online shopping website, navigating through pages, choosing different product categories, or comparing products, you are interacting with the front end of a website. Let us see how the front end of a website is developed by front-end developers. For this, we need to understand how a website is made. To create a website, web developers usually use Hypertext Markup Language, HTML, Cascading Style Sheets, CSS, and JavaScript. These languages are designed to work in conjunction with each other. HTML is used to create the physical structure of a website.
The physical structure contains elements such as text, links, images and videos, page dividers, and buttons. The HTML code ensures a proper formatting of all text and image elements so that browsers display the page consistently. The front-end developer codes the structure of the website. A website is like a house, which has only been constructed. Just like we need interior designers to add style to a space, we need front-end developers to add the necessary glamour and appeal to a website. When you order products from any website, you realize that the pages have a pleasing font, attractive colors, and are easy to navigate. Developers use CSS to create stylish websites.
CSS provides front-end developers with a standard method to define, apply, and manage different sets of style characteristics for a website and each of its components. CSS ensures uniformity in look and feel, style, colors, fonts, designs, and layouts. So HTML is used to create the structure, and CSS is used to design it and make it appealing. CSS is also used to create websites that have cross-browser compatibility, which means that they are compatible with multiple browsers and multiple devices, such as PC, mobile devices, iPads, etc. Online shopping websites are intuitive, interactive, and quick to load. This is where JavaScript comes into the picture. JavaScript is an object-oriented programming language that is used in conjunction with HTML and CSS to add interactivity to a website.
For example, you use HTML to add a login button to a page and CSS to style that button. Then you use JavaScript to add login functionality to that button. A new front-end development language is Syntactically Awesome Style Sheets, SASS, called SAS. It is an extension of CSS that is compatible with all versions of CSS. SASS enables you to use things like variables, nested rules, and inline imports to keep things organized. SASS allows you to create style sheets faster and more easily. Another language that is being used now is Learner Style Sheets, LESS or LESS.
LESS enhances CSS, adding more styles and functions. It is backwards compatible with CSS. LESS.js is a JavaScript tool that converts the LESS styles to CSS styles. Using all these languages, websites are designed as adaptive and responsive. Or adaptive websites display the version of the website designed for a specific screen size. For example, a website can provide more information if opened on a PC than when opened on a mobile device. Responsive design of a website means that it will automatically resize to the device it is being accessed from.
For example, if you open up a product's website on your mobile device, it will adapt itself to the small size of the screen and still show you all the features. A JavaScript framework is an application framework that is written in JavaScript. Programmers can manipulate the different functions, use them wherever required, and can create device-responsive applications. A few examples of several frameworks being used are Angular Framework, an open-source framework being maintained by Google. Angular Frameworks allow websites to render the HTML pages quickly and efficiently. It has built-in tools for routing and form validation. React.js has been developed and maintained by Facebook.
It is a JavaScript library that builds and renders components for a web page. It is not a complete suite of tools. For example, routing is not a part of this framework and will need to be added using a third-party tool. React.js only helps build and drop components into a page. Vue.js is maintained by the community and its main focus is the Vue layer, which includes user interface, buttons, and visual components. It is flexible, scalable, and integrates well with other frameworks. It is very adaptable.
It can be a library or it can be the framework. The task of a front-end developer evolves continuously. The technologies are upgraded constantly, and so front-end developers need to keep upgrading the websites that they create. The websites that they create should work in multiple browsers, multiple operating systems, and multiple devices.
Welcome to the importance of back-end development. A front-end developer creates websites and Cloud applications using HTML, CSS, and JavaScript to create what the user sees and interacts with in the client's software. A back-end developer creates and manages all the resources that are needed to respond to the requests that the user makes through the client. The back-end developers tasks focus on enabling this server infrastructure or back-end to process requests, supply data, and provide other services securely. Front-end and back-end developers must work together very closely. Each needs to understand the requirements of the solution and how their respective parts will interact before the development process can begin. Throughout the life cycle of the website or Cloud app, front-end and back-end developers collaborate to resolve issues and add functionality.
How does the work of a back-end developer affect you as you are browsing the Internet or using a Cloud App? Think about it like this. When you're shopping online, what happens to the data you enter? Your login information, your product searches, your payment info. The back-end processes all of these things. The back-end developers write and maintain the parts of the application that process the inputs. Let's think about your experience as you explore an online shopping site and make a purchase.
As you search for products, your search request is submitted to a web application, which then retrieves the data from a separate database and serves it back to the client for display. To facilitate this, a back-end developer must understand the language that the web application uses, how to query the database for the correct data, and how to bring the two together. Even a simple task like navigating around the site can require the skills of a back-end developer. Many sites have restricted areas that are only available to users who have an account and have logged in. User account management, authentication and authorization can be the responsibility of the back-end developer too. Once you've decided what you want to purchase, you must add it to your card and make a payment. The purchase process requires you to submit sensitive information such as your address and credit card number.
The back-end developer must ensure that this data is securely handled and stored. Front-end client interactions, whether a request for data, like an image, accepting input from a user filling out a form, or securing sensitive information like a credit card number, all require different services from the backend server. Each request needs to interact with the back-end in a different way. Back-end developers use APIs, routes, and endpoints to process incoming requests. An API is code that works with data, usually using JSON or XML. APIs have set rules and structure. A route is a path to a website or page that the user interacts with.
Routes generally take user input and show results based on the input and end point maybe an API or may simply be a path. When a request from the front-end arrives at the back-end, it is routed to the correct service. If the back-end has an endpoint defined for the request by using routing, the request will be addressed and replied to. If the endpoint is missing, the server returns a 404 error. Back-end developers must create and maintain this server side routing. Along with back-end APIs, routes effectively allow the front-end client to plug into the correct socket at the back-end. APIs provide a mechanism for Cloud apps, mobile apps, and other types of software to access resources from the back-end.
To perform all this back-end development, you will need to be familiar with at least one back-end language and its associated frameworks. Among the most popular languages today is JavaScript, which was originally designed to run in web browsers, adding extra interactivity and dynamic content to web pages. JavaScript is also being used on the back-end with new releases adding server-side functionality. JavaScript has many frameworks, but two of the most well-known are Node.js and Express. Python is another popular language. It's very flexible and easy to learn. Python has wide functionality.
It can be used for everything from creating webpages to connecting to a database, to performing data analysis. Two well-known Python frameworks are Django and Flask. Back-end developers often work with data and databases. You will also benefit from learning some SQL. To help handle requests from databases, back-end developers can use object relational mapping tools or ORM to connect to the databases and retrieve the correct data. Although an ORM can hide some of the complexity of querying databases, it's useful to understand the fundamentals of databases so that you can troubleshoot any issues that arise. The day-to-day tasks of a back-end developer focus on the behind the scenes functionality that keeps websites, Cloud apps, and mobile apps up and running.
Back-end development covers a wide range of technologies, from managing user accounts, authentication and authorization to ensuring that sensitive data is stored and transferred securely. Back-end developers also work with databases, retrieving, processing, and storing data as required. Life for a back-end developer is very challenging and ever-changing.
Welcome to Teamwork and Squads. After watching this video, you will be able to define teamwork and describe the advantages of collaboration in software engineering and describe squads. By definition, a team is a group of people working together towards a common aim. Within a team, you’ll find a range of different people with different skills, experience, and talents. Each person can give their attention and effort to the things that they are good at, and by working alongside others on tasks outside their current repertoire, they can expand their skillset. Working in a team promotes creativity. Collaborating with others gives you the opportunity to discuss ideas and challenge one another’s thinking about a subject.
Good teamwork is empowering: positive attitudes and behaviors can impact the rest of the team and create positive results. Working well as a team doesn’t always come naturally, but there are some things you can consider to help your team succeed. Each member needs to trust and respect the other members of the team. This generally comes with time, but depends on all of the members contributing equitably. Defining and agreeing on goals for a project is essential so that the whole team knows what they are working towards. And you also need to define and agree on roles to avoid any duplication of effort or missed tasks. Working with each members strengths is important to make the most of the talent within your team, as is celebrating success and analyzing problems.
Communication is vital in a team environment. Ensure that you choose a method that works for everyone so you know that the whole team is seeing and responding to information. So, what does teamwork look like in software engineering? Teams often start projects with a kick-off meeting where they plan how they will complete the project, assign tasks, and agree on goals. Throughout the lifetime of a project, you’re likely to have whole team and/or sub team meetings to review progress and plans. Design and code reviews can be requested at the team level and undertaken by whoever has availability at that point in time. Team members might present walkthroughs of their sections of responsibility to the rest of team so that the whole team has oversight of all parts of the project.
And, key team members will likely present walkthroughs to stakeholders at various times during the project. When a project is complete, retrospective meetings may be held to review what went well and what could be improved in future projects. You may have a mentor who may or may not be in your current project team. You might also be asked to be a mentor. Sometimes team mentoring is used so everyone can learn from each other. Some groups also have teams working on internal projects such as defining code standards, maintaining or updating legacy cross-project code, or reviewing potential new software for usefulness to the team. Good teamwork can bring many benefits to a project.
Working alongside others can encourage creativity and enable you to take advantage of each person’s strengths while also allowing them to gain knowledge and skills from other members of the team. When working as part of a team, software engineers are more likely to adhere to corporate coding standards and regularly document their code. The additional accountability that teamwork creates results in better quality code, fewer bugs, and more maintainable code. From a software engineer’s point of view, working as a team can reduce stress because there’s always someone to turn to and get help from. And having someone to discuss problems with can help you to increase your understanding and resolve more issues by yourself. By working in a team, each member has a greater idea of the bigger picture, resulting in a more coherent overall solution. Some organizations that follow Agile development methodologies may call a team a squad.
Typically, a squad is a small team of up to 10 developers. It is likely to consist of: A squad leader who acts as the anchor developer and coach for the squad. And a few software engineers who develop and implement the product features and test cases. It may also include one or two user experience developers or designers. In some squads the developers may work together in pairs to practice pair programming. You’ll learn more about pair programming in another video. In this video, you learned that: Software engineering teams meet regularly throughout the duration of a project.
Good teamwork encourages creativity, shares knowledge, and results in better quality code. Squads are small teams used in agile development.
Welcome to Insiders' Viewpoints: Teamwork in Software Engineering. In this video, we will hear from experts discussing how teamwork is important in software development, and how teams work together. Yeah, so teamwork is very, very important in the world of software development. As a software engineer, you're not just going to be sitting at your desk coding all day. One of the most important aspects of working on a team or on an engineering team is communication, and knowing how to collaborate and speak with your team members about the code you've written, especially if you're going to a UX designer, and say, Hey, here's what I can do. And your spec is a bit off. Can we massage your your specs a bit just so we can meet the code coding requirements.
Incredibly important, I while I think it's possible for a single person to engineer and deploy and run software, I, I think doing it as a team is both more impactful and gets you more potential to do bigger and greater things, I think it's also just a more fulfilling process, when you're when you're, you're building something with a group of individuals, I think, you know, with without the support structure, it's hard to build something and support it and maintain it just by yourself. So teamwork, to me, is essential, because we're talking to each other all day. And we're not only talking to our tech leads or senior engineer, we're talking to product managers, we're talking to UX designers, we're talking to business analysts, we're talking to data analysts, and so on and so forth. You have the support system, you have diversity of opinions and perspectives in terms of how you go about building it, it's more satisfying, you kind of can take larger risks, because you're, you're in it together, and you're there to support each other, I think the celebration of of a job well done is is a lot more, you know, it's a lot more fulfilling when you're when you're doing that with someone else. But I think it just gives you both kind of a larger range of scope and a larger sort of risk portfolio, if you will, and you're able to, I think just, you know, get a lot more done a lot more checks and balances and really gives you you know, less likely, there's a less likely chance that you're gonna miss something, or you're gonna make a mistake, there's a lot of a lot of support there. And so every project I've worked on has had at least three other people that I have needed to communicate with and support to be a reliable resource for them to go to them for questions. Like I always have to be talking to somebody about something.
So teamwork is crucial. Like, you can't, you can't work in an isolated silo forever, at some point, you have to talk to someone else. Building a project product takes a lot of people, a lot of us come together to make a whole and to get the product shipped to production so our users can use it. And so teamwork is imperative.
Welcome to Pair Programming. After watching this video, you will be able to describe pair programming and compare different styles and list the benefits and challenges of pair programming. Pair programming is an extension of teamwork where two developers work side-by-side at one computer. They can either be physically at the same computer or work virtually via video link or shared screens. The former is the preferred option, but virtual pair programming can also be productive. Pair programming is a type of Agile development where two developers can plan and discuss their ideas continually as they create a solution, generally resulting in a better end product. There are various styles of pair programming: Driver/navigator style is the most common style, where one developer is the driver, typing in the code, and the other is the navigator, reviewing the code as it’s written and giving directions where to go next.
The navigator also keeps an eye on the bigger picture of the overall solution. When working in this way, it’s important to regularly swap roles to keep both of the pair engaged across the whole task. Ping-pong style incorporates test-driven development. For each task, one developer writes a failing test and then the second developer writes code to pass that test. For each new task, they swap roles, so regularly changing who writes the test and who writes the implementation. The two developers work together at the end of each task refactoring the successful code to refine and improve it. Strong style pair programming is a good way for junior software engineers to learn from more experienced ones.
The defining rule for this is that for an idea to go from your head to the computer, it must go through someone else’s hands. So, the more experienced of the pair is the navigator and the driver learns from witnessing their implementation and thought processes. For this to work well, the driver shouldn’t challenge any ideas until the full implementation is complete so as not to interrupt the flow of ideas from the navigator. Now pair programming has many benefits. It’s a good way to share knowledge and skills from one developer to another or between the two and a great way for a new team member to get up to speed on a project. As well as enhancing the technical skills of the pair, it’s also a good way of building soft skills such as communication and problem solving. Having two sets of eyes on the code often results in fewer typos, logic errors, and bugs.
And it enables code reviews to be done on the fly. While this doesn’t replace formal code reviews, it does enable another layer of review. Having two people thinking about a problem can result in multiple initial ideas, but is likely to result in the optimal approach being chosen earlier in the process. And although pair programming can take longer than individuals writing the same solutions, it’s likely to result in better code with less time spent reviewing, testing, and bug fixing. There are also a few challenges to overcome. Working in a pair requires long periods of focus which can be exhausting for the two programmers. And personal or other work commitments can impact the pair schedule.
Sometimes one of the pair can end up controlling the entire process, resulting in a more typist/programmer pairing which doesn’t benefit from any of the positives of pair programming. And at other times, individual personalities may not work well together. When multiple sets of pair programmers are present, their discussions can result in a noisy environment for the other workers in the room. In this video, you learned that: Pair programming is an Agile development technique where two developers work alongside each other. There are multiple styles of pair programming. And pair programming builds technical and soft skills, results in better quality code and solutions, and increases overall efficiency.
Welcome to Insiders’ Viewpoints: Pair Programming. In this video, software engineers will discuss their experiences with pair programming and share their thoughts about the benefits and potential challenges associated with this way of working. First, we'll begin by asking about their experiences with pair programming and about the benefits they associate with it. At every job I've ever had, there have come times where you pair up with someone else, you get someone else sitting next to you at a computer, you're sitting next to them at their computer, you're looking at a problem together, you're thinking about it. Yes, I have actually, some of the benefits are definitely working with an engineer who might be more of a senior engineer, because they have a lot of insight. And they obviously have a lot of experience doing what you're probably trying to figure out how to do. And it's really great when it's someone who can both guide you but also kind of take take a step back and not take over at the same time.
I think pair programming can can be very beneficial. I think. If you're when you're working with someone together, it's an opportunity to learn I think pair programming can be very great in circumstances where someone is new to a team. New to a programming language new to a set of tools, or a development environment that is new to them, sitting next to someone who's an expert, I think can both help you ramp up more quickly, it can help the the team itself, sort of understand where you are, in terms of your own knowledge and journey and help put you in a place to both succeed and utilize you in your skills as best as possible. It does help you get real time feedback, you don't necessarily have to wait for code to be sent out to be reviewed, and you can kind of, you know, brainstorm together in real time on the actual implementation of it. Ultimately, I try to keep in mind that the goal of pair programming is that everyone has inherent blind spots in the way that they think. And that the way that they approach a problem.
And if you are talking to somebody else, they can point out what your blind spots are. And they're going to have different blind spots than you as well. So you can point out their blind spots. What do you think are the drawbacks and challenges of pair programming? I think that can be a con sometimes when you're working with another engineer and you're trying to pair program with someone who kind of like takes over and then doesn't allow you to do your part or to learn especially if they kind of like already know how to do something. So it's kind of like a double-edged sword. On the one hand, you want to get that practical experience of practice of pair programming and you want to get that experience from someone else.
But at the same time, you want to make sure that you're learning. I personally find pair programming to be a little frustrating. Because the ways I go about solving problems can be very different than the ways other people go about solving problems. And it's not that I have some special, unique, wonderful technique, it's just that everyone's brain works differently. And watching someone else go through their workflow of how to solve a problem, they're not clicking the exact same buttons that you are. And that can get very frustrating to me. It's like, why are you using your mouse because all those things, there's keystrokes or like, you could be doing this so much faster.
And so I find it a challenge to do pair programming sometimes. You actually need calendar time. So you need to be able to dedicate time to sit together and work together and have an aligned schedule. You both you can either be physical, could do it virtually, but you need to make the time to do it. Pair programming, some can come with some overhead in terms of getting off the ground. So if you have a tight time crunch, competing priorities, maybe just not enough, there might be not enough time in the schedule to allow for it, that can be one of the cons. That it can while you can get long term, I think efficiency benefits from you know, built, did writing the code together, because then support in the future will be easier because you have more people who know how the code was written and what the intent was.
So there are definitely long term benefits. But there could be you know, some short term costs to it. So there are trade offs in that sense
아직 댓글이 없습니다.
로그인 후 댓글을 남길 수 있어요