DOCSLIB.ORG

Lightning-Smart PHP IDE Enjoy Productive PHP Development

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Lightning-Smart PHP IDE Enjoy Productive PHP Development REFACTORING Refactor this Ctrl + Alt + Shift + T ⌃ T Lightning-Smart Rename Shift + F6 ⇧F6 PHP IDE Safe delete Alt + Delete ⌘ ⌦ Inline variable Ctrl + Alt + N ⌘ ⌥ N Extract Method / Variable Ctrl + Alt + M / V ⌘ ⌥ M / V EDITING Extract Parametert / Constant Ctrl + Alt + P / C ⌘ ⌥ P / C Basic code completion Ctrl + Space ⌃ Space GENERAL Show intention actions Alt + Enter ⌥ ↩ and quick-fixes Search everywhere Double Shift Double⇧ Quick documentation lookup Ctrl + Q F1 , ⌃ J Find action Ctrl + Shift +A ⌘⇧A Parameter info Ctrl + P ⌘ P Open corresponding Alt + 0 ... 9 ⌘ 0 ... ⌘ 9 Generate code Alt + Insert ⌘ N, ⌃↩ tool window Surround with... Ctrl + Alt + T ⌘ ⌥ T Open Preferences Ctrl + Alt + S ⌘ , Insert live template Ctrl + J ⌘ J Comment / uncomment line Ctrl + / ⌘ / SEARCH Comment / uncomment block Ctrl + Shift + / ⌘⇧/ Extend syntax-aware selection Ctrl + W ⌥↑ Find Ctrl + F ⌘ F Shrink syntax-aware selection Ctrl + Shift + W ⌥↓ Find in path Ctrl + Shift + F ⌘⇧F Add or remove caret Alt + Click ⌥Click Find usages Alt-F7 ⌥ F7 Select all occurrences Shift + Ctrl + Alt + J ⌘ ⌃ G Find usages in file Ctrl + F7 ⌘ F7 Select next occurrence Alt + J ⌃ G Show usages Ctrl + Alt + F7 ⌥ ⌘ F7 Unselect occurrence Alt + Shift + J ⌃⇧G Unselect all occurrences Esc ⎋ NAVIGATION or carets Duplicate current line Ctrl + D ⌘ D Go to declaration Ctrl + B, Ctrl + Click ⌘ B, ⌘ Сlick Delete line Ctrl + Y ⌘ ⌨ Go to class Ctrl + N ⌘ O Move line up Alt + Shift + Up ⌥⇧↑ Go to file Ctrl + Shift + N ⌘⇧O Move line down Alt + Shift + Down ⌥⇧↓ Go to symbol Ctrl + Alt + Shift + N ⌘ ⌥ O Join lines Ctrl + Shift + J ⌃⇧J Go to line Ctrl + G ⌘ L Split line Ctrl + Enter ⌘ ↩ Go to type declaration Ctrl + Shift + B ⌃⇧B Delete to word start Ctrl + Backspace ⌥ ⌨ Go to super-method Ctrl + U ⌘ U Delete to word end Ctrl + Delete ⌥ ⌦ or super-class Expand code block Ctrl + NumPad + ⌘ + View recent files Ctrl-E ⌘ E Collapse code block Ctrl + NumPad – ⌘ – Jump to navigation bar Alt-Home ⌘ ↑ Expand all Ctrl+Shift+Equals ⌘⇧+ Jump to editor Esc ⎋ Collapse all Ctrl+Shift+Minus ⌘⇧ – Go to previous editor tab Alt + left ⌘⇧[ Reformat code Ctrl + Alt + L ⌘ ⌥ L Go to next editor tab Alt + right ⌘⇧] Auto-indent line Ctrl + Alt + I ⌘ ⌥ I Quick definition Ctrl + Shift + I ⌥ Space, ⌘ Y Close active editor tab Ctrl + F4 ⌘ W Move to code block start Ctrl + [ ⌘ ⌥ [ Move to code block end Ctrl + ] ⌘ ⌥ ] RUNNING AND DEBUGGING Move to matching brace Ctrl + Shift + M ⌃ M Navigate to last Ctrl + Shift ⌘⇧⌨ Run / Debug Shift + F10 / F9 ⌃ R / ⌃ D edit location + Backspace Select configuration and run Alt + Shift + F10 ⌃ ⌥ R Previous highlighted error Shift + F2 ⇧F2 Select configuration and debug Alt + Shift + F9 ⌃ ⌥ D Next highlighted error F2 F2 Rerun tests Alt + Shift + R ⌃ ⌘ R Run Gulp / Grunt / npm task Alt + F11 ⌥ F11 VCS AND LOCAL HISTORY Step over / Step into F8 / F7 F8 / F7 Step out Shift + F8 ⇧F8 VCS operations popup Alt + backquote ⌃ V Evaluate expression Alt + F8 ⌥ F8 Commit to VCS Ctrl + K ⌘ K Enjoy Productive Resume F9 ⌘ ⌥ R Update project Ctrl + T ⌘ T 4831 Toggle breakpoint Ctrl + F8 ⌘ F8 View recent changes Alt + Shift + C ⌥⇧C PHP Development Key features Supported technologies Smart PHP code editor Debugging, testing and profiling • PHP Code editor • Frameworks PHP 5.3–7.2 Symfony, Drupal, PhpStorm features an editor that actually “gets” your PHP PhpStorm is renowned for its zero-configuration Visual Code analysis WordPress, Zend, code and deeply understands its structure. The IDE provides Debugger, providing extraordinary insight into what goes Code completion Magento, CakePHP, the best code autocompletion, refactorings, on-the-fly error on in your application at every step. It works with Xdebug Refactorings Yii, Laravel, Joomla! prevention, supports language mixtures and more. Automated and Zend Debugger, and can be used both locally and Code generation refactorings treat your code with care, helping you make global remotely. Testing with PHPUnit, Behat, PHPSpec, and • Git / SVN / HG / CVS / TFS ... PHPDoc support project changes easily and safely. Codeception as well as profiler integration are also available. • Remote hosts deployment Quick fixes FTP / SFTP / FTPS PHP_CodeSniffer Local or mounted folder PHP Mess Detector • Emmet • Smarty, Twig, Blade • Behat, PHPSpec, Codeception • Testing PHPUnit, Behat, PHPSpec • Issue trackers integration and Codeception With task context switching • Remote PHP interpreters • Built-in web server SSH, Vagrant, Docker, • HTML5 / XML / Schema Code quality analysis Complete development environment Docker Compose • CSS / Sass / LESS / SCSS Hundreds of code inspections verify your code as you type, inspecting Perform many routine tasks right from the IDE, thanks • Debugging & profiling + Stylus, Compass & more the whole project for possible errors or code smells. PHPDoc support, to Version Control Systems integration, support for remote Xdebug, Zend debugger • JavaScript code (re)arranger, code formatter with code style configuration and deployment, databases / SQL, command-line tools, Vagrant, • Terminal & Tools ECMAScript 6, TypeScript, other features help you write neat code that’s easy to support. Composer, REST Client, and many other tools. Local and via SSH Node.js, AngularJS, • Databases & SQL React, Meteor, Vue.js, Emmet 10+ dialects and refactorings Subscription pricing Yearly Monthly REST API development Productivity Guide Business € 199* € 19.90* The editor-based REST client will assist you in composing Check your PhpStorm feature usage and get tips & tricks HTTP requests, sending them to web-services, viewing to enhance your productivity in HELP | Productivity Guide Individual € 89* € 8.90* responses, and analyzing them. Open source Free project *20% discount after 1st year Learn more and download your free 30-day trial jetbrains.com/phpstorm.
Load more

