1 - 10 of 15 Chapters
[You probably woke up by an alarm set on your mobile phone, maybe learned about the weather on your smartwatch, or checked some emails on your computer. Words like apps, smartphones, smartwatches, and software are so common nowadays that sometimes it’s hard to remember that most of these things...
[Everything usually starts in the same way: there is something that can be solved or improved by the use of technology. Maybe it is an idea that someone had while seeing themselves or their friends struggle with something. Maybe a user that reported some extra functionality (usually called...
[Right now, we have a clear idea of our potential users’ needs. You understand their pain points, and we have a good idea of how we might solve them. The next step is being able to translate these ideas (and requirements) into a software system. And to do that, we need to first take a step back...
[In the previous chapter, we launched our new e-commerce landing page, and now you want to show your family so they can see it. Your mom goes to a browser and types the URL you gave her: jollyfarm.co. Have you ever considered what happens when she presses enter?]
[The JollyFarm, as an e-commerce, will be a dynamic system. This means that it will need a frontend and a backend system. We can start by looking at what the frontend consists as you have more familiarity with it. Every website you’ve accessed, every mobile app you’ve used, and everything you...
[We defined how our frontend should look like, now it’s time to think about the other side! While the frontend is responsible for interacting with users and making sure they have an amazing experience with the website, the backend is responsible for implementing the business logic as well as...
[Whenever a new project is starting, there are several important decisions that might seem trivial but can highly impact the future of the project. Although someone might jump at you with an answer for them, the truth is that it’s never as simple as “use this” or “use that.” As with anything in...
[So far, we spent a long time on decisions and work that happen before a single line of code is ever written. We have the requirements for the MVP, we know the tools, now comes the fun part! It’s time to start building it. To do that, we need to have developers working together toward common...
[Software is never done. There is always a new feature that was requested or a new bug that needs to be fixed. In reality, the developer will spend the vast majority of time not writing code but reading it.]
[In the previous chapter, we discussed several topics that can impact the quality of the code and overall productivity of developers writing it. Although all of them are fundamental, there’s still a big piece missing: checking that the code does what’s intended. At the end of the day, the user...
Read and print from thousands of top scholarly journals.
Continue with Facebook
Sign up with Google
Log in with Microsoft
Already have an account? Log in
Bookmark this article. You can see your Bookmarks on your DeepDyve Library.
To save an article, log in first, or sign up for a DeepDyve account if you don’t already have one.
Sign Up Log In
To subscribe to email alerts, please log in first, or sign up for a DeepDyve account if you don’t already have one.
To get new article updates from a journal on your personalized homepage, please log in first, or sign up for a DeepDyve account if you don’t already have one.