Please enable JavaScript.

Coggle requires JavaScript to display documents.

Plan de estudio 2023, Developer, DevOps, Infraestructura, DB (SQL, No SQL,…

- - - - https://app.pluralsight.com/paths/skills/unit-testing-in-java
- - - - Testing
      - https://react.dev/learn
      - https://fullstackopen.com/es/
    - - Testing
      - https://www.youtube.com/watch?v=FF3D4tppyag
      - https://qwik.builder.io/tutorial/welcome/overview/
    - - https://www.udemy.com/course/rxjs-de-cero-hasta-los-detalles/learn/lecture/16623726?src=sac&kw=rxjs#overview
    - - https://www.udemy.com/course/angular-material-course/learn/lecture/29985506?start=0#overview
  - - - https://www.udemy.com/course-dashboard-redirect/?course_id=4086932
      - https://css-tricks.com/snippets/css/a-guide-to-flexbox/
    - - https://www.udemy.com/course/startcss/learn/lecture/23164398?start=0#overview
      - Scalable and Modular Architecture for CSS
        A flexible guide to developing sites small and large. http://smacss.com/
    - - xs (portrait phones)
      - sm (landscape phones)
      - md (tablets)
      - lg (desktops)
      - xl (large desktops)
- - - - https://www.jhipster.tech/
      - https://1drv.ms/b/s!AtFgg6I8wCB1so1D3JzdgFHbFo_CCA?e=aEOtRu
      - ng-bootstrap
      - Internationalization (i18n)-ngx-translate
      - https://www.jhipster.tech/doing-api-first-development/
- - - - git add .: esto incluye archivos en el stage, el stage es el area de las cosas que se van a ir en el proximo commit
      - git commit -m "......"
      - git status
      - git init
      - git commit -a: which will automatically notice any modified (but not new) files, add them to the index, and commit, all in one step.
      - git-tag - Create, list, delete or verify a tag object signed with GPG. git tag tagname commit name
    - - git log: At any point you can view the history of your changes using
    - - git branch: list of all existing branches
      - git branch name: new branch
      - git switch name
      - git merge experimental: aplica los cambios en la rama experimental a la rama actual
      - git diff: muestra los conflictos. This form is to view the changes you made relative to the index (staging area for the next commit). In other words, the differences are what you could tell Git to further add to the index but you still haven’t.
      - gitk: will show a nice graphical representation of the resulting history.
      - git branch -m new name: Rename
      - git branch -d o -D name: Delete. -d requiere que los se haya hecho un merge en la rama actual, -D lo borra de manera forzada
      - git branch branch-name tagname: start a new branch named branch-name based at tagname
    - - git clone ruta-repo my-repo
      - git pull ruta-repo branch. Ojo con hacer commit antes enla rama local
      - alice$ git fetch /home/bob/myrepo master
        alice$ git log -p HEAD..FETCH_HEAD
        "show everything that is reachable from the FETCH_HEAD but exclude anything that is reachable from HEAD".
        Alice already knows everything that leads to her current state (HEAD), and reviews what Bob has in his state (FETCH_HEAD) that she has not seen with this command.
      - git stash : lsaca los cambio del stage y los dejo de ver. Se usa cuando requiero hacer un pull pero no quiero hacer un commit antes.
      - git stash aplly: devuelve lops cambios al stage
      - git remote add bob /home/bob/myrepo: defining remote repository.
      - git merge bob/branch-name
    - - git log
      - git show nombre del commit el cual sacas con git log
      - git show HEAD
      - git show brnach-name
  - - - git-init(1) to create a new repository.
        
        git-log(1) to see what happened.
        
        git-switch(1) and git-branch(1) to switch branches.
        
        git-add(1) to manage the index file.
        
        git-diff(1) and git-status(1) to see what you are in the middle of doing.
        
        git-commit(1) to advance the current branch.
        
        git-restore(1) to undo changes.
        
        git-merge(1) to merge between local branches.
        
        git-rebase(1) to maintain topic branches. https://medium.com/@harishlyadav/when-to-use-git-rebase-explained-3c8192cba5c7
        
        git-tag(1) to mark a known point.
    - - git-clone(1) from the upstream to prime your local repository.
        
        git-pull(1) and git-fetch(1) from "origin" to keep up-to-date with the upstream.
        
        git-push(1) to shared repository, if you adopt CVS style shared repository workflow.
        
        git-format-patch(1) to prepare e-mail submission, if you adopt Linux kernel-style public forum workflow.
        
        git-send-email(1) to send your e-mail submission without corruption by your MUA.
        
        git-request-pull(1) to create a summary of changes for your upstream to pull.
    - - git-am(1) to apply patches e-mailed in from your contributors.
        
        git-pull(1) to merge from your trusted lieutenants.
        
        git-format-patch(1) to prepare and send suggested alternative to contributors.
        
        git-revert(1) to undo botched commits.
        
        git-push(1) to publish the bleeding edge.
- - - - https://explore.skillbuilder.aws/learn/public/learning_plan/view/84/developer-learning-plan?la=cta&cta=topbanner
    - - https://aws.amazon.com/es/training/learn-about/architect/?th=tile&tile=learnabout