International Online Hiring Tournament - Java, .

Net, Ruby on Rails, PHP Software Engineering Managers ($100K/year),

November 11th
We're running our Online Hiring Tournament on November the 11th to hire remote Software Engineering
Managers who demonstrate outstanding managerial skills as well as the technical background to deeply understand the
code their teams are developing.
Crossover (www.crossover.com) is an Austin, TX based HR and Technology company finding the top 1% of talent around
the world and introducing them to US software enterprises. The company also has a unique technology enabling full time
remote work from wherever you live.
We are searching for world-class Software Engineering Managers who will be expected to demonstrate both a mastery
of the technical skills associated with the projects at hand, as well as the managerial ability to motivate, build, and
monitor your team. Specifically, you will be responsible for overseeing from 4 to 6 teams of 3 to 4 individuals. You will
own the
 process of breaking specifications created by the product management team into clear tasks and
timelines, as well as
 assembling the results into high value, reusable components.
 Under your leadership, we expect to see consistent improvement in both static code quality metrics
and weekly production.

More important information about the position we are hiring forhere: Software Engineering manager.
The tournament for the role Software Engineering Managers will be limited to candidates with following qualifications:
 Proven managerial skills with at least 5 years of experience managing multiple teams
Experience with Cloud architecture and DevOps
At least 5 years of experience in hands-on Java and/or .Net and/or Ruby on Rails and/or PHP programming
 Proficiency in Agile, SDLC, or SLA
 Proficiency in AWS and TDD is desired but not mandatory
 English communication skills

This 5 hours-event will include live testing in a transparent, gamified and competitive process. We will conduct all
testing for our $100K/yr valued full time Software Engineering Managers.

This gamified concept was tested by Crossover in Warsaw, Cluj-Napoca, Krakow, Lviv, Lahore, Istanbul, Cairo and Karachi
before, where we hired over 100 amazing specialists from around the world. Now it's global! All you have to do is to
register and follow the test instructions. It will be 5 hours so get ready!
We recommend you to attend the tournament instead of applying online, as our tournament process will be much faster
(approximately 5 hours instead of a multi-day testing process).
How can I get more information?
We will organize an Information Webinar before the tournament for all interested candidates
Webinar address and test platform link will be sent to confirmed candidates.
Register at the green button, where we'll ask you some brief questions about your background.
After answering the questions your registration will be almost completed. If everything is OK you will receive the
confirmation letter along with the detailed guidelines for the next steps you should take before the tournament.

The development management role is the role whose purpose it is to keep the vision on track. This is much like a
CEO, who sets the vision for an organization. While it's the project manager's goal to get the project to the finish line,
it is the Development Manager 's responsibility to look ahead to make sure that the finish line is the right finish line to
be reaching. While the project management position is a management position, the development manager role is a
leadership position.

TEST
 Multiple-choice test
 *Coding or project challenges * (featuring real-time scoring—see how you rank against your peers)
 30-minute technical interview
 Hiring decision: If you receive and accept a job offer, you may be eligible for a hiring bonus or other prizes!
Given this hastily coded news publishing site - please perform the following:

1. Functional testing + Testing suite

a. Functional testing is a quality assurance (QA) process and a type of black-box testing that bases
its testcases on the specifications of the software component under test.
2. Code reviews + Tools:
a. https://www.quora.com/What-are-the-best-code-review-tools
3. Coding two new modules +
4. Unit tests for both existing code and your new module +
a. http://www.softwaretestinghelp.com/unit-testing-tools/
5. Documentation:
a. https://www.process.st/software-documentation/
6. A video demo

TOOLS TO PREPARE:

1. JAVA
a. IDE: NetBeans. IntelliJ. Eclipse. Android Studio
b. Development standards/best practices
c. Java reference site
d. Best JAVA Code Samples
e. JAVA Developer standards & Methodology
f. Patterns and Code generation
g. Unit testing? nUnit.
h. Code review tools/plugins - TOP
i. Top sw engineer tools
j. Documentation generation tools/plugins

2. .NET
a. IDE: Visual Studio
b. Development standards/best practices
c. Microsoft Azure
d. .NET reference site
e. .NET Code Samples
f. .NET Developer standards & Methodology
g. Patterns and Code generation
h. Unit testing? nUnit.
i. Code review tools/plugins - TOP
j. Top sw engineer tools
k. Documentation generation tools/plugins

3. PHP
 IDE: PHP Storm, NetBeans
a. PHP Frameworks: Laravel, Code Igniter , Symphony, Zend, Yii 2, CakePHP
b. PHP Developer standards & Methodology and Best Practices
i. Standards
ii. Methodology
iii. Best Practices
c. References:
i. Quick sheets
ii. Reference book(s)
iii. Libraries
iv. Code Samples
v. PHP Scripts – Jabbers,
 vi. Templates
d. Patterns and Code generation
i. CodeCharge, CodeSmith, PHP Generator
 Unit testing? PHPUnit – The PHP Testing Framework
 Code review tools/plugins – PHP_CodeSniffer
e. Top sw engineer tools
f. Documentation generation tools/plugins
g. PHP accelerator?
i.
h. PHP Template Engine?
i.
4. AWS – Amazon Web Services
5. GitHub
6. PMP, Prince 2, ITIL…?
7. Agile…?
8. Video demo tool – TOP
9. Playbook?

10. Mikrofon. Skype. Video. Software.

11. https://www.qasymphony.com/blog/100-plus-best-software-testing-tools/
https://dzone.com/articles/top-10-automated-software-testing-tools
https://www.quora.com/What-are-the-best-code-review-tools
http://www.discoversdk.com/blog/code-review-tools-you-should-get-to-
know?utm_medium=blog&utm_campaign=aaron&utm_source=quora
https://developer.android.com/training/testing/unit-testing/index.html
https://www.process.st/software-documentation/

Agile
Agile software development describes a set of values and principles for software development under which
requirements and solutions evolve through the collaborative effort of self-organizing cross-functional teams.
 It advocates adaptive planning, evolutionary development, early delivery, and continuous improvement, and
it encourages rapid and flexible response to change.
 These principles support the definition and continuing evolution of many software development methods.
 The Manifesto for Agile Software Developmentis based on twelve principles:

1. Customer satisfaction by early and continuous delivery of valuable software.

