gistfile1.txt

Prodev

- Bad code vs good code
  - Differences
  - How does good code looks like?
  - How to write good code
    - <RESEARCH>
    - Opinions (read a lot)
  - How to deal with bad code?
    - Avoid?
    - Around?
    - Refactor?
      - TDD!
- What does a pro-dev looks like?
  - ... we are all engineers
  - we are not different
  - there is no magic!
  - The why do we have Seniors
    - They do process
      - Whatever but they do, it may be a different one every time, but there is one
    - They think more about the problem than the solution
    - Think first Do second
    - The Problem
- Design an interface for an elevator in a building 1000 floors tall
- Lets go from Problem to Production Release as a Pro
  - Mindset
    - Don't code anything
    - Don't decide on technologies first
    - Separate what you want to learn from what you need to solve
    - Coding is expensive use paper as much as possible
  - Problem
    - Aerial photography with precision positioning metadata
      - Aerial
        - Aircraft
          - Types
            - ...
          - Size
        - Control
          - Used by engineers
          - They can carry up a mobile device
          - ...
        - Performance
          - Large areas
            - Define large
          - Precision
          - Flight times
        - ...
      - Photography
        - Cameras
          - Weight
          - Size
        - Night/Day?
        - How many pictures a second?
        - Height limit?
        - File extraction
        - Control
          - API?
        - ...
      - Precision metadata
        - Sensors
          - Position
          - Height
          - Light
        - Data reading
        - Interfaces
          - Cable
          - Logic
        - Storage
          - Files?
          - Embedded?
      - Coordination
        - How to control everything
        - How to match Photo with sensor data
        - How to storage
        - How to handle errors
        - How to monitor
        - ...
      - Every use case needs different equipment
    - Our particular solition
      - Where we started
        - Follow laser
        - Autonomous stations
        - Precision data
        - Visualization tools
        - "The uber for drones"
      - Where we are now
        - An specific problem: Construction
          - Constraints
          - Assumptions
          - Expected output
        - The drone is now tailored for the specific use case
      - Data processing platform
      - Our specific problem
        - Provide a set of aerial photos that follow a constrained route that overlap themselves at least on 90% where each photo has embedded exif data GPS, camera orientation, aircraft attitude.
          - The photos should be taken at the ground in the most horizontal position possible
          - The photos should can be taken out and uploaded to the Skycatch Uploading System.
          - The photo should have embedded in its exif tag
            - Lat, Lng
            - North
            - Atti (yaw, pitch, roll)
      - The Drone
        - EVO 3x
          - Components
            - What makes it fly
              - Power train
              - FC
                - Sensors
                  - GPS
                  - Baro
                  - IMU
              - RC
                - Radio
                - App
            - What takes the pictures
              - Camera
              - Storage
            - Controller
          - Intel Edison
            - Full Linux
            - Open Embed
            - Yocto
            - 
    - plan deploy document
    - gitflow
    -