Ebachour Week 11 - Revision history

Ebachour: /* Link to Presentation */ fixed link

2017-11-14T07:51:24Z

‎Link to Presentation: fixed link

Ebachour: Finished

2017-11-14T07:40:42Z

Finished

Ebachour: Starting assignment lol

2017-11-14T07:37:59Z

Starting assignment lol

New page

=10 things I didn't know=

=Outline and Electronic Journal=
*Xcode is the Apple IDE that you use to build software for Mac or iPhone.
**iOS SDK comes filled with dozens and dozens of APIs
***each API gives you access to some feature
****Location
****Playing sounds
****Rend text
****Collection information
***They don’t necessarily give you everything, but still they do a lot of the work
**The IDE does most of the work of giving you functions that you can use to write software, but it doesn’t necessarily give you everything.
***For example, they give you the time in milliseconds when playing a song, but you have to write the code that displays this time in minutes and seconds or even hours if that’s what you want for your program
**Software that is used to make software is usually free because it stimulates the development of even more software and therefore these developers want people to have access to it.
*Framework
**There are hundreds of frameworks to choose from
**Handles a lot of the tedious parts of writing software for you.
***Django has a command that makes a directory with some files and configurations inside, your project directory, which gives you access to libraries and services that add to and enhance the standard library
**Sometimes you can tell what framework was used to build a website just by looking at the finished product.
***Downsides
****Frameworks lock you into a way of thinking.
****Some people feel that the framework makes things too easy and that they become a crutch.
****You pay a price of speed and control for all the convenience they offer
**Most of the frameworks are free
*Debugging
**Debugging is programming. It’s running your code, finding out that there is some unexpected outcome, changing it, and then running again. It can be frustrating because bugs can be hard to find.
***Stupid like 4 + 20 vs. 4 + “20”
**Testing
***TDD = test driven development
***Tests are just code
****They check the functions in other code
****They run automatically, and you can find out if your day’s work broke things
*Version control
**Record every change made to the documents in your codebase
**Stores all of these records for you to have access to at any point
**Record who made every change
***Very transparent
**Totally free
**The best way to development collaboratively
***Open source
****Anybody can fork and do work on the project as much as they want without affecting any of the actual codebase, and then they can ask if their code can be added to the main codebase and the developers get to decide if it makes the cut
**Clone => Add => Commit => Push
***Gets code from Github, and brings it to you, and then you can push your code changes whenever you want with the next three commands
*Main message to show us how the modern world of development works and what tools are used in making software and websites
*This article was very clearly written and easy to read. It was important because it is able to provide a general understanding of development and stacks to anybody who reads it.
*Described IDE, SDK, Frameworks, Testing and Debugging, and Version Control in this paper. Explained them all in plain English which allows us all to understand everything.
*Every single one of these things mentioned above are pretty much crucial to the development of any software or website, just as we will be implementing most of them for our own project.

=Acknowledgements=
I worked with my homework partner [[User:Simonwro120 | Simon Wroblewski]] in class. We also met face-to-face one time outside of class. We texted outside of class and met to work on the presentation part of the assignment together.<br>
'''While I worked with the people noted above, this individual journal entry was completed by me and not copied from another source.'''<br>
[[User:Ebachour|Ebachour]] ([[User talk:Ebachour|talk]]) 23:37, 13 November 2017 (PST)

=References=
* LMU BioDB 2017. (2017). Week 14. Retrieved November 14, 2017, from https://xmlpipedb.cs.lmu.edu/biodb/fall2017/index.php/Week_14

{{Template:ebachour}}

@@ Line 61: / Line 61: @@
 =Link to Presentation=
-[[Media:e_and_s_presentation_2.pptx|Eddie and Simon Presentation]]
+[[Media:e_and_s_presentation_2.pdf|Eddie and Simon Presentation]]
 =Acknowledgements=

@@ Line 1: / Line 1: @@
 =10 things I didn't know=
 =Outline and Electronic Journal=
@@ Line 45: / Line 58: @@
 *This article was very clearly written and easy to read. It was important because it is able to provide a general understanding of development and stacks to anybody who reads it.
 *Described IDE, SDK, Frameworks, Testing and Debugging, and Version Control in this paper. Explained them all in plain English which allows us all to understand everything.
 *Every single one of these things mentioned above are pretty much crucial to the development of any software or website, just as we will be implementing most of them for our own project.
 =Acknowledgements=