2. Welcome changing requirements, even in late development
3. Working software is delivered frequently (weeks rather than months)
4. Close, daily cooperation between business people and developers
5. Projects are built around motivated individuals, who should be trusted
6. Face-to-face conversation is the best form of communication (co-location)
7. Working software is the primary measure of progress
8. Sustainable development, able to maintain a constant pace
9. Continuous attention to technical excellence and good design
10. Simplicity—the art of maximizing the amount of work not done - is essential
11. Best architectures, requirements, and designs emerge from self-organizing teams
12. Regularly, the team reflects on how to become more effective, and adjusts accordingly

SDLC
 In software engineering, a software development process is the process of dividing software
development work into distinct phases to improve design, product management, and project
management. It is also known as a software development life cycle. The methodology may include the
pre-definition of specific deliverables and artifacts that are created and completed by a project team to
develop or maintain an application.[1]

Most modern development processes can be vaguely described as agile. Other methodologies
include waterfall, prototyping, iterative and incremental development, spiral development, rapid
application development, and extreme programming.
SLA
A service-level agreement (SLA) is defined as an official commitment that prevails between a service
provider and a client. Particular aspects of the service – quality, availability, responsibilities – are
agreed between the service provider and the service user.[1] The most common component of SLA is
that the services should be provided to the customer as agreed upon in the contract.
AWS - Amazon web services
TDD
Test-driven development (TDD) is a software development process that relies on the repetition of a
very short development cycle: first the developer writes an (initially failing) automated test case that
defines a desired improvement or new function, then produces the minimum amount of code to pass
that test, and
DevOps
DevOps is the combination of cultural philosophies, practices, and tools that increases an
organization’s ability to deliver applications and services at high velocity: evolving and improving
products at a faster pace than organizations using traditional software development and
infrastructure management processes.
Cloud architecture
Cloud computing architecture refers to the components and subcomponents required
for cloud computing. These components typically consist of a front end platform (fat client, thin client,
mobile device), back end platforms (servers, storage), a cloud based delivery, and a network (Internet,
Intranet, Intercloud).

Software Engineering Manager $50/hr

Job Description
If you are an elite Software Engineering Manager eager to gain unprecedented visibility to the top technology companies throughout the globe, employ your technical and managerial skills to
oversee cutting-edge software in a high-intensity environment, and earn $100,000 USD per year while working from virtually anywhere on the planet, this job is for you.

The Company:

Crossover is a well-funded startup that has developed a unique way to find, curate and manage the top 1% of global talent – and connect them to medium and large businesses. We are
experiencing rapid growth within the companies we currently serve and are increasing our staff to expand our business.

Brick and mortar offices are history. The future of our global workforce will consist of teams collaborating from every corner of the world. Our platform connects customers to the world’s best
talent for both technical and non-technical contracting. But we don’t just find the best; we also provide the software tools, training, and expert management to ensure success for long-term
growth.

Job Description:
Crossover is looking for Software Engineering Managers who demonstrate outstanding managerial skills
as well as the technical background to deeply understand the code their teams are developing. You will
be expected to demonstrate both a mastery of the technical skills associated with the projects at hand, as
well as the managerial ability to motivate, build, and monitor your team. Specifically, you will be
responsible for overseeing from 4 to 6 teams of 3 to 4 individuals. You will own the process of breaking
specifications created by the product management team into clear tasks and timelines, as well as
assembling the results into high value, reusable components. Under your leadership, we expect to see
consistent improvement in both static code quality metrics and weekly production.

