
Working well together: Our development style, with no overtime and flexible office attendance
Hi. I'm the engineer Kawashima.
We are currently looking for freelancers who will be able to participate in support on a per-project basis, as announced by a tweet from the representative Takasaki.
in our company
Kenji TAKAZAKI/non-standard world (@nplusone) August 23, 2018
Web designer
editor/writer
engineer
We are looking for freelancers who can work with us on a project-by-project basis, especially those near Saito. https://t.co/lcdvjBj4ms
In order to prevent the mismatch of “it’s a little different from what you imagined” when you work together, in this article I would like to introduce “what style we are working on?”)
For engineers in particular, I think that the technology and tools used for development are also of concern, so it is described in detail later in this article.
It is a great help to the image of working with us.
Contents [ hidden display ]
business values and systems
NONSTA aims to realize a work-life harmony that values both work and life, and incorporates various mechanisms into our daily operations.
Under a remote work system where employees are free to enter the company, we use Scrum methods to allocate appropriate resources and basically do not overtime.
In order to achieve business efficiency, we actively utilize IT tools and enhance our manuals to prevent employees from becoming a part of the business and create an environment that makes it easier for each member to voluntarily make decisions.
for details Company Information page of this site I'm very happy to see it.
business communication in general
GitHub
Code management, issue management and manuals are integrated on GitHub.
Past Hiring Articles Show GitHub Utilization So please take a look at it together.
The rules for branch operation GitHub flow It is simple and has a mechanism that prevents trouble.
Each task is estimated in accordance with the Scrum approach, and we care not to focus too many tasks during development.
Supplement: About Scrum
Scrum is one way to achieve the progression of an agile development project.
It is characterized by “flexible development for the entire team to cope with project changes” and it is often compared with waterflow development (*the direction in which we proceed along specifications as they flow from upstream to downstream; effective for large-scale development, but less flexible and a lot of loss when changing specifications).
A succinct overview of the Scrum approach is as follows:
- Repeat production and review on a per-task basis for the period (sprint) of one to two weeks
- The man-hours of production tasks are estimated by story points, not time
- Provides a place for team members to check the progress of production tasks on a daily basis
For more information, please refer to the previous article below.
https://www.non-standardworld.co.jp/tech/15657/
Slack
We use Slack for communication during work.
Remote communication is active in NONSTA because remote work is permitted and we have been collaborating with members living in Tokyo, Fukuoka and other areas in recent years.
Each member of Slack has a separate reporting channel that allows them to easily post tasks they are working on, questions you may have, and scoldings – making it easier for them to communicate with each other by visualizing how their work is going.
* Partitions are explained in an easy-to-understand manner in the following article:)
Slack's 'Split-Up' Makes Work Efficient | Gadget Lab https://note.mu/reoleo/n/n102308f5b4e3
zoom
For remote face-to-face communication, we use a video tool called Zoom.
Because the communication environment is stable, there are few stresses such as cutting in meetings that last for an hour, not to mention daily morning meetings.
The usage and characteristics of zoom are described in the following past articles.
https://www.non-standardworld.co.jp/tech/20989/
web design
Adobe XD
and the web design tool Adobe XD I use it.
The XD design specification also serves as a design instruction manual, allowing both designers and engineers to work smoothly.
Nonsta’s engineers are responsible for naming, writing and compressing images from XD design files rather than design specifications.
Please refer to the following past article for the good compatibility between XD and coding.
https://www.non-standardworld.co.jp/tech/20020/
development
We have created a manual that summarizes coding rules and procedures, and update every day.
As of November 2018, the technologies used in website implementation (including WordPress projects) are as follows.
- HTML5
- CSS3
- Sass(compass)
- JavaScript
- jQuery
- PHP
- Ruby on Rails
Chrome / firefox / safari / Edge The latest version of the browser, and IE11 are supported on smartphones: Safari is up to date for iOS 8 or later; Chrome is up to date for Android 5.
* Support is mainly for WordPress projects, and there’s little chance that you would like to request a Ruby on Rails project.
Codekit
The task runner at the front implementation uses Codekit, a GUI tool for compilation, compression and real-time preview.
Since configuration files are shared with git, it is an environment that is easy to join the work.
Local by Flywheel
In WordPress projects, engineers with knowledge of PHP will be responsible for creating and embedding theme files after creating HTML camps.
Local by Flywheel is used to build a WordPress local environment, making it easy for members to unify and share their local environments.
https://www.non-standardworld.co.jp/tech/20659/
DeployBot
We use DeployBot to deploy the website we created.
It works with git repositories to automatically deploy the pushed files, and it can easily roll back in case of trouble.
In addition, GitHub Flow is adopted as a git branch operation rule that can be easily combined with DeployBot. As the name suggests, it is a simple workflow proposed by GitHub and it is characterized by producing in the master branch as production environment and development branch per function.
For more information, please refer to the previous article below.
https://www.non-standardworld.co.jp/tech/20267/
Selenium IDE
We use the Selenium IDE for UI testing of our site.
Since you can create, edit and run tests in the browser without writing any test code, we try to automate as much as possible simple tests that are done on routines such as entering forms or checking link transitions.
You can check the situation when you actually use it from the past article below.
https://www.non-standardworld.co.jp/tech/20823/
instead
Did you refer to the image of Nonsta's development style :)
For a series of flows including direction, service guide page haha. corporate site production page I hope you can also refer to it.
If you feel that it would be comfortable to work together, please don't hesitate. this application form. Please contact us from here and we will be waiting!