The most recent Rzeszów Ruby User Group meeting confirmed our belief that it’s worth it to discuss topics other than Ruby even among a Ruby crowd. The organizers saw a 50% increase in attendance compared to previous editions. Participants talked about the advantages and disadvantages of TypeScript, and learned what the role of a DevOps Engineer is and isn’t. Overall, it was a very fruitful meeting.
<blockquote class="twitter-tweet" data-lang="pl"><p lang="en" dir="ltr"><a href="https://twitter.com/hashtag/Rzeszow?src=hash&ref_src=twsrc%5Etfw">#Rzeszow</a> <a href="https://twitter.com/hashtag/Ruby?src=hash&ref_src=twsrc%5Etfw">#Ruby</a> User Group we start in a moment! Typescript from rubyist's perspective. Devops. And certainly a lot of discussions. If you are not here yet you still have a few minutes to arrive! And thanks <a href="https://twitter.com/iRonin_IT?ref_src=twsrc%5Etfw">@iRonin_IT</a> for sponsoring! :) <a href="https://twitter.com/hashtag/RRUG?src=hash&ref_src=twsrc%5Etfw">#RRUG</a> <a href="https://twitter.com/hashtag/IT?src=hash&ref_src=twsrc%5Etfw">#IT</a> <a href="https://t.co/CHG6bxno7p">pic.twitter.com/CHG6bxno7p</a></p>— RRUG (@RRUGpl) <a href="https://twitter.com/RRUGpl/status/1092841956869316608?ref_src=twsrc%5Etfw">5 lutego 2019</a></blockquote>
<script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
She also listed the pros and cons of using TypeScript. The language’s disadvantages include a level of complexity which can be overwhelming at first, and an extra compilation stage which results in a delay before freshly introduced changes become visible. However, TypeScript has many advantages that make using it worthwhile, such as high predictability, ease of debugging and a good syntactical structure. Róża summed up her presentation by saying that TypeScript works very well for large projects and teams, but in smaller ones, the gains won’t be equal to the time investment necessary to use the language.
The second presentation of the evening was delivered by Michał Borkowski. His topic was DevOps - more specifically, Michał wanted to explain what it means to be a DevOps Engineer, what an environment with a real DevOps culture is like, and how to make the first steps towards building such a culture. For Michał, DevOps isn’t a job, a single person with the term in their job title or even a team using DevOps principles. There’s also no specific toolset that can claim the name for itself. Instead, DevOps needs to be understood as a culture of shared responsibility, transparency and automation.
DevOps promotes the shortening of the feedback loop between teams in a company, for example between software developers and the operations team. It emphasizes the importance of constant knowledge sharing with team members, as well as continuous improvement and automation of processes. The goal is to deliver new iterations more quickly, while maintaining system security and stability through effective monitoring. Michał finished his talk with a practical presentation of several basic command line prompts, such as previewing logs, which can help developers in completing simple tasks on the production environment.
Remember to join us at the next RRUG meeting - as iRonin is RRUG’s sponsor, we’ll be posting about upcoming meetings on our social media. You can follow us there to make sure you’re always up-to-date with our Ruby events.
Looking for top quality Ruby on Rails software development outsourcing?
iRonin has been delivering commercial software projects for a decade, putting extra effort into always choosing the right solution for every task.