"왕초보의 앱 확장 프로그램 개발 입문하기"
iOS 개발자의 친구, Safari와 Xcode의 확장 프로그램을 써보신 적 있나요? 꼭 Safari와 Xcode가 아니어도 확장 프로그램을 써본 경험은 있을 거예요. 개발하다 필요한 순간에 코드 스냅샷을 찍거나 웹 사이트 번역을 하거나 팝업창을 띄운다던가... 이런 경험들 말이죠.
이러한 사용 경험을 개발 경험으로 바꾼다면 어떨까요?
이 세션에서는 Safari Extension과 Xcode Extension을 만드는 과정을 간단하게 공유해 드리려고 합니다. 과자 먹듯이 가볍게 들어주세요!
-------------
Let's Swift 2022 의 '우당탕탕! Safari Extensiond에서 Xcode Extension까지' 세션의 발표자료입니다.
(2022-11-30)
Chef vs Puppet vs Ansible vs SaltStack | Configuration Management Tools Compa...Edureka!
This DevOps Tutorial takes you through what is Configuration Management all about and basic concepts of Infrastructure as code. It also compares the four most widely used Configuration Management tools i.e. Chef, Puppet, Ansible and SaltStack.
Check our complete DevOps YouTube playlist here: http://goo.gl/O2vo13
DevOps Tutorial Blog Series here: https://goo.gl/P0zAfF
Slide deck of the presentation done at the Hactoberfest 2020 Singapore event. The talk and demo showed GitHub Actions in practice with examples of Github Superlinter, SonarCloud integration and CI CD to Azure Kubernetes service.
The recording of the session is available on YouTube
https://youtu.be/sFvCj62wmWU?t=6732&WT.mc_id=AZ-MVP-5003170
Github Actions enables you to create custom software development lifecycle workflows directly in your Github repository. These workflows are made out of different tasks so-called actions that can be run automatically on certain events.
This document provides an overview of Spring MVC including:
- Spring MVC is a web framework built on the Servlet API that uses the MVC pattern. It features a DispatcherServlet that handles requests and delegates to controllers.
- The request processing workflow in Spring MVC involves the DispatcherServlet dispatching tasks to controllers, which interact with services and return a view name. The view is then rendered using a ViewResolver.
- Spring MVC applications use a WebApplicationContext containing web-related beans like controllers and mappings, which can override beans in the root context. Configuration can be done via XML or Java-based approaches. Important annotations map requests and bind parameters.
Github is a continuous Integration and Continous delivery platform that provides an excellent option for automating workflows to run specific tasks when some event like code push or a release is triggered on the repository. In this Session we will be exploring Github Actions and learning how to use them in our projects.
This document discusses Cypress, an open-source JavaScript testing framework for front-end web applications. It highlights key Cypress features like time travel debugging, real-time reloads, and automatic waiting. It provides an overview of how to install Cypress, write tests using an arrange-act-assert structure, query elements, make assertions, and interact with elements. Examples of testing a login flow and cart panel are also presented. The document promotes Cypress and encourages attending live coding sessions to learn more about component testing.
GitHub Actions is an automation platform for GitHub repositories that allows users to build workflows to automate software tasks. It was introduced in 2019 and is based on Azure Pipelines. Workflows are configured using YAML files and can be triggered by events like push commits, pull requests, or scheduled times. Actions, which are reusable code components, can be used in workflows and are sourced from the GitHub marketplace or created by users. GitHub Actions is free for public repositories and offers paid plans for private repositories.
This document discusses using GitHub Actions for continuous integration and continuous delivery (CI/CD) workflows. It begins with an introduction and agenda, then discusses the basics of GitHub Actions including what problems it solves and why CI/CD is important. Several key aspects of GitHub Actions are then covered at a high level, including how it compares to AWS CodePipeline, examples of GitHub workflows, and the core components of actions, artifacts, events, jobs, runners, steps, and workflows. The document concludes with an overview of creating a GitHub Actions workflow and exploring further possibilities.
Jenkins is a tool that supports continuous integration by automatically building, testing, and deploying code changes. It integrates code changes frequently, at least daily, to avoid "big bang" integrations. Jenkins runs builds and tests across multiple platforms using slave nodes. It supports various source control systems and build tools and notifies developers of failed builds or tests through email or other plugins.
This document discusses code obfuscation techniques used to protect intellectual property and hide malicious code. It describes general obfuscation methods like control transformations, computation transformations, and data abstraction obfuscation. Specific techniques are outlined like opaque predicates, inheritance modifications, variable splitting, and method inlining/cloning. Code obfuscation aims to complicate reverse engineering but cannot completely prevent it, and it decreases performance. When used judiciously, obfuscation provides some protection against theft and malware insertion.
The document discusses ReactorKit, an architecture framework that uses RxSwift to help address issues like massive view controllers and cyclic data dependencies. It provides concise summaries of ReactorKit's key concepts including the Reactor pattern which separates business logic from views using a unidirectional data flow, and examples of how state changes and view actions flow through the different components.
* What is different GitHub Flow and Git Flow?
* What is GitHub Actions?
* How to write the simple workflow?
* What's problem in GitHub Actions UI?
* What's problem with Secrets in GitHub Actions?
* How to write your first GitHub Actions and upload to the marketplace?
* What's a problem with environment variables in GitHub Actions?
The document discusses hexagonal architecture and how it can be applied to PHP applications. It begins by defining software architecture and its importance. It then explains hexagonal architecture, which separates an application into distinct layers including domain, application, and infrastructure layers. The layers are decoupled via defined boundaries and interfaces. Commands are used to communicate between layers and are handled by command buses and handlers. Examples are given of implementing repositories, commands and handlers to follow this pattern in a PHP application.
This document provides an introduction to the version control system Git. It defines key Git concepts like the working tree, repository, commit, and HEAD. It explains that Git is a distributed version control system where the full history of a project is available once cloned. The document outlines Git's history, with it being created by Linus Torvalds to replace the commercial BitKeeper tool. It then lists and briefly describes important Git commands for local and collaboration repositories, including config, add, commit, log, diff, status, branch, checkout, merge, remote, clone, push, and pull. Lastly, it covers installing Git and generating SSH keys on Windows for accessing Git repositories.
This document provides an overview of Spring MVC including:
- Spring MVC is a web framework built on the Servlet API that uses the MVC pattern. It features a DispatcherServlet that handles requests and delegates to controllers.
- The request processing workflow in Spring MVC involves the DispatcherServlet dispatching tasks to controllers, which interact with services and return a view name. The view is then rendered using a ViewResolver.
- Spring MVC applications use a WebApplicationContext containing web-related beans like controllers and mappings, which can override beans in the root context. Configuration can be done via XML or Java-based approaches. Important annotations map requests and bind parameters.
Github is a continuous Integration and Continous delivery platform that provides an excellent option for automating workflows to run specific tasks when some event like code push or a release is triggered on the repository. In this Session we will be exploring Github Actions and learning how to use them in our projects.
This document discusses Cypress, an open-source JavaScript testing framework for front-end web applications. It highlights key Cypress features like time travel debugging, real-time reloads, and automatic waiting. It provides an overview of how to install Cypress, write tests using an arrange-act-assert structure, query elements, make assertions, and interact with elements. Examples of testing a login flow and cart panel are also presented. The document promotes Cypress and encourages attending live coding sessions to learn more about component testing.
GitHub Actions is an automation platform for GitHub repositories that allows users to build workflows to automate software tasks. It was introduced in 2019 and is based on Azure Pipelines. Workflows are configured using YAML files and can be triggered by events like push commits, pull requests, or scheduled times. Actions, which are reusable code components, can be used in workflows and are sourced from the GitHub marketplace or created by users. GitHub Actions is free for public repositories and offers paid plans for private repositories.
This document discusses using GitHub Actions for continuous integration and continuous delivery (CI/CD) workflows. It begins with an introduction and agenda, then discusses the basics of GitHub Actions including what problems it solves and why CI/CD is important. Several key aspects of GitHub Actions are then covered at a high level, including how it compares to AWS CodePipeline, examples of GitHub workflows, and the core components of actions, artifacts, events, jobs, runners, steps, and workflows. The document concludes with an overview of creating a GitHub Actions workflow and exploring further possibilities.
Jenkins is a tool that supports continuous integration by automatically building, testing, and deploying code changes. It integrates code changes frequently, at least daily, to avoid "big bang" integrations. Jenkins runs builds and tests across multiple platforms using slave nodes. It supports various source control systems and build tools and notifies developers of failed builds or tests through email or other plugins.
This document discusses code obfuscation techniques used to protect intellectual property and hide malicious code. It describes general obfuscation methods like control transformations, computation transformations, and data abstraction obfuscation. Specific techniques are outlined like opaque predicates, inheritance modifications, variable splitting, and method inlining/cloning. Code obfuscation aims to complicate reverse engineering but cannot completely prevent it, and it decreases performance. When used judiciously, obfuscation provides some protection against theft and malware insertion.
The document discusses ReactorKit, an architecture framework that uses RxSwift to help address issues like massive view controllers and cyclic data dependencies. It provides concise summaries of ReactorKit's key concepts including the Reactor pattern which separates business logic from views using a unidirectional data flow, and examples of how state changes and view actions flow through the different components.
* What is different GitHub Flow and Git Flow?
* What is GitHub Actions?
* How to write the simple workflow?
* What's problem in GitHub Actions UI?
* What's problem with Secrets in GitHub Actions?
* How to write your first GitHub Actions and upload to the marketplace?
* What's a problem with environment variables in GitHub Actions?
The document discusses hexagonal architecture and how it can be applied to PHP applications. It begins by defining software architecture and its importance. It then explains hexagonal architecture, which separates an application into distinct layers including domain, application, and infrastructure layers. The layers are decoupled via defined boundaries and interfaces. Commands are used to communicate between layers and are handled by command buses and handlers. Examples are given of implementing repositories, commands and handlers to follow this pattern in a PHP application.
This document provides an introduction to the version control system Git. It defines key Git concepts like the working tree, repository, commit, and HEAD. It explains that Git is a distributed version control system where the full history of a project is available once cloned. The document outlines Git's history, with it being created by Linus Torvalds to replace the commercial BitKeeper tool. It then lists and briefly describes important Git commands for local and collaboration repositories, including config, add, commit, log, diff, status, branch, checkout, merge, remote, clone, push, and pull. Lastly, it covers installing Git and generating SSH keys on Windows for accessing Git repositories.
2016년 11월 모 대학에서 IT 계열 전공 재학생들을 대상으로 진행했던 진로 특강 자료입니다.
앞쪽의 제반 내용들은 다양한 자료들을 정리하면서 제 생각을 담았습니다.
이 자료의 가장 핵심적인 내용은 5가지 유형의 현직 선배들을 대상으로 설문을 실시하여 후배들에게 들려주고 싶은 현실적이고 진솔한 이야기를 정리한 부분입니다.
IT 분야 그리고 소프트웨어 개발자의 삶의 모색하는 분들에게 조금이나마 도움이 되길 바라는 마음에 자료를 공개합니다.
패스트캠퍼스의 안드로이드 앱 개발 입문 캠프는, 3주간의 빡센 자바 프로그래밍 훈련 기간을 거쳐 남은 5주동안 실습 예제 중심으로 빠르게 안드로이드 앱 개발을 경험해보는 8주 강의입니다.
- 강사님과 실시간 질문 답변을 주고받을 수 있는 온라인 채널 제공
- 앱 마켓에 런칭하며 필요한 필수 지식까지 전수
- 8주 강의가 끝나도 계속 질문 답변 채널을 닫지 않는, 그야말로 평생 교육
- 개별 매니저가 수강생 한 분씩 케어하는 시스템
으로 인해 많은 사랑을 받고 있습니다. 앞으로도 많은 관심 부탁드려요!
24. 취업 준비하기
블라인드 코딩테스트는 묻지도 따지지도 말고 지원하기
- 코딩테스트 모의 시험 가능
- 알고리즘 문제 + Swift 문법 or CS 지식
- 문제나 키워드 기억해놓으면 나중에 Swift 혹은 CS 공부할 때 도움이 됨
- (잘하면) 2차 코딩테스트 체험 가능
- 대부분 API 사용해 서비스 구현하는 과제
- 기업에서 어떤 방식으로 코드를 구성하는지 체험할 수 있음