Ivan Necas
Software Architect at Masaryk University Brno
Brno, Southeast, Czechia
Summary
🤩
Rockstar🎓
Top SchoolIvan Necas is a Software Architect with 15 years of experience building and shaping complex, data-driven infrastructure and product teams at Red Hat, focusing on improving supportability and cross-product integrations. He blends hands-on full-stack and backend engineering (notably on Foreman and concurrent-ruby) with architectural leadership, mentoring, and POC-driven research to turn ambiguous requirements into pragmatic solutions. A long-time open-source contributor, he has improved Puppet/Foreman deployments, hardened concurrency primitives in concurrent-ruby, and enhanced API tooling in apipie-rails — work that surfaces in widely used projects underpinning infrastructure automation. Based in Brno, he pairs deep Ruby/Rails expertise with operating-level concerns (SSL, DB setup, deployment parametrization), helping teams ship more customizable, robust systems. Colleagues rely on him to start technical conversations, drive cross-team architecture, and translate support and customer insights into prioritized engineering work.
15 years of coding experience
13 years of employment as a software developer
Master's degree, Information Technology, Master's degree, Information Technology at Masarykova univerzita Brno
English
Github Skills (36)
git10
ruby-rails10
debug10
puppeteer10
foreman10
apidoc10
puppet10
futures10
api-design10
dsl10
testing10
configuration-management10
rails10
ruby10
api10
Programming languages (24)
Github contributions (5)
Apipie/apipie-rails
Apr 2012 - Sep 2019
Ruby on Rails API documentation tool
Role in this project:
Back-end Developer
Back-end DeveloperContributions:329 commits, 118 PRs, 127 pushes in 7 years 6 months
Contributions summary:Ivan's contributions primarily involved enhancing the Apipie-Rails API documentation tool. They refactored the code to move the engine and assets into a separate namespace, improving organization and preventing conflicts. They introduced configuration options like `baseurl` and implemented a custom dispatcher to support assets hosted at different addresses. Furthermore, the user made improvements by allowing a way to extend existing params with a concern.
ruby-on-railsapiruby-on-rails-apirails-apirails
theforeman/foreman
Jun 2012 - Jun 2019
an application that automates the lifecycle of servers
Role in this project:Full-stack Developer
Full-stack DeveloperContributions:148 commits, 212 PRs, 109 pushes in 7 years 1 month
Contributions summary:Ivan primarily contributed to the Foreman project by addressing various issues related to running Foreman in subpaths and improving its overall usability. They focused on fixing path-related problems for creating hosts and graphs, and also improved the handling of template rendering in safe mode. Furthermore, they enhanced the API by fixing the path for the "create medium" API and addressing authorization issues, leading to improvements in security and API functionality. They also updated the code to improve performance and added a test to clear the current user after processing the request.
automatesmaasinfrastructure-managementvirtualizationhybrid-cloud
Find and Hire Top DevelopersWe’ve analyzed the programming source code of over 60 million software developers on GitHub and scored them by 50,000 skills. Sign-up on Prog,AI to search for software developers.