Skip to main content

What to expect from devops

Build smart automation
  • automate everything and everywhere
  • implement clever monitoring 
  • in case of a failure automatically fall back into the previous working state

Enable continues development
  • give all developers easy and simple way how to do continues development without compromises
  • build support for step-by-step deployment and A/B testing
  • deliver production-like environment runnable on developer's workstation 

Rule the cloud
  • deeply understand cloud technology
  • code scalable infrastructure for actual and future needs
  • enforce optimal security model

Be step ahead
  • always think one step in future about necessary improvements
  • constantly identify bottlenecks and limits of current production system with possible solutions 
  • apply agile and lean principles 

Comments

Post a Comment

Popular posts from this blog

Senior or Junior

Usually companies call young employees Juniors and more experienced Seniors. Sometimes you need to just sit and wait and it will come. Sooner or later. From my point of view it is not enough. I met a lot of old employees they call themselves Seniors but they behave like Juniors. So I defined my point of view on Seniority: professional simple understand what I am doing and understand reason why I am doing it can coach others this is very basic; who can coach others is just fine but who can coach others to became a new coaches is super not genius but have deep knowledge on some specialized parts geniality is overestimated, we do not need "magical guru", to be expert is good enough; if you are "one to go" when there is problem, it is OK big picture overview it is not probably possible to understand a whole system in details but it is necessary to have at least overview know what I know and know what I do not know to see myself in correct light is very ...
Post a Comment
Read more

Anti-Lean Quotes

Set of quotes which usually highlights Anti-Lean behavior Create waste instead of Eliminate waste ' Developer who is not working at least on 4 projects is not properly utilized ' - less is definitely more and only done-done work counts by end of the day, limited work in progress is helping to focus on right priorities ' In case of any network issues please create a ticket on the help desk system at our partner's web-page' - creating catch 22 situations by design is craziness, such a process does not make any sense 'Yes, this is what our customers really need but could we add also this small feature, just in the case?' - extra feature creates an extra complexity, it is better to stay focused on real value and make it great for the users ' I know that you are working on the top priority but I am sure that you can do also this small task till noon' - probably there will be nothing really done by noon, task switching is more expensiv...
Post a Comment
Read more

Agile is not a religion

It is quite annoying to me when argument during discussion is like this:  it must be XY because the book says it. It is kind of: Bible is saying XY so we have to follow = end of discussion.  I am not very happy in such a case because we probably do not understand principles and just trying to blindly imitate something without deep knowledge of the matter. I prefer to admit it or show personal standpoint.
Post a Comment
Read more

Toyota Production System and Agile Software Development

Andon Board : The facility for workers to signal problems to supervisors for immediate remedy, stopping the production process if necessary. Workstations along the production line can activate a warning on an illuminated central display board, which constantly displays productivity levels. =>  SCRUM/Kanban board + CI/CD automation Asa-ichi Meeting : A meeting held every morning in Toyota plants to discuss quality deviations and eliminate their causes. An essential part of the practice of kaizen. => Daily stand up Genchi Genbutsu: Going to the source to find the facts to make correct decisions, build consensus and achieve goals. => Retrospective (Root Cause Analysis) + face2face communication Heijunka: Leveling the production schedule in both volume and variety. A precondition for just-in-time and elimination of mura, muri and muda. => Velocity + self-organization + sustainable development Jidoka : Making problems visible so that they can be ...
Post a Comment
Read more