Category: software topics

“Typography error”
It is abbreviated as “Typo”. The code doesn’t move because of a typo.

e.g.
get hello/index のところを get hello/indox などとtypingをミスすことをタイポエラーという。

タイポグラフティエラー対策？？
うーん、正直よくわかりませんな。。

とにかく今のプロジェクトのクオリティを上げることが最優先、と考えていたが、思っていたより直ぐに「モダンな開発環境とは何か？」という問いに直面してしまった。

自分なりに整理してみる。
まず、技術トレンドに乗っている
これが大事では。レガシーなシステムは切り離して、トレンドを忠実に追うこと。そのためには、まずそういう環境に身を置くことが大事。ちゃんと技術トレンドに沿っているエンジニアと一緒に仕事をしないといけない。
– 言語はpython
– クラウドはaws
– mac

積み重ねだと思うが、結構大事かも。

次に、、、
積極的に新しい技術を学んでいけ
やっぱりこれは大事なんじゃないか。。と思い始めた。

結果的にそれが価値に繋がるのでは。

最近思うのは、競争相手は中国やインドなどのエンジニアだということ。働き方改革など悠著な事を言っている場合ではありませんね。

SLA is an abbreviation of Service Level Agreement, which is an agreement on the level of service (definition, scope, content, achievement goals, etc.) established between the provider of the service and its users. This is a statement to the extent that the service provider can guarantee the quality to the contractor.

SLAs are often used mainly for communication services, cloud services, rental servers, etc. We define service definition and guarantee items such as communication speed and upper limit of use stop time, and if the service quality falls below the guarantee value of SLA, reduction of charge will be performed.

Technical debt is a new metaphor that refers to a sloppy software architecture and the consequences of unsatisfying software development. It is also referred to as “design debt”.

What kind of technical debt is there?
– Low coverage or no written test code
– Findings that smooth sharing has not been done between developers and stakeholders.
– Ignored compiler warnings and code analysis results
– Designs and codes that are unnecessarily complex
– Code not in compliance with coding conventions
– Unwanted odor (this metaphor is often used for refactoring)
– Old versions of languages and frameworks
– Difference between development environment and production environment

たった1人からはじめて、「越境」するチームをつくるまで

推薦されたので、読了した。
最初、「越境」という意味が、国境を超える、と思っていたのだが、そうではなくて、一歩踏み出す、という意味だ。
本書はソフトウェア開発における悩みやその解決のアプローチ方法を多数提示している。よって、環境や立場は異なるが、各登場人物の心境に共感できることが多く、読み物として楽しめる。俯瞰して読むことで、チーム開発においては、身勝手な行動は一切慎むべきだということが手に取るようにわかる。また、突き詰めると、エンジニアや当事者のスキルセット次第ということもよくわかる。スキルが足りないと、コミュニケーションミスが齟齬が起きやすいように感じた。

https://classmethod.jp/

Described on the homepage that aws professional group solves the problem.

When examining company information, first of all it is a habit to see employment information.

First view shows project manager, aws integration.

Job detail
What kind of work do you do?
As a project manager, we will do project promotion in general. We will promote a series of work such as progress management and quality control from the planning and agreement of the project with the engineers and partners in the company.

Also, for customers who have already installed AWS, as an account manager as well as sales, we think about further use of AWS to solve problems of customers and solve business problems, and we will help you decide policy.

What kind of human resources are you looking for?
Those who have a strong will to make the project successful with customers. If problems occur, do not hold them alone, those who can deal with organizations and team involvement.

Wow, what engineer are doing is roughly the same with other places.

AWS operational design consultant
– Operational design work of service built by our company or customer
– Proposal of labor saving, automation by combining various services of AWS
– Support for operational design in order to acquire certification of our company or customer service.

With aws design, you have to understand aws in a great deal of detail.

Is not it listed? want to invest lol

RFP is a document that asks the vendor candidate to make a concrete proposal when introducing an information system or outsourcing it. Describe the purpose and overview of the system, requirements and constraints.

A concrete RFP method is easy to create when considering the overall configuration into the following three categories.

1. Overall picture
It is intended to make it simple to understand the whole system development that we would like to request the proposal this time.
Describe development objectives, goals, budget, schedule and so on.

2. Proposed requirements
Specifically, it shows specifically what you want a suggestion that meets.Describe the scope you want the suggestion, the division of roles, required functions, operation / maintenance, deliverables.

3. Other
Information that seems better to convey to other than 1 and 2, what you are astray about judgement, etc. are listed as supplements.

1. overall picture
background of development
purpose of development
goals / achievements
budget size
schedule
target
number of contents to be handle

2. proposed requirements
scope to request suggestion
delivery deliverables
method of system development
functional requirement
operation and maintenance requirements
education and training requirements
organization
structure

3. other
consideration
assumed competing site

エンジニアにとって、英語力は必須。
これは間違いないだろう。

英語でも、リスニング、リーディング、ライティングがある。特に重要なのはreadingかと思っていたが、どうやら考えが甘すぎた。。
– listening
– reading
– writing

本当に重要なのは、英語の表現力。
高いレベルの仕事をするには、説得力のある説明や、よりスムーズに仕事をできるような英語力が必須。
とはいえ、これは直ぐには身につかないし、何をやるのがベストか？

案1:英語でブログを書く
案2:英語のサービスを作る
案3:海外に移住する

どうするか？？
英語が重要なのは絶対に間違いない。
案1を1年～2年くらい目標にやってみるか。。