• 01
  What we do
• 02
  3 things that you could achieve at Lampart
• 03
  Message from CEO
• 04
  Company Overview

02
3 things that you could achieve at Lampart

• 

  01
  REAL “BASIC SKILLS”

  You will be able to acquire "true basic skills".

  A programming language is merely “a language”.
  While there are many people who think they “can program”, a programming language is merely “a language”. There is absolutely no meaning in simply “writing it” and “getting it” to operate.

  “Being able to program means” first writing out a condition and considering whether there are any oversights in the condition, then considering “exceptions” for situations that are disconnected from the condition.
  Once you can do this, you will then “be able to design programs” based on your “knowledge of programming languages” and “frameworks”.

  Depending on the purpose of the system, there should be many choices available to you at this time, so it is necessary to consider which to choose. While one decision may work for now, it is necessary to consider how far ahead you should hypothesize about things to come before implementing it.
  Wide-ranging experience and knowledge are necessary to check and make assumptions about the business operations and kinds of duties conducted by our client companies.

  At Lampart, we teach the fundamentals that, by their nature, every engineer should learn.
  Because of this, at Lampart, you will acquire the basic skills that apply across any environment, business, or programming language.

• 

  02
  GOOD JUDGMENT
  AND ADAPTABILITY

  You will be able to acquire abilities to consider test cases.

  It goes without saying that engineers are responsible for “making sure that the things they make work properly”.

  What kinds of use cases do we assume at Lampart in creating our programs?
  At Lampart, through program source review, we check how thoroughly the use case was considered, figure out where the consideration was insufficient, and provide feedback regarding not just the bad points, but also the good points.

  Our quality control team creates test case tables from requirement definitions and design specifications and validates operations. With regard to result processing, the team confirms database, screen, and output result (form, CSV, etc.) items one by one.
  Test result feedback from the quality control team assesses not just programing, but also oversights in assumptions. This feedback is an incredibly valuable opportunity for growth and will dramatically raise your “skills in considering test cases”.
  This kind of skill should be assumed when developing programs and will certainly be useful in “use cases diagrams”.

• 

  03
  THE IMPORTANCE OF
  COMMUNICATION

  "Communication is our company's lifeblood". You will be able to learn the important business skills of "reporting, contacting, and consultation".

  The three words “reporting, contacting, and consultation” are the most fundamental and important actions there are.

  “It wasn’t written, so I didn’t implement it,” and “It wasn’t written, so I just did it the way I wanted to,” are two excuses that mean absolutely nothing to the customer.
  Instead, think, “It isn’t written, so what should I do?” and seek confirmation without fail.

  When you don’t understand meaning of the method, or when it’s difficult and not going well no matter what you do, consult without feeling embarrassed.

  If you carry on without consulting anyone, you will not grow.
  It may be a bit embarrassing to ask questions or seek consultation, but which is better: the you who carries on not understanding and not being able to do something, or the you who, as a result of gathering a bit of courage and asking or consulting, has become able to do something?

  At Lampart, it’s more “embarrassing to carry on without knowing”, or to “make something without checking and run into a system bug”, so “there is nothing embarrassing about asking or consulting for help in order to avoid bad results”.

  At Lampart, we have created “a culture in which everyone honors this way of thinking”.
  Because of this culture, we are a company where individuals can communicate easily with one another and continue to grow.

  We receive work orders from our customers.

  There’s no problem if a project is advancing at a good pace, but it is never more necessary to stand forward and make a report than when progress is not good (or when there’s bad news).
  The evaluation of Lampart and all of the individuals who work here is based on “the degree of perfection of the systems” we deliver to our customers and “how they are assessed”. It is for this reason that we are prompt to report “any trouble that comes up in a project”. The speed with which we are able to solve the problem matters greatly.
  By quickly and accurately reporting mistakes made by yourself and your team, it is possible to heighten the quality of the product we ultimately deliver to the customer, which raises the assessment of our company. This is then linked to an evaluation of you.
  Therefore, we do not blame the individual who reports “bad news” or “problems”; instead, we as a team gratefully assess what was reported, which is then connected with the growth of the team and us all.

03
Message from CEO

04
Company Overview