A successful Software Engineering Manager at Crossover will demonstrate the following qualities:
 Ruthless commitment to impeccable code quality
 Deep understanding of a wide range of the latest technologies and architectural approaches
 Advanced proficiency in one or more core programming languages (Java or C#), related frameworks,
and best practices
 The ability to make appropriate technical decisions, review design and code, and ensure best technical
practices
 Commitment to hands-on engagement as an individual within the team, despite managerial status
 Willingness to embrace iterative development as the means for building seamless products
 Perfectionism: knowing how a job should be done and not stop until it’s done correctly
 Exceptional ability to effectively motivate and manage teams of individuals
 Commitment to increasing efficiency in the workplace by continuously automating parts of the
software engineering process
 Excellent remote management skills (you will be using Skype, GoToMeeting, Google Docs, etc.)

Required Skills and Experience:

A successful Software Engineering Manager at Crossover will demonstrate the following qualifications:
 Bachelor's degree in Computer Science, Computer Engineering, or Electrical Engineering
 Proven managerial skills with at least 5 years of experience managing multiple teams
 Experience with Cloud architecture and DevOps
 At least 5 years of experience in hands-on Java and/or .NET programming
 Proficiency in Agile, SDLC, or SLA
 Proficiency in AWS and TDD is desired but not mandatory
 Outstanding English communication skills

Total compensation: $50/hr for 40 productive hours per week

Location: Global (remote)

We’re one of the few legitimate companies offering high-paying jobs that are 100% remote, work from
home. You never have to fight traffic to the office again and you have the freedom to choose when and
where you put in your 40 hours to be most effective each week.
To qualify, please provide a resume/CV demonstrating the required experience and skills. From there, to
help us find the top 1% of talent, there will be a series of interviews and online examinations. We realize
these are challenging and can require a decent amount of time so we thank you in advance for your
efforts.

Top IDE for PHP Projects

 PHPStorm
1. Netbeans
 2. Aptana Studio
3. Eclipse
Top Code Editors for PHP Projects
1. Sublime Text
2. Visual Studio Code
3. Atom
 Notepad++
4. Coda
5. Brackets
6. SlickEdit
7. jEdit
8. Programmer’s Notepad
9. Komodo Edit
10. RJ TextEd
PHPStorm

 Platform(s): Microsoft Windows, Mac OS X, Linux

 Supported Languages: PHP 5.3, 5.4, 5.5, 5.6 and 7.0, HTML and JavaScript
 Price: USD 199 for the first year, Subsequent usage costs less.
 More Information: Code quality analysis, PHPUnit tests, GitHub
 Visit: PHPStorm
Netbeans
  Platform(s): Microsoft Windows, Mac OS X, Linux, Solaris
 Supported Languages: Java ME & SE, JavaScript, HTML5, PHP, C/C++, XML, Groovy, Javadoc, JSP
 Price: FREE (CDDL or GPLv2)
 More Information: Integration of Subversion, Mercurial, and Git, NetBeans Profiler
 Visit: Netbeans
Aptana Studio

 Platform(s): Microsoft Windows, Mac OS X, Linux, Plugin for Eclipse

 Supported Languages: JavaScript, HTML5, CSS3, DOM, CSS, Ruby on Rails, PHP, Python, Perl
 Price: FREE (GPL)
 More Information: Open source, deployment wizard for RoR.
 Visit: Aptana Studio
Eclipse
  Platform(s): Microsoft Windows, Mac OS X, Linux, Solaris
 Supported Languages: Ada, ABAP, C, C++, COBOL, D, Fortran, Haskell, Java, JavaScript, Julia,
Lasso, Lua, NATURAL, Perl, PHP, Prolog, Python, R, Ruby, Ruby on Rails, Rust, Scala, Clojure,
Groovy, Scheme, and Erlang, LaTeX, Mathematica.
 Price: FREE (Eclipse Public License)
 More Information: Rich Client Platform, supports Tomcat, GlassFish and other servers, Web
Tools Platform.
 Visit: Eclipse
Sublime Text

 Platform(s): Microsoft Windows, Mac OS X, Linux

 Supported Languages: All popular languages
 Price: USD 70/license
 More Information: Package Manager
 Visit: Sublime Text
Visual Studio Code
  Platform(s): Microsoft Windows, Mac OS X, Linux
 Supported Languages: Batch, C++, Clojure, CoffeeScript, DockerFile, Elixir, F#, Go, Pug template
language, Java, HandleBars, Ini, Lua, Makefile, Objective-C, Perl, PowerShell, Python, R, Razor,
Ruby, Rust, SQL, Visual Basic, XML
 Price: FREE (MIT License)
 More Information: GitHub support, code refactoring, debugger
 Visit: Visual Studio Code
Atom

 Platform(s): Microsoft Windows, Mac OS X, Linux

 Supported Languages: HTML, CSS, Less, Sass, GitHub Flavored Markdown, C/C++, C#, Go, Java,
Objective-C, JavaScript, JSON, CoffeeScript, Python, PHP, Ruby, Ruby on Rails, shell script,
Clojure, Perl, Git, Make, Property List (Apple), TOML, XML, YAML, Mustache, Julia & SQL
 Price: FREE (MIT License)
 More Information: Open source, built-in Package Manager, Themes.
 Visit: Atom
Notepad++
  Platform(s): Microsoft Windows,
 Supported Languages: Ada, asp, Assembly, AutoIt, Batch, C, C++, C#, Caml, Cmake, COBOL,
CoffeeScript, CSS, D, Diff, Flash ActionScript, Fortran, Gui4CLI, Haskell, HTML, INNO, Java,
JavaScript, JSP, KiXtart, LISP, Lua, Makefile, Matlab, MS-DOS, INI file, NSIS, Normal Text File,
Objective-C, Pascal, Perl, PHP, PostScript, PowerShell, Properties, Python, R, Resource file, Ruby,
Shell, Scheme, Smalltalk, SQL, TCL, TeX, Visual Basic, VHDL, Verilog, XML, YAML
 Price: FREE (GPL)
 More Information: Open source, Macro recording and playback, User Defined Syntax
Highlighting and Folding
 Visit: Notepad++

The following table lists the various Web Template Engines used in Web template systems and
a brief rundown of their features. The content here is a work in progress.
Erro
Cond Evalu Nat
Engine rs
Vari Fun ition Loo ation Assig i1 ural Inhe
(imple Licen Incl and
Languages abl ctio al pin (lang nme 8 tem ritan
mentati se udes exce
es ns inclu g uage nt n plat ce
on) ptio
sion ) es
ns
Yes Y
GPL
Amber C++ Yes Yes Yes Yes Yes Yes Yes (C++ e No No
v 3.0
) s
Apac
Apache he
Java, C# Yes Yes Yes Yes Yes Yes Yes Yes No
Velocity Licen
se
action4J Apac
Java Yes No Yes Yes Yes No Yes Yes
AVA he
 Erro
Cond Evalu Nat
Engine rs
Vari Fun ition Loo ation Assig i1 ural Inhe
(imple Licen Incl and
Languages abl ctio al pin (lang nme 8 tem ritan
mentati se udes exce
es ns inclu g uage nt n plat ce
on) ptio
sion ) es
ns
Licen
se
ASP.NET Prop
(Micros C#, VB.NET rieta Yes Yes Yes Yes Yes Yes Yes Yes
oft) ry
ASP.NET GNU
C# Yes Yes Yes Yes Yes Yes Yes Yes
(Mono) LGPL
GPL
AutoGe N
C licen Yes Yes Yes Yes Yes Yes Yes Yes Yes
n o
se
Apac
Y
he
Beard Scala No No Yes Yes Yes No No No e No Yes
Licen
s
se
MIT Y
Blade PHP Licen Yes Yes Yes Yes Yes No Yes Yes e No Yes
se s
PHP 5, PHP(C- BSD-
Blitz Yes Yes Yes Yes Yes No Yes Yes
module) like
Apac
he
Carrot Java Yes Yes Yes Yes Yes No Yes Yes Yes
Licen
se
Casper Java, JavaScript MIT Yes Yes Yes Yes Yes Yes Yes Yes
Cheetah BSD
Templat Python licen Yes Yes Yes Yes Yes Yes Yes Yes Yes
e ses
open
Chip
-
Templat PHP, Perl Yes Yes Yes Yes Yes No Yes No
sour
e Engine
ce?
Chunk Y
open
Templat Java Yes Yes Yes Yes Yes No Yes Yes e Yes Yes
-
es s
 Erro
Cond Evalu Nat
Engine rs
Vari Fun ition Loo ation Assig i1 ural Inhe
(imple Licen Incl and
Languages abl ctio al pin (lang nme 8 tem ritan
mentati se udes exce
es ns inclu g uage nt n plat ce
on) ptio
sion ) es
ns
sour
ce
LLGP
CL-EMB Common Lisp Yes Yes No No Yes Yes Yes No
L
Classic
CodeCh Prop Y
ASP, C#, VB.NET, PH
arge rieta Yes Yes Yes Yes Yes Yes Yes No e Yes
P, Perl, Java/JSP, Col
Studio ry s
dFusion
Prop Y
ColdFusi
CFML, CFScript rieta Yes Yes Yes Yes Yes Yes Yes Yes e Yes Yes
on
ry s
MIT
N
Cottle C# Licen Yes Yes Yes Yes Yes No Yes No No
o
se
csharpt
New
emplate C# Yes No No No No No No No
BSD
s
C, C++, Perl, PHP, Py BSD-
CTPP Yes Yes Yes Yes Yes No No Yes
thon like
Y
GNU
dbPager C++ Yes Yes Yes Yes Yes Yes Yes Yes e
GPL
s
MIT
Dermis Classic ASP Licen Yes No Yes No Yes No Yes No
se
Y
BSD-
Django Python Yes Yes Yes Yes Yes Yes Yes Yes e Yes
like
s
DTL::Fas
t (port
MIT
of Djang N
Perl Licen Yes Yes Yes Yes Yes No Yes Yes Yes
o o
se
templat
es)
 Erro
Cond Evalu Nat
Engine rs
Vari Fun ition Loo ation Assig i1 ural Inhe
(imple Licen Incl and
Languages abl ctio al pin (lang nme 8 tem ritan
mentati se udes exce
es ns inclu g uage nt n plat ce
on) ptio
sion ) es
ns
Apac
Djolt- he
Objective-C Yes No No No Yes No No No
objc Licen
se
DNA MIT
Templat Javascript Licen Yes No No No Yes No Yes No Yes No
e se
GNU Yes
Dwoo PHP5.3 / PHP7 Yes Yes Yes Yes Yes Yes Yes Yes
LGPL (PHP)
Dylan
unkn No
Server Dylan Yes Yes Yes Yes No No No
own ?
Pages
Yes
MIT
(Coff
ECT JavaScript Licen Yes Yes Yes Yes Yes Yes Yes Yes
eeScr
se
ipt)
GPL
/ Ru
eRuby Ruby by Yes Yes Yes Yes Yes Yes Yes Yes
Licen
se
Y
FigDice PHP 5 GPL Yes Yes Yes Yes Yes Yes Yes Yes e Yes
s
Apac
Y
FreeMar he
Java Yes Yes Yes Yes Yes Yes Yes Yes e No No
ker Licen
s
se
Genshi
(templat Yes Y
BSD-
ing Python Yes Yes Yes Yes Yes (Pyth Yes Yes e Yes
like
languag on) s
e)
 Erro
Cond Evalu Nat
Engine rs
Vari Fun ition Loo ation Assig i1 ural Inhe
(imple Licen Incl and
Languages abl ctio al pin (lang nme 8 tem ritan
mentati se udes exce
es ns inclu g uage nt n plat ce
on) ptio
sion ) es
ns
Go BSD Y
templat Go Licen Yes Yes Yes Yes Yes Yes Yes Yes e Yes No
es se s
Google- BSD
ctempla C++ Licen Yes No Yes Yes Yes No No No
te se
Grantle
e Y
Templat C++/Qt LGPL Yes Yes Yes Yes Yes Yes Yes Yes e Yes
e s
System
Apac
Yes
he
GvTags Groovy Yes Yes Yes Yes Yes (Groo Yes No
Licen
vy)
se
MIT
H2o PHP, Ruby Licen Yes Yes Yes Yes Yes No Yes Yes
se
MIT
Yes N
HAH PHP Licen Yes Yes Yes Yes Yes Yes No Yes No
(PHP) o
se
MIT Yes
Haml Ruby, PHP(WIP) Licen Yes Yes Yes Yes Yes (Ruby Yes Yes
se )
Hamlets Java BSD Yes Yes Yes Yes Yes No Yes Yes
MIT
Handleb N
JavaScript Licen Yes Yes Yes Yes Yes No No Yes Yes No
ars o
se
Hyperkit
open
PHP/XM
-
L PHP, XML Yes Yes Yes Yes Yes Yes Yes Yes
sour
Templat
ce
e Engine
 Erro
Cond Evalu Nat
Engine rs
Vari Fun ition Loo ation Assig i1 ural Inhe
(imple Licen Incl and
Languages abl ctio al pin (lang nme 8 tem ritan
mentati se udes exce
es ns inclu g uage nt n plat ce
on) ptio
sion ) es
ns
Apac
Histone
PHP, Java, JavaScrip he N
templat Yes Yes Yes Yes Yes No Yes Yes Yes Yes
t Licen o
e Engine
se
HTML-
N
TEMPLA Common Lisp BSD Yes No Yes No Yes No No No
o
TE
Apac
he
HTTL Java Yes Yes Yes Yes Yes Yes Yes Yes
Licen
se
CDD
L+
JavaServ
Java GPL Yes Yes Yes Yes Yes Yes Yes Yes
er Pages
Licen
se[1]

jin-
templat Java, PHP LGPL Yes No No No No No Yes No
e
Yes
Jinja Python BSD Yes Yes Yes Yes Yes (Pyth Yes No
on)
Yes Y
Jinja2 Python BSD Yes Yes Yes Yes Yes (Pyth Yes Yes e Yes Yes
on) s
Prop
JScore PHP + JS rieta Yes Yes Yes Yes Yes Yes Yes Yes
ry
Thro
ugh
BSD-
Kalahari Python Yes Yes inhe No Yes No Yes Yes
like
ritan
ce
 Erro
Cond Evalu Nat
Engine rs
Vari Fun ition Loo ation Assig i1 ural Inhe
(imple Licen Incl and
Languages abl ctio al pin (lang nme 8 tem ritan
mentati se udes exce
es ns inclu g uage nt n plat ce
on) ptio
sion ) es
ns
Kid
(templat Yes
ing Python MIT Yes Yes Yes Yes Yes (Pyth Yes Yes
languag on)
e)
MIT
Liquid Ruby and others Licen Yes Yes Yes Yes Yes No Yes Yes No
se
Lofn Common Lisp MIT Yes Yes Yes Yes Yes Yes Yes No
Yes Y
Lucee CFML LGPL Yes Yes Yes Yes Yes (CFM Yes Yes e Yes Yes
L) s
Yes
Mako Python MIT Yes Yes Yes Yes Yes (Pyth Yes Yes Yes Yes
on)
Mars- MIT
Templat PHP 5 Licen Yes No No Yes Yes No No No
er se
MiniTe GNU
PHP, Java, VB.NET Yes Yes Yes Yes Yes No No No?
mplator LGPL
MIT
mTempl N
PHP Licen Yes Yes Yes Yes Yes Yes Yes Yes Yes
ate o
se
Yes
MIT Y
Mustac (for
30+ languages Licen Yes Yes Yes Yes No No Yes e Yes No
he eac
se s
h)
MIT
nTPL node.js, JavaScript Licen Yes Yes Yes Yes Yes Yes Yes Yes
se
Open
Power BSD- Yes
PHP 5 Yes Yes Yes Yes Yes Yes Yes
Templat like (PHP)
e
 Erro
Cond Evalu Nat
Engine rs
Vari Fun ition Loo ation Assig i1 ural Inhe
(imple Licen Incl and
Languages abl ctio al pin (lang nme 8 tem ritan
mentati se udes exce
es ns inclu g uage nt n plat ce
on) ptio
sion ) es
ns
Y
GNU
Obyx C++ Yes Yes Yes Yes Yes Yes Yes Yes e Yes
GPL
s
Y
New
Pebble Java Yes Yes Yes Yes Yes Yes Yes Yes e No Yes
BSD
s
open
- Yes
Outline PHP 5 Yes Yes Yes Yes Yes Yes Yes?
sour (PHP)
ce
MIT
Yes
pHAML PHP Licen Yes Yes Yes Yes Yes Yes Yes?
(PHP)
se
PHP Y
PHP PHP Licen Yes Yes Yes Yes Yes Yes Yes Yes e Yes No
se s
MIT
Pug JavaScript Licen Yes Yes Yes Yes
se
PURE
Unobtru
MIT
sive
JavaScript Licen Yes Yes Yes Yes Yes Yes Yes Yes Yes
Renderi
se
ng
Engine
Yes
pyratem
Python MIT Yes Yes Yes Yes Yes (Pyth Yes No Yes
p
on)
MIT
QueryTe
PHP 5, JavaScript Licen Yes Yes Yes Yes Yes Yes Yes Yes
mplates
se
GNU Yes
RainTPL PHP Yes Yes Yes Yes Yes Yes Yes
LGPL (PHP)
 Erro
Cond Evalu Nat
Engine rs
Vari Fun ition Loo ation Assig i1 ural Inhe
(imple Licen Incl and
Languages abl ctio al pin (lang nme 8 tem ritan
mentati se udes exce
es ns inclu g uage nt n plat ce
on) ptio
sion ) es
ns
Apac
Y
he
Razor C#, F#, VB.NET Yes Yes Yes Yes Yes Yes Yes Yes e Yes Yes
Licen
s
se
Apac
Y
he Yes
Rythm Java Yes Yes Yes Yes Yes Yes Yes e Yes Yes
Licen (Java)
s
se
Apac
Yes
he
Scalate Scala, Java Yes Yes Yes Yes Yes (Scala Yes Yes
Licen
)
se
GNU N
Scurvy PHP Yes No Yes Yes Yes No No Yes Yes
GPL o
Y
Simphpl GNU Yes e
PHP Yes Yes Yes Yes Yes No Yes No
e LGPL (PHP) s
?
Y
GNU Yes
Smarty PHP Yes Yes Yes Yes Yes Yes Yes? e Yes
LGPL (PHP)
s
StampT N
PHP BSD Yes No No No No No No No Yes No
E o
StringTe Java (native), Pytho
BSD Yes No Yes Yes Yes No
[2] No No No
mplate n, C#
SUIT Y
GNU
Framew PHP, Python Yes Yes Yes Yes Yes Yes Yes Yes e
LGPL
ork s
Templat
e open
Y
Attribut -
Python, PHP 5 Yes Yes Yes Yes Yes Yes Yes Yes e
e sour
s
Languag ce
e
 Erro
Cond Evalu Nat
Engine rs
Vari Fun ition Loo ation Assig i1 ural Inhe
(imple Licen Incl and
Languages abl ctio al pin (lang nme 8 tem ritan
mentati se udes exce
es ns inclu g uage nt n plat ce
on) ptio
sion ) es
ns
open
Y
-
Twital PHP 5.3 Yes Yes Yes Yes Yes Yes Yes Yes e
sour
s
ce
Templat GNU Yes
PHP 5 Yes Yes Yes Yes Yes Yes Yes?
e Blocks GPL (PHP)
open
Templat - Yes
Perl, Python Yes Yes Yes Yes Yes Yes Yes
e Toolkit sour (Perl)
ce
Apac
Y
Thymele he
Java Yes Yes Yes Yes Yes Yes Yes Yes e Yes No
af Licen
s
se
Y
TinyBut GNU
PHP Yes Yes Yes Yes Yes Yes Yes Yes e Yes
Strong LGPL
s
Y
Tonic PHP BSD Yes Yes Yes Yes Yes Yes No Yes e Yes Yes
s
Apac
Any
he
Yes Yes Yes Yes Yes Yes
[
Toupl with OOPand String [3] [3] [3] [3] [3] Yes[3] Yes [3]

Licen 3]

class support
se
Y
Twig PHP BSD Yes Yes Yes Yes Yes No Yes Yes e No Yes
s
Apac
Yes Y
he
Twirl Scala Yes Yes Yes Yes Yes (Scala Yes e
Licen
) s
se
uBook
N
Templat PHP GPL Yes No No No Yes No Yes Yes Yes
o
e
 Erro
Cond Evalu Nat
Engine rs
Vari Fun ition Loo ation Assig i1 ural Inhe
(imple Licen Incl and
Languages abl ctio al pin (lang nme 8 tem ritan
mentati se udes exce
es ns inclu g uage nt n plat ce
on) ptio
sion ) es
ns
Artis
vlibTem tic
PHP Yes Yes Yes Yes Yes No No No
plate Licen
se
Apac
he
WebMa
Java Licen Yes Yes Yes Yes Yes Yes Yes Yes
cro
se, G
PL
new
ZeniTPL PHP Yes No No No Yes No Yes No
BSD
Ope
n N
BabaJS JavaScript Yes Yes Yes Yes Yes Yes Yes Yes No
Sour o
ce
GPL N
Rage JavaScript Yes Yes Yes Yes Yes Yes Yes Yes Yes
v 3.0 o
GPL
JavaScript, PHP, v
Y
Planner Java, ASP.NET, 3.0,
Yes Yes Yes Yes Yes Yes Yes Yes e Yes Yes
Fw Python, Perl, Ruby, Prop
s
Node.js, and more rieta
ry
N
Fenom PHP ? N/A N/A N/A N/A N/A N/A N/A N/A
/A
N/A N/A

Eval Erro
Con Nat
Engine uatio rs
Var Fun Incl ditio Lo Assi i1 ural Inhe
(imple Lice n and
Languages iabl ctio ude nal opi gnm 8 tem ritan
mentat nse (lang exce
es ns s inclu ng ent n plat ce
ion) uage ptio
sion es
) ns
LEGEND:

 Engine (implementation) = engine name

 Languages = implementation language of the engine (not the template script language)
 License = Software license agreement
 Platform = Computing platform
 Variables = script language power to use variables
 Functions = script language power to use functions
 Includes = script language power include external files
 Conditional inclusion = script language power to conditional includes
 Looping = script language power to do loops (for, while) or recursion
 Evaluation (language) = script language power to do "eval command" (to the
implementation language)
 Assignment = set names and references to sub-templates (?)
 Errors and exceptions = engine output script errors.
 i18n = Internationalization and localization feature
 Natural templates = the template can be a document as valid as the final result, the engine
syntax doesn't break the document's structure
 Inheritance = Supports the ability to inherit a layout from a parent template, separately
overriding arbitrary sections of the parent template's content.

For inclusion above

 Paperclip (JavaScript/DOM/Node template engine) - fast, reactive templates.
 Embedded Perl(Mojolicious: Embedded Perl) - Embedded Perl is a powerful templating
engine for use with the Mojolicious Web Framework. It supports variables, functions,
includes, conditional inclusion, looping, evaluation, assignment, exceptions, i18n, natural
templates, and inheritance. [4]

 erlydtl erlydtl django for erlang

 Latte, template engine originating from Nette Framework
 Foil
 PH7 Engine
 Haanga
 TPLN
 Volt Volt template engine for use with Phalcon Framework
 tiny_template, simple runtime C++ templating
 jtwig, Java implementation of the Twig template engine

Now, let’s take a look at 15 such tools:

1. JDK ( Java Development Kit)

I know what you are going to say, “of course you need a JDK to get started with Java”; but the
fact is there is nothing obvious in programming. If you plan on developing Java based applets
and applications, your first need to get yourself a tool like JDK, which includes the necessary
Java Complier, the Java Runtime Environment, and the Java APIs. It will help you get started
with Java.
2. Eclipse IDE

Ask experienced Java developers about their favorite Java Integrated Development
Environment (IDE) and quite a number of them will point to Eclipse. Eclipse provides much
needed assistance for code completion, refactoring and syntax checking. It also offers
something called the Java Development Tools project (JDT) that provides a range of tool plugin-
ins to help develop all kinds of Java applications.

The real advantage of this IDE, however, is that it allows developers to combine language
support, for e.g. it also offers a C/C++ and PHP IDE. This makes it a one stop resource for Java
development.

3. NetBeans

This is another IDE that offers a comprehensive array of features such as converters, editors
and code analyzers that help you come up with applications that implement the latest Java
technologies. The range of tools is extensive and the people behind this IDE are making
continuous improvements to it. You also get the benefit of static analysis tools that help you
write bug free code.

4. IntelliJ IDEA 13.1

This one calls itself the ‘most intelligent Java IDE’ going around. You can only know if this
actually is the case if you use it, but there is no doubt that it does help developers come up with
innovative Java solutions. It has features that help boost productivity such as ‘Smart Code
Completion’ and ‘On-the-fly Code Analysis’; it also offers advanced support for web and mobile
development and a whole lot more. So, try it out.

5. Oracle JDeveloper

If you are looking for a free IDE that helps you build a reliable Service Oriented Architecture
with Java, or Java Enterprise Edition applications, there is nothing better than JDeveloper. It
supports the full development life cycle, which means you are assured of a Java solution you
can justifiably be proud of.

6. JUnit

This is a unit testing framework that helps developers write and run tests. But there is an
essential difference between JUnit and similar frameworks available on the market. You can
test one block of code at a time rather than waiting for the module to be completed before you
run a test. You can actually ‘test and then code’, meaning you have very little doubt about the
final functionality of an application.

7. Apache ANT™
With the ANT™, you get the benefit of working with a tool by the Apache Software Foundation.
This one is an open source tool whose greatest advantage is its simplicity. One key aspect of
programming that gets the developer’s goat is handling complex repetitive tasks. With ANT™,
you can automate such tasks. This is just one of the many features this tool simplifies.

8. JRat (Java Runtime Analysis Toolkit)

If you want to measure the application’s performance, JRat is the analysis toolkit you must use.
With this tool, you can identify potential problem areas that can impact application
performance.

9. Apache JMeter™

This is another tool from the Apache stable. It is a testing tool that will measure functional
behavior and also the performance of your websites, databases, web services etc. The fact that
it has an easy to understand GUI means you can easily build a test plan and debug the
application quickly.

10. Apache Maven

We have mentioned Apache’s ANT™ earlier in the list, and Maven helps you do the same thing;
but developers think it is a big step up the ladder compared to ANT™. As far as dependency
management, build actions, debugging and collaboration is concerned, it is a few notches
higher than ANT™. To put it simply, if you are using ANT™ you need to tell it exactly what to do;
you need to mention the exact location of your source, assign the storage location of the
resultant bytecode and how you want everything to be packaged in the JAR file.

Maven, on the other hand, simplifies these things for you.

11. Gradle

If you want a tool that is a combination of everything that is good about the ANT™ and Maven,
you will be very happy with this one. With Gradle you can code in Groovy, which is a huge point
in its favor because you can code just about anything. The second huge advantage of this tool is
that it supports the convention-over-configuration paradigm.

12. Clover

This tool provides Java and Groovy code coverage. With Clover, you can zero in on the code
that might turn out to be the most problematic and make sure your testing focuses on that
particular code. Result – a problem free application.

13. YourKit
This one is a Java profiler that allows on-demand profiling during development or production;
this means you can ensure your product meets the highest standards of quality. On-demand
profiling means the profiled application can be run without incurring any overheads.

14. Mockito

If you want to write tests with clean and simple API, which deliver clean verification errors,
Mockito should be your drink of choice. Mockito is essentially a mock library that helps you
create, verify and stub mocks – an essential aspect of Java development.

15. FindBugs™

Java code has bugs? Who’re you going to deploy to find them? A good answer will be
FindBugs™. It free, easy to run and really very good!

10 Skills that will make you a great Java Developer:

An ancient proverb states “time and tide wait for no man.” If you are working in the software
industry today, this truth still applies. Today, in order to effectively work on Java projects, you
have to understanding of basic Java and Java EE APIs like JDBC and servlets are usually
expected. Basic Java/Java EE APIs serve as the foundation of the application, but to be a
participant in application development, you need more. So what other technologies/APIs are
critical to being a project member? here are the top 10 technologies/APIs every Java developer
should know:

1. At least one MVC Framework like JSF, Playframework , Struts, or Spring MVC
2. Hibernate or JPA for databases
3. Dependency Injection (as demonstrated in Spring or Java EE through @Resource)
4. SOAP based Web Services (JAX-WS)
5. Some build tool (Ant, Maven, etc.)
6. JUnit (or other Unit Testing framework)
7. Version Control mostly Git
8. Java Server Pages (JSP) is a server-side programming technology that enables the creation
of dynamic, platform-independent method for building Web-based applications. JSP have
access to the entire family of Java APIs, including the JDBC API to access enterprise
databases. This tutorial will teach you how to use Java Server Pages to develop your web
applications in simple and easy steps.
9. JSTL - The JavaServer Pages Standard Tag Library (JSTL) is a collection of useful JSP tags which
encapsulates the core functionality common to many JSP applications. JSTL has support for
common, structural tasks such as iteration and conditionals, tags for manipulating XML
documents, internationalization tags, and SQL tags.
10. Application server/container configuration management and application deployment
(whether it is WebSphere, Tomcat, JBoss, etc. you need to know where your application
runs and how to improve its execution).
 11. AJAX

LEJLA PROJECT!!! How to…

In any technology say Java or some other language, it is more important and valuable to know
the language fundamentals thoroughly (OOP concepts, interfaces, class, objects, threading
etc.) rather than specific frameworks or syntax. It's always easy to quickly learn new
technologies when you master the fundamentals.

12. 1. Have strong foundation and understanding on OO Principles

For a Java developer, having strong understanding on Object Oriented Programming is a
must. Without having a strong foundation on OOPS, one can't realize the beauty of an
Object Oriented Programming language like Java. If you don't have good idea on what
OOPS is, even though you are using OOP language you may be still coding in procedural
way. Just studying OO principle definitions won't help much. We should know how to
apply those OO principles in designing a solution in OO way. So one should have a
strong knowledge on Object modeling, Inheritance, Polymorphism, Design Patterns.
13. 2. Master the core APIs
It doesn't matter how strong you are in terms of theoretical knowledge if you don't
know the language constructs and core APIs. In case of Java, one should have very
strong hands-on experience with core APIs like java.lang.*, I/O, Exceptions, Collections,
Generics, Threads, JDBC etc. When it comes to Web application development, no matter
which framework you are using having strong knowledge on Servlets, JSPs is a must.
14. 3. Keep coding
Things look simpler when talking about them theoretically. We can give a solution to a
problem very easily in theory. But we can realize the depth of the problem when we
start implementing our approach. You will come to know the language limitations, or
design best practices while coding. So keep coding.
15. 4. Subscribe to forums
We are not alone. There are lots of people working on the same technologies that we
are working on. While doing a simple proof of concept on a framework may not give you
real challenges, when you start using it on real projects you will face weird issues and
you won't find any solution in their official documentation. When starting to work on a
new technology the best and first thing to do is subscribe to the relevant technology
forums. Whatever the issue you are facing, someone else in the world might have
already faced it earlier and might have found the solution. And it would be really really
great if you can answer the questions asked by other forum users.
16. 5. Follow blogs and respond
As I already told you are not alone. There are thousands of enthusiastic technology
freaks around the world blogging their insights on technology. You can see different
perspectives of same technology on blogs. Someone can find great features in a
technology and someone else feels its a stupid framework giving his own reasons of why
he felt like that. So you can see both good and bad of a technology on blogs. Follow the
good blogs and respond/comment on posts with your opinion on that.
 17. 6. Read open source frameworks source code
A good developer will learn how to use a framework. But if you want to be an
outstanding developer you should study the source code of various successful, popular
frameworks where you can see the internal working mechanism of the framework and
lot of best practices. It will help a lot in using the frameworks in very effective way.
18. 7. Know the technology trends
In the open source software development technology trends keep on changing. By the
time you get good idea on a framework that might become obsolete and some brand
new framework came into picture with super-set of features. The problem which you
are trying to solve with your current framework may be already solved by the new
framework with a single line of configuration. So keep an eye on whats coming in and
whats going out.
19. 8. Keep commonly used code snippets/utilities handy
Overtime you may need to write/copy-paste same piece of code/configuration again
and again. Keeping those kind of configuration snippets like log4.properties, jdbc
configuration etc and utilities like StringUtils, ReflectionUtils, DBUtils will be more
helpful. I know it itself won't make you outstanding developer. But just imagine some
co-developer asks you to help in fetching the list of values of a property from a
collection of objects and then you just used your ReflectionUtil and gave the solution in
few minutes. That will make you outstanding.
20. 9. Know different development methodologies
Be familiar with various kinds of methodologies like Agile, SCRUM, XP, Waterfall etc.
Nowadays choosing the development methodology depends on the client. Some clients
prefer Agile and some clients are happy with waterfall model. So having an idea on
various methodologies would be great.
21. 10. Document/blog your thoughts on technology
In day to day job you may learn new things, new and better way of doing things, best
practices, architectural ideas. Keep documenting those thoughts or blog it and share
across the community. Imagine you solved a weird problem occurred while doing a
simple POC and you blogged about it. May be some developer elsewhere in the world is
facing the same issue on a production deployed application. Think how important that
solution for that developer.

7 Silly Mistakes Developers Make That Will Ruin Your Career

December 6, 2016 by Geoffrey Barnes
The idea of mistaking your way to the top of the software industry is definitely dumbfounded.

Every developer will have their share of missteps in a career but you could learn a great deal from
others people’s experiences and save yourself the hassle. Thereby avoiding some of the most costly
errors.

Often than not, the key to a solid developer career always involves striking a balance: Not staying
with one stack or job too long, for example, but then again not switching languages and employers
so often that you raise red flags.

Here are some of the most notable career traps for engineers that can potentially ruin your
career and that you need to avoid while you navigate a tech market that’s constantly changing.

1. Staying too long at one job

These days it’s rare to have a decades-long run as a developer at one firm.
In many ways, it’s a badge of honor, showing your importance to the business or at least your
ability to survive and thrive. But those who have built a career at only one company may suddenly
find themselves on the wrong end of downsizing.

The longer you stay in one position, the more your skills and pay stagnate, and you will get bored
and restless.

There is no iron rule on how long you should take at a job. In my recent interview with Rob
Percival, he declines to give a particular figure to go by.

Opinions vary on how long you should stay in one job. In my opinion I think leaving a position
after an average of 2 -3 years is probably about right.

Exclusive Bonus: Click here to download my book on How to Become a $50/Hour Software
Developer in 7 Simple Steps and jump-start your software career today.

If you stay at a job for too long, you run the risk of limiting your exposure to new
approaches and techniques.

Besides, your professional network won’t be as deep or as varied as someone who changes teams
or companies.

This however can limit your growth and knowledge in other areas.

Obviously, staying a few months at each job isn’t a great look on your resume, but employee
turnover is pretty high these days and employers expect younger workers like recent college
graduates to move around a bit before staying long-term at a company.

2. Job hoping too often

Consider the other side of the coin. Are you moving around too often? If that’s a concern, you
might want to ask yourself whether you’re really getting what you need from your time at a firm.

Constant job hopping can be seen as a red flag.

Besides, those who move on too quickly may not get to see the entire life-cycle of the project
which is really great and essential for your learning and experience.

You risk becoming a mercenary, a hired gun, and you miss out on the opportunity to get a sense
of ownership over a product and build lasting relationships with people.

No matter how talented and knowledgeable you are as a software engineer, you still need the ability
to see things from the perspective of a user.

It takes a great deal of time in a position to get to know end user needs that your software addresses
and how they are using and interacting with your product.
Employers hire based on:

 technical skill,
 dependability, and more often than not,
 culture fit.

Stability and project completion often complement these hiring needs.

For contractors, it’s a good rule to complete each project before moving to the next role. Some
professionals tend to ‘rate shop’ to earn the highest hourly rate possible, but in turn burn bridges,
which won’t pay off in the long run.

3. You are passing on a promotion

There’s a point in every developer’s life where you wonder: Is this all? If you enjoy coding more
than running the show, you might wonder if staying put could stall your career.

Moving into management should be a cautious, thoughtful decision.

Management is a career change, not the logical progression of the technical track, and requires a
different set of skills.

There are many companies who push good technical talent into management because the
company thinks it’s a reward for the employee.

Everyone should be in management at least once in their career if for nothing else than to gain
insight into why and how management and companies operate.

This goes a long way to help you get to know your own work environment because there’s no one-
size-fits-all answer when it comes to this.

However, I have experienced some cases where unhappy managers:

 had no real power,

 were overloaded with paperwork and meetings, and
 had to play politics to get along.

In those environments, it would be better to stay in development.

For the long term goal though, I would recommend that everyone gets into management, because
development careers stall out after 20 years, and you will not receive any much more
compensation beyond that time.

Sometimes accepting a promotion can put you, and your colleagues/friends, in control of your
workday happiness.
4. You are not paying it forward
A less obvious mistake might be staying too focused on your own career track without
consideration of the junior developers in your office.

Those who pair with young programmers are frequently tapped when a team needs leadership.

Mentoring junior developers has made me better at my job. I learn any subject deeper by
teaching it than I do by any other method.

Again, as developers often struggle with interpersonal skills, mentoring provides me a great
opportunity to brush up on these people skills.

If experience is the best teacher, then be rest assured that teaching others will only deepen your
knowledge.

Never make the statement ‘I’m not good with people’, it just comes out as lazy and careless.

5. Sticking to your one favorite stack

Your expertise in one stack may make you invaluable to your current workplace, but is it really
helping your career? Can it hurt to be too focused on only one stack?

Focusing too much on one stack used by your current employer obviously is great for the firm
but maybe not for you.

It’s a benefit to other employers looking for a very specialized skill set, and every business is
different.

There’s no modern software engineering role in which you will use only one technology for the
length of your career.

If you take a Java developer that has been working in Java for 10 years, and all of a sudden they
start working on a JavaScript application, they’ll write it differently than someone with similar
years of experience as a Python developer.

Each technology that you learn influences your decisions. If say you take a Java object-oriented
approach to a loosely typed language like JavaScript, you’ll try to make it do things that it isn’t
supposed to do.

It will hurt your trajectory to be too focused on one stack.

Every stack has a different culture and perspective, which ultimately will broaden and expedite
your career growth. For example, many C# developers are only aware of the Microsoft ecosystem,
when there is a far larger world out there. If you have used Bitbucket for version control for a long
time, you might consider trying out Github.

Proficiency, but not mastery, with one stack should be the benchmark before moving on to another
shinny stuff.

You’ll know it’s time to move on when you are good at the skill, but not necessarily great.

This is not to say I’m advocating for mediocrity, in fact it’s exactly the opposite. I am saying that
before you head off to learn a new skill make sure you are good, competent, or above average at
your current skill before you consider moving on.

You must avoid the expectation trap that each new language is simply the old one with a different
syntax.

Developers of C# and Java who try to force JavaScript into a classical object-oriented approach
have caused much unnecessary pain to themselves and their team members.

6. Neglecting soft skills

Programmers are typically less outgoing than, say, salespeople. No secret there.

But soft skills can be picked up over time, and some of the nuances of developing a successful
career, like learning from mentors and developing relationships, can be missing from your career
until it’s too late.

Soft skills and conversations with customers will also give a great sense of compassion that
will improve how you build. You begin to think about what the customers really need instead of
over-engineering.

It makes for better software when people talk.

Let me stress the point that your work with other people is a crucial part of developing a successful
developer career.

All human activities are social, and development is no exception.

A lack of soft skills is a career killer.

Haven’t you seen when less proficient programmers move ahead, then developers who don’t
have people skills or simply aren’t exercising them are left wondering why?

Don’t you agree that everyone loves a boss who demonstrates tact and proficient
communication?

To improve your soft skills, the:

  Internet,
 e-courses,
 friends, and
 mentors

are invaluable resources if you are humble and remain coachable.

Besides, we will all reach a point in our career when we will need to lean on relationships for
help.

If no one is willing to stand in your corner, then you, not they, have a problem, and you need
to address it.

In my career, I have valued coachable people over uncoachable when I have had to make tough
personnel decisions.

Programming is only one aspect of development.

The big part is being able to communicate and understand business objectives and ideas, between
groups of people with varying levels of technical skills. I’ve seen too many IT people who try to
communicate too much technical detail when talking with management.

7. You fail to develop a career road map

Developing goals and returning to them over time, or conversely developing an agile-like, go-
with-the-flow approach both have their proponents.

Make a list of experiences and skills that you’d like to acquire and use it as a map, updating
it at least annually.

I engineer less for goals and more for systems that allow me to improve rapidly and seize
opportunities as they arise.

Having said that, I recommend making a list of experiences and skills that you’d like to acquire
and use it as a map, updating it at least annually.

Knowing where you’ve been is as useful as knowing where you want to go. And of course equally
as important, where you don’t want to go.

Early in my career, I hadn’t learned to say NO yet.

So I agreed to a project plan that there was no way could be successfully delivered. And I knew it
couldn’t.
If I had been more assertive, I could have influenced the plan that a bunch of nontechnical people
made and saved my then-employer time and money, my co-workers a substantial amount of
pain, and ultimately the relationship we had with the customer.

What are your some of the mistakes you’ve made as a developer that hampered the successful
progress of your career?

Please share your thoughts in the comments below.