Recommended publications
  • Behat Table of Contents
    behat #behat Table of Contents About 1 Chapter 1: Getting started with behat 2 Remarks 2 Examples 2 Functional testing as user stories 2 Beginning with Behat 2 Extending Behat with Mink 4 Testing JavaScript with Mink and Selenium 6 Setting up test data 7 Capturing emails 8 Installation or Setup 9 Credits 12 About You can share this PDF with anyone you feel could benefit from it, downloaded the latest version from: behat It is an unofficial and free behat ebook created for educational purposes. All the content is extracted from Stack Overflow Documentation, which is written by many hardworking individuals at Stack Overflow. It is neither affiliated with Stack Overflow nor official behat. The content is released under Creative Commons BY-SA, and the list of contributors to each chapter are provided in the credits section at the end of this book. Images may be copyright of their respective owners unless otherwise specified. All trademarks and registered trademarks are the property of their respective company owners. Use the content presented in this book at your own risk; it is not guaranteed to be correct nor accurate, please send your feedback and corrections to [email protected] https://riptutorial.com/ 1 Chapter 1: Getting started with behat Remarks This section provides an overview of what behat is, and why a developer might want to use it. It should also mention any large subjects within behat, and link out to the related topics. Since the Documentation for behat is new, you may need to create initial versions of those related topics.
    [Show full text]
  • Preview Grav Tutorial (PDF Version)
    Grav About the Tutorial Grav is a flat-file based content management system which doesn't use database to store the content instead it uses text file (.txt) or markdown (.md) file to store the content. The flat-file part specifically refers to the readable text and it handles the content in an easy way which can be simple for a developer. Audience This tutorial has been prepared for anyone who has a basic knowledge of Markdown and has an urge to develop websites. After completing this tutorial, you will find yourself at a moderate level of expertise in developing websites using Grav. Prerequisites Before you start proceeding with this tutorial, we assume that you are already aware about the basics of Markdown. If you are not well aware of these concepts, then we will suggest you to go through our short tutorials on Markdown. Copyright & Disclaimer Copyright 2017 by Tutorials Point (I) Pvt. Ltd. All the content and graphics published in this e-book are the property of Tutorials Point (I) Pvt. Ltd. The user of this e-book is prohibited to reuse, retain, copy, distribute or republish any contents or a part of contents of this e-book in any manner without written consent of the publisher. We strive to update the contents of our website and tutorials as timely and as precisely as possible, however, the contents may contain inaccuracies or errors. Tutorials Point (I) Pvt. Ltd. provides no guarantee regarding the accuracy, timeliness or completeness of our website or its contents including this tutorial. If you discover any errors on our website or in this tutorial, please notify us at [email protected] i Grav Table of Contents About the Tutorial ...................................................................................................................................
    [Show full text]
  • Devops with Vagrant and KVM/Qemu Hiroshi Miura (@Miurahr) NTT DATA Corporation
    CloudOpen Japan 2014 DevOps with Vagrant and KVM/qemu Hiroshi Miura (@miurahr) NTT DATA Corporation. Copyright © 2013 NTT DATA Corporation Disclaimer Any product name, service name, software name and other marks are trade mark or registered mark of corresponding companies. This presentation is in a purpose of providing current information on emerging technologies and there is no grantee of correctness and/or persistence of features in any future. A presenter and NTT Data Corporation provide information in as-is basis and have no responsiveness for results that you got according to information in this presentation material. Copyright © 2014 NTT DATA Corporation 2 Who am I? • Production work • OpenStack SI team • Swift object storage • OSS devel: • Vagrant-KVM • Linux Kernel • etc… Github.com/nttdata-osscloud Github.com/miurahr Copyright © 2014 NTT DATA Corporation 3 Agenda 1. What is DevOps 2. Introduction to Vagrant 3. Vagrant-KVM 4. Infrastructure chages 5. Future Copyright © 2014 NTT DATA Corporation 4 What is DevOps? Mike Loukides, 2012, @Velocity conference “If you're going to do operations reliably, you need to make it reproducible and programmatic.” Copyright © 2014 NTT DATA Corporation 5 What is DevOps? • The nature of “operations” Cloud changes • Growing distributed systems • Software development practice • “cooperation and collaboration” between dev and ops Copyright © 2014 NTT DATA Corporation 6 DevOps for developer • Gap between Development and Operations • Goals • Process and approach • Tools • Infrastructure engineering becomes like a development. • Infrastructure as a code • Adoption of Vagrant Copyright © 2014 NTT DATA Corporation 7 Introduction To Vagrant Copyright © 2014 NTT DATA Corporation 8 What is Vagrant • development environment on VM, container or cloud • same • among team members.
    [Show full text]
  • Design Patterns in PHP and Laravel — Kelt Dockins Design Patterns in PHP and Laravel
    Design Patterns in PHP and Laravel — Kelt Dockins Design Patterns in PHP and Laravel Kelt Dockins [email protected] Design Patterns in PHP and Laravel Kelt Dockins Dolph, Arkansas USA ISBN-13 (pbk): 978-1-4842-2450-2 ISBN-13 (electronic): 978-1-4842-2451-9 DOI 10.1007/978-1-4842-2451-9 Library of Congress Control Number: 2016961807 Copyright © 2017 by Kelt Dockins This work is subject to copyright. All rights are reserved by the Publisher, whether the whole or part of the material is concerned, specifically the rights of translation, reprinting, reuse of illustrations, recitation, broadcasting, reproduction on microfilms or in any other physical way, and transmission or information storage and retrieval, electronic adaptation, computer software, or by similar or dissimilar methodology now known or hereafter developed. Trademarked names, logos, and images may appear in this book. Rather than use a trademark symbol with every occurrence of a trademarked name, logo, or image we use the names, logos, and images only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark. The use in this publication of trade names, trademarks, service marks, and similar terms, even if they are not identified as such, is not to be taken as an expression of opinion as to whether or not they are subject to proprietary rights. While the advice and information in this book are believed to be true and accurate at the date of publication, neither the authors nor the editors nor the publisher can accept any legal responsibility for any errors or omissions that may be made.
    [Show full text]
  • Drifter Documentation Release 1.2.0
    Drifter Documentation Release 1.2.0 Gilles Crettenand, Sylvain Fankhauser, Christian Stocker and contributors Aug 27, 2019 Getting Started 1 Goals 3 2 The idea behind the framework5 3 What this framework is not ?7 4 Intended Public 9 4.1 Requirements...............................................9 4.2 Usage................................................... 10 4.3 Customization.............................................. 11 4.4 Contributing............................................... 11 4.5 System Roles............................................... 11 4.6 Webserver Roles............................................. 13 4.7 Database Roles.............................................. 15 4.8 PHP Roles................................................ 16 4.9 Python Roles............................................... 18 4.10 Ruby Roles................................................ 19 4.11 Java Roles................................................ 20 4.12 Webpack................................................. 21 4.13 Gulp Role................................................. 23 4.14 Browser Roles.............................................. 24 4.15 Other Roles................................................ 25 4.16 PHP.................................................... 26 4.17 CI..................................................... 27 4.18 Running and writing tests........................................ 29 4.19 The future ?................................................ 29 4.20 Create boxes..............................................
    [Show full text]
  • Test Kitchen, Inspec Docker - Fastest Way to Run Stuff (Virtual Virtual Machines) DOCKER
    TEST DRIVEN INFRASTRUCTURE COMPLIANCE AS CODE by Joaquín Menchaca À PROPOS DE MOI ABOUT ME ROCKET LAWYER SENIOR DEVOPS BUILD/RELEASE ENGINEER aka Linux Ninja Pants Automation Engineering Mutant actual photo https://slides.com/devopsstu dio/lisa18_tdi AGENDA 1. Setup 2. Context 3. Chef + InSpec 4. Ansible + InSpec 5. Bonus SETUP THE CODE https://github.com/darkn3rd/lisa18_t est_driven_infra CODE git clone \ https://github.com/darkn3rd/lisa18_test_driven_infra cd lisa18_test_driven_infra # Using Virtual Workstation vagrant up vagrant ssh cd lisa18_test_driven_infra # Using Host (MacOS X or Linux) #### Install Requirements # Using Host (Windows) #### Install Rrequiremnts #### Warning: Might not work, had success w/ Chef THE HOST SETUP must be able to run Docker or Vagrant MINIMUM REQUIRED ChefDK - bundles ruby, test kitchen, inspec Docker - fastest way to run stuff (virtual virtual machines) DOCKER Easiest Path is Docker Desktop DOCKER PACKAGE MANAGERS choco install docker-for-windows https://chocolatey.org/ brew cask install docker https://brew.sh/ DIRECT DOWNLOAD https://www.docker.com/products/docker-desktop DOCKER Debian Package on Ubuntu sudo apt-get update -qq sudo apt-get install -y apt-transport-https \ curl ca-certificates software-properties-common DOCKER_REPO="https://download.docker.com/linux/ubuntu" curl -fsSL ${DOCKER_REPO}/gpg | \ sudo apt-key add - sudo add-apt-repository \ "deb [arch=amd64] ${DOCKER_REPO} \ $(lsb_release -cs) \ stable" sudo apt-get update -qq sudo apt-get install -y docker-ce sudo usermod -aG docker $USER
    [Show full text]
  • Coverity Static Analysis
    Coverity Static Analysis Quickly find and fix Overview critical security and Coverity® gives you the speed, ease of use, accuracy, industry standards compliance, and quality issues as you scalability that you need to develop high-quality, secure applications. Coverity identifies code critical software quality defects and security vulnerabilities in code as it’s written, early in the development process when it’s least costly and easiest to fix. Precise actionable remediation advice and context-specific eLearning help your developers understand how to fix their prioritized issues quickly, without having to become security experts. Coverity Benefits seamlessly integrates automated security testing into your CI/CD pipelines and supports your existing development tools and workflows. Choose where and how to do your • Get improved visibility into development: on-premises or in the cloud with the Polaris Software Integrity Platform™ security risk. Cross-product (SaaS), a highly scalable, cloud-based application security platform. Coverity supports 22 reporting provides a holistic, more languages and over 70 frameworks and templates. complete view of a project’s risk using best-in-class AppSec tools. Coverity includes Rapid Scan, a fast, lightweight static analysis engine optimized • Deployment flexibility. You for cloud-native applications and Infrastructure-as-Code (IaC). Rapid Scan runs decide which set of projects to do automatically, without additional configuration, with every Coverity scan and can also AppSec testing for: on-premises be run as part of full CI builds with conventional scan completion times. Rapid Scan can or in the cloud. also be deployed as a standalone scan engine in Code Sight™ or via the command line • Shift security testing left.
    [Show full text]
  • Symfony 5 : TWIG
    Symfony 5 : TWIG Achref El Mouelhi Docteur de l’universite´ d’Aix-Marseille Chercheur en Programmation par contrainte (IA) Ingenieur´ en Genie´ logiciel [email protected] H & H: Research and Training 1 / 64 Plan 1 Introduction 2 Commentaire 3 Interpolation 4 Declaration´ de variable 5 Operations´ sur les variables 6 Structure conditionnelle 7 Structure iterative´ H & H: Research and Training 2 / 64 Plan 8 Filtre 9 Ref´ erencement´ d’un fichier 10 Lien hypertexte 11 Variables globales 12 Inclusion 13 Block et heritage´ 14 Bonnes pratiques H & H: Research and Training 3 / 64 Remarque Symfony 5 utilise la version 3 de Twig. Introduction Symfony Twig Moteur de templates pour PHP. Apparu en 2009. Syntaxe inspiree´ par Jinja (moteur de template du framework Django de Python). Issu et utilise´ par Symfony . Supporte´ par plusieurs IDE : NetBeans, PhpStorm, Eclipse, Visual Studio Code... Supporte´ par plusieurs editeurs´ de texte : Sublime text, notepad++, vim... © Achref EL MOUELHI © H & H: Research and Training 4 / 64 Introduction Symfony Twig Moteur de templates pour PHP. Apparu en 2009. Syntaxe inspiree´ par Jinja (moteur de template du framework Django de Python). Issu et utilise´ par Symfony . Supporte´ par plusieurs IDE : NetBeans, PhpStorm, Eclipse, Visual Studio Code... Supporte´ par plusieurs editeurs´ de texte : Sublime text, notepad++, vim... © Achref EL MOUELHI © Remarque Symfony 5 utilise la version 3 de Twig. H & H: Research and Training 4 / 64 Inconvenients´ Ralentir le chargement de page Un langage (de template) de plus
    [Show full text]
  • Chapter 2 - Local Infrastructure Development: Ansible and Vagrant
    Chapter 2 - Local Infrastructure Development: Ansible and Vagrant Prototyping and testing with local virtual machines Ansible works well with any server to which you can connect—remote or local. For speedier testing and development of Ansible playbooks, and for testing in general, it’s a very good idea to work locally. Local development and testing of infrastructure is both safer and faster than doing it on remote/live machines—especially in production environments! In the past decade, test-driven development (TDD), in one form or another, has become the norm for much of the software industry. Infrastructure development hasn’t been as organized until recently, and best practices dictate that infrastructure (which is becoming more and more important to the software that runs on it) should be thoroughly tested as well. Changes to software are tested either manually or in some automated fash- ion; there are now systems that integrate both with Ansible and with other deployment and configuration management tools, to allow some amount of infrastructure testing as well. Even if it’s just testing a configuration change locally before applying it to production, that approach is a thousand times better than what, in the software development world, would be called ‘cowboy coding’—working directly in a production environment, not documenting or encapsulating changes in code, and not having a way to roll back to a previous version. The past decade has seen the growth of many virtualization tools that allow for flexible and very powerful infrastructure emulation, all from your local workstation! Chapter 2 - Local Infrastructure Development: Ansible and Vagrant 10 It’s empowering to be able to play around with a config file, or to tweak the order of a server update to perfection, over and over again, with no fear of breaking an important server.
    [Show full text]
  • (Php)Storming Wordpress a Remote Debugging Experience Introduction
    (Php)Storming WordPress A remote debugging experience Introduction / Andrea Fuggetta / Senior software engineer at Ndevr, Inc. - https://ndevr.io/ / Some of the projects I worked on: About Us / Since 2015 / Distributed / 50% Located in NY/NJ Metro / Average experience over 15 years Outline / Tools and software / Setting up Xdebug / Setting up PhpStorm / Setting up your terminal / Let’s code! – Debugging case scenarios: / WordPress theme / WP-CLI application / PHPUnit test / References / Q&A Tools and software / PhpStorm / Google Chrome w/ Xdebug helper / Terminal / Vagrant / Xdebug / PHPUnit / WP-CLI Setting up Xdebug / Info on https://xdebug.org/docs/install / Installation on Mac OSX via Homebrew: # brew install <php-version>-xdebug / Installation on Linux via apt-get: # sudo apt-get install <php-version>-xdebug / Php.ini: Add: zend_extension="/path-to/xdebug.so" [Xdebug] xdebug.remote_enable=1 xdebug.remote_port=“9000” Debugging / Breakpoint: line break where an application suspends execution allowing you to examine data / Step-over: runs code in current line and moves to next code statement / Step-into: moves into functions/methods if any are present in current line / Step-out: runs current function/method and returns to previous execution point Listens for connections Setting up PhpStorm / Enable external connections and set correct port / More info can be found at https://www.jetbrains.com/help/phpstorm/2016.2/configuring-xdebug.html Setting up PhpStorm / Zero-configuration debugging / Create a new remote debug configuration / Important
    [Show full text]
  • Prioritizing Pull Requests
    Prioritizing pull requests Version of June 17, 2015 Erik van der Veen Prioritizing pull requests THESIS submitted in partial fulfillment of the requirements for the degree of MASTER OF SCIENCE in COMPUTER SCIENCE by Erik van der Veen born in Voorburg, the Netherlands Software Engineering Research Group Q42 Department of Software Technology Waldorpstraat 17F Faculty EEMCS, Delft University of Technology 2521 CA Delft, the Netherlands The Hague, the Netherlands www.ewi.tudelft.nl www.q42.com c 2014 Erik van der Veen. Cover picture: Finding the pull request that needs the most attention. Prioritizing pull requests Author: Erik van der Veen Student id: 1509381 Email: [email protected] Abstract Previous work showed that in the pull-based development model integrators face challenges with regard to prioritizing work in the face of multiple concurrent pull requests. We identified the manual prioritization heuristics applied by integrators and ex- tracted features from these heuristics. The features are used to train a machine learning model, which is capable of predicting a pull request’s importance. The importance is then used to create a prioritized order of the pull requests. Our main contribution is the design and initial implementation of a prototype service, called PRioritizer, which automatically prioritizes pull requests. The service works like a priority inbox for pull requests, recommending the top pull requests the project owner should focus on. It keeps the pull request list up-to-date when pull requests are merged or closed. In addition, the service provides functionality that GitHub is currently lacking. We implemented pairwise pull request conflict detection and several new filter and sorting options e.g.
    [Show full text]
  • How to Communicate with Developers
    How to Communicate with Developers Employer branding, job listings, and emails that resonate with a tech audience Developers are one of the most in-demand groups of employees these days. And guess what, they noticed this as well: Countless approaches by potential employers, sometimes several messages a day through Linkedin, and a few desperate recruiters even cold calling. So those with technical talents are by no means oblivious to the talent shortage. The good news is that they don’t just use this bargaining power to simply negotiate the highest salaries and most outrageous benefits. Instead, developers are intrinsically motivated. They are looking for the right place to work. Your challenge in this noisy jobs market is to clearly communicate what defines your employer brand, what work needs doing, and, ultimately, who might be the right fit for the role. All of this is easier said than done. Because tech recruiting is a complex business, it is easy to not see the forest for the trees. This guide will help you decide where to start or what to fix next. In the first and more general part, we would like you to take a step back. Before we even think about how to package our job opening and approach a candidate with our offer, we look at what information and knowledge you should gather about your tech team and the company at large. Following that, we will take a practical look at how to write and talk about your company and the role, with a special focus on the job listings and a recruiting emails as a first introduction.
    [Show full text]