Начальник отдела маркетинга регионального рынка ТМК в своем докладе остановился на рынке сырьевых материалов, который оказывает непосредственное влияние на формирование рынка трубной продукции. Он проанализировал сегменты стального лома и горячекатаного штрипса России и мира, в заключении сделав небольшой прогноз относительно того как сложится ситуации здесь в 2014 г.
This document discusses Google's search engine marketing strategies. It explains that search engine optimization (SEO) and pay-per-click (PPC) advertising can be used together to drive more traffic ("1+1=3"). It also discusses how advertisers can target "moments of relevance" by connecting with consumers across Google's search, content network, and web utilities. The document provides examples of different ad formats on Google and how they can help achieve various advertising goals like driving conversions or leads. It emphasizes the importance of crafting compelling ads with headlines, descriptions, and calls to action that are relevant to users.
The document provides an overview of information and communication technology (ICT) spending and usage in Thailand for the years 2549-2551 (2006-2008). Some key findings from 2550 (2007) include:
- Total ICT spending was 537.8 billion baht, a 9% increase from 2549. Communications spending accounted for the largest share at 391.2 billion baht (72.7% of total).
- Computer hardware spending increased 6.8% to 68.7 billion baht. Computer software increased 17.6% to 57.1 billion baht.
- Enterprise/corporate entities accounted for 53.3% of total ICT spending, while households/SOHO accounted
- The document discusses moving away from the traditional "rails way" architecture to a more modular architecture for a Rails application.
- It describes splitting the application into separate frontend (AngularJS) and backend (Rails API) components. The Rails backend is refactored using patterns like entities, repositories, and presenters to separate concerns and improve testability/reusability.
- Examples demonstrate implementing validation modules, form objects, service classes, and separating domain logic from data access using a repository pattern with the Sequel ORM rather than ActiveRecord. This leads to a cleaner architecture.
Начальник отдела маркетинга регионального рынка ТМК в своем докладе остановился на рынке сырьевых материалов, который оказывает непосредственное влияние на формирование рынка трубной продукции. Он проанализировал сегменты стального лома и горячекатаного штрипса России и мира, в заключении сделав небольшой прогноз относительно того как сложится ситуации здесь в 2014 г.
This document discusses Google's search engine marketing strategies. It explains that search engine optimization (SEO) and pay-per-click (PPC) advertising can be used together to drive more traffic ("1+1=3"). It also discusses how advertisers can target "moments of relevance" by connecting with consumers across Google's search, content network, and web utilities. The document provides examples of different ad formats on Google and how they can help achieve various advertising goals like driving conversions or leads. It emphasizes the importance of crafting compelling ads with headlines, descriptions, and calls to action that are relevant to users.
The document provides an overview of information and communication technology (ICT) spending and usage in Thailand for the years 2549-2551 (2006-2008). Some key findings from 2550 (2007) include:
- Total ICT spending was 537.8 billion baht, a 9% increase from 2549. Communications spending accounted for the largest share at 391.2 billion baht (72.7% of total).
- Computer hardware spending increased 6.8% to 68.7 billion baht. Computer software increased 17.6% to 57.1 billion baht.
- Enterprise/corporate entities accounted for 53.3% of total ICT spending, while households/SOHO accounted
- The document discusses moving away from the traditional "rails way" architecture to a more modular architecture for a Rails application.
- It describes splitting the application into separate frontend (AngularJS) and backend (Rails API) components. The Rails backend is refactored using patterns like entities, repositories, and presenters to separate concerns and improve testability/reusability.
- Examples demonstrate implementing validation modules, form objects, service classes, and separating domain logic from data access using a repository pattern with the Sequel ORM rather than ActiveRecord. This leads to a cleaner architecture.
This document discusses how to break bad habits by using GitLab CI to automate routine tasks. It provides examples of automating tests, packaging code, and deploying artifacts and websites. Specifically, it shows how to:
1. Run automated tests with GitLab CI
2. Package code into downloadable artifacts
3. Deploy packages and websites to AWS S3 and GitLab Pages
4. Separate testing and production using environments
5. Allow multiple developers to work on the same project simultaneously
6. Avoid mistakes by not deploying directly to production
This document discusses common problems that arise when developing Ruby on Rails applications. It argues that Rails principles like DRY, KISS, and fat models/skinny controllers are often misunderstood and misapplied. This leads to complexity over time as applications grow. The document recommends approaches like SOLID principles, design patterns, refactoring techniques, and separating business logic from controllers to help address these problems.
What I Have Learned from Organizing Remote Internship for Ruby developersIvan Nemytchenko
This document describes a remote internship opportunity for Ruby developers. Interns would work on a portfolio project for 20 hours per week minimum, gaining experience with the full development cycle, teamwork, and remote work. Applicants would take an aptitude test assessing their skills with requirements like user registration, permissions, and integrating with external APIs. Successful interns would work independently on assigned features while receiving guidance from mentors. Lessons from past internship programs are discussed, like the need for clearer communication and ensuring interns have enough support to avoid burnout.
1. The document discusses using GitLab CI to automate software development tasks like testing, packaging, and deployment.
2. It provides examples of configuring GitLab CI pipelines to run tests, package code as gzip and ISO files, and deploy artifacts to S3 storage and GitLab pages.
3. The document also covers more advanced topics like using environments to separate staging and production, enabling manual deployment for production, and automatically deploying feature branches to separate review environments.
A document lists several cities and dates for Lean Poker events in Eastern Europe and Russia, including events in Belgrade, Omsk, Moscow, and Lviv on March 26th with event websites provided.
How to use any static site generator with GitLab Pages. Ivan Nemytchenko
It is possible to delegate all the routine work of static site generation to GitLab Pages. It is possible because of built-in CI service.
March, 19 2016, Kiev, Ruby Meditation
At the early days, Rails community accepted few principles unconditionally because they sound like axioms.
People use principles and acronyms to compress meanings. By doing so, there's a risk for them to be misunderstood. And I think this is exactly what's happened to with some people in Rails community.
So let's try to decompress them, and see what might be wrong with our understanding.
It is common for rails-teams to stuck at some point. It happens when team doesn't try to manage complexity of their app.
In this talk I demonstrated my path from a Rails-application to somewhat modular architecture app: things like Form Objects, Repositories, Entities etc. emerged naturally, as a solutions for existing problems, not because we were told by someone to use them.
March 15, Wroclaw, wroc_love.rb 2015
Different approaches to ruby web applications architectureIvan Nemytchenko
This document discusses different ways to organize Ruby code, including code organization styles used in Semaphore, various Ruby libraries like Lotus and Chassis, and resources for learning about design patterns from authors like Sandi Metz and Avdi Grimm. It also provides contact information for the presenter to discuss code examples.
This document provides an overview of ActiveRecord and Mongoid object document mappers for Ruby on Rails applications. It describes MongoDB as a scalable and high-performance NoSQL database without transactions or joins. It explains how Mongoid provides a similar API to ActiveRecord but is designed for MongoDB's schemaless and document-based data model. Various Mongoid associations like embeds_many and embedded_in are demonstrated through code examples. Additional MongoDB features through Mongoid like localization, GridFS for file storage, and hybrid ActiveRecord/Mongoid applications are also briefly covered.
This document discusses how to break bad habits by using GitLab CI to automate routine tasks. It provides examples of automating tests, packaging code, and deploying artifacts and websites. Specifically, it shows how to:
1. Run automated tests with GitLab CI
2. Package code into downloadable artifacts
3. Deploy packages and websites to AWS S3 and GitLab Pages
4. Separate testing and production using environments
5. Allow multiple developers to work on the same project simultaneously
6. Avoid mistakes by not deploying directly to production
This document discusses common problems that arise when developing Ruby on Rails applications. It argues that Rails principles like DRY, KISS, and fat models/skinny controllers are often misunderstood and misapplied. This leads to complexity over time as applications grow. The document recommends approaches like SOLID principles, design patterns, refactoring techniques, and separating business logic from controllers to help address these problems.
What I Have Learned from Organizing Remote Internship for Ruby developersIvan Nemytchenko
This document describes a remote internship opportunity for Ruby developers. Interns would work on a portfolio project for 20 hours per week minimum, gaining experience with the full development cycle, teamwork, and remote work. Applicants would take an aptitude test assessing their skills with requirements like user registration, permissions, and integrating with external APIs. Successful interns would work independently on assigned features while receiving guidance from mentors. Lessons from past internship programs are discussed, like the need for clearer communication and ensuring interns have enough support to avoid burnout.
1. The document discusses using GitLab CI to automate software development tasks like testing, packaging, and deployment.
2. It provides examples of configuring GitLab CI pipelines to run tests, package code as gzip and ISO files, and deploy artifacts to S3 storage and GitLab pages.
3. The document also covers more advanced topics like using environments to separate staging and production, enabling manual deployment for production, and automatically deploying feature branches to separate review environments.
A document lists several cities and dates for Lean Poker events in Eastern Europe and Russia, including events in Belgrade, Omsk, Moscow, and Lviv on March 26th with event websites provided.
How to use any static site generator with GitLab Pages. Ivan Nemytchenko
It is possible to delegate all the routine work of static site generation to GitLab Pages. It is possible because of built-in CI service.
March, 19 2016, Kiev, Ruby Meditation
At the early days, Rails community accepted few principles unconditionally because they sound like axioms.
People use principles and acronyms to compress meanings. By doing so, there's a risk for them to be misunderstood. And I think this is exactly what's happened to with some people in Rails community.
So let's try to decompress them, and see what might be wrong with our understanding.
It is common for rails-teams to stuck at some point. It happens when team doesn't try to manage complexity of their app.
In this talk I demonstrated my path from a Rails-application to somewhat modular architecture app: things like Form Objects, Repositories, Entities etc. emerged naturally, as a solutions for existing problems, not because we were told by someone to use them.
March 15, Wroclaw, wroc_love.rb 2015
Different approaches to ruby web applications architectureIvan Nemytchenko
This document discusses different ways to organize Ruby code, including code organization styles used in Semaphore, various Ruby libraries like Lotus and Chassis, and resources for learning about design patterns from authors like Sandi Metz and Avdi Grimm. It also provides contact information for the presenter to discuss code examples.
This document provides an overview of ActiveRecord and Mongoid object document mappers for Ruby on Rails applications. It describes MongoDB as a scalable and high-performance NoSQL database without transactions or joins. It explains how Mongoid provides a similar API to ActiveRecord but is designed for MongoDB's schemaless and document-based data model. Various Mongoid associations like embeds_many and embedded_in are demonstrated through code examples. Additional MongoDB features through Mongoid like localization, GridFS for file storage, and hybrid ActiveRecord/Mongoid applications are also briefly covered.