“Atacílio possui a característica marcante de se preocupar com as pessoas! Sem pronto pra ajudar a resolver toda e qualquer questão em que é acionado! É indiscutível o conhecimento que possui para realizar o trabalho, além de características de lider que o tornam especial para o time.!”
Sobre
I am an Engineering Manager with 14+ years in software engineering and 8+ years leading…
Atividades
-
Hoje é o último dia das incrições para o DevTITANS, uma ótima oportunidade para quem quer conhecer sobre o mundo de desenvolvimento em Android e…
Hoje é o último dia das incrições para o DevTITANS, uma ótima oportunidade para quem quer conhecer sobre o mundo de desenvolvimento em Android e…
Compartilhado por Atacílio Cunha
-
I am very excited about the advancements of AI for developing apps quickly. I myself built a few prototypes using ClaudeCode and Codex, and this had…
I am very excited about the advancements of AI for developing apps quickly. I myself built a few prototypes using ClaudeCode and Codex, and this had…
Atacílio Cunha gostou
Experiência e formação acadêmica
-
SiDi
Ver experiência completa de Atacílio
Veja o cargo, tempo na empresa e muito mais dessa pessoa.
ou
Licenças e certificados
-
-
Engenharia de Software Moderna
Curso de Extensão em Engenharia de Software Moderna (DCC/UFMG)
Emitido em Expira em -
Fundamentos de Arquitetura de Software
desenvolvedor.io
Emitido em Expira emNº da credencial https://desenvolvedor.io/certificados/e19c6c51-8910-43cb-bff6-caf3838dff38 -
Projetos
-
Samsung Car Mode
Samsung's driving solution that allows users to interact with the mobile device using voice control features. Target devices are: Samsung Galaxy S5, Note 4 , Note Edge and Galaxy S6.
https://www.youtube.com/watch?v=Sys8fBErxao
https://www.youtube.com/watch?v=SDo7wb15w2I#t=177
Outros criadores -
Idiomas
-
English
Nível avançado
Organizações
-
Aliança 3:6
Pianist
- o momentoAliança 3:6 is a musical group linked to Seventh-Day Adventist (SDA) Church.
Recomendações recebidas
2 pessoas recomendaram Atacílio
Cadastre-se agora para visualizarOutros perfis semelhantes
Ver mais publicações
-
Pedro Piñera Buendia
Ubiratan Soares recently asked me about swift-build, and it got me thinking about Apple's build tooling ecosystem. While unifying build systems is definitely a step in the right direction—especially as Swift expands across platforms—there's a fundamental challenge: the persistent fragmentation of build graphs between Xcode projects and Swift packages. I'd love to see Apple provide clear direction on the path forward. Without that clarity, teams are stuck maintaining two separate graph representations, ensuring they remain reconciled, and dealing with bugs that emerge from this complexity. Build graph reconciliation is genuinely challenging, and splitting that effort across two systems compounds the difficulty. We're now seeing Swift Package interfaces adopting features that Xcode projects have had for years. Developers naturally want feature parity, which is understandable. However, this has created a liability: the Swift Packages interface has become an awkward mix of APIs for dependency management and interfaces for project-level configuration. These are fundamentally different use cases, and serving both creates friction. This tension forces Xcode to trigger asynchronous reconciliation processes that leave the IDE essentially unusable during execution. What's worse is the lack of meaningful UI—just a spinner with no insight into what's happening. For teams under tight deadlines, this is a genuine productivity blocker. If I were making these decisions, I'd commit to a unified solution and establish a long-term plan that addresses architectural decisions in Xcode that didn't pan out well. Many improvements would involve deprecating workaround features like "mergeable libraries." This shouldn't have been necessary—if the build system properly handled dynamic frameworks without requiring copy phases, we wouldn't need band-aid solutions. Technically, I don't think Swift in its current form is ideal for build configuration. You want something that evaluates instantly and prohibits environment access to ensure hermeticism. But when even Apple's packages perform I/O operations and break hermetic builds, we can't expect the broader ecosystem to maintain stricter standards. From an outside perspective, it appears the Swift and SwiftPM teams are pushing new capabilities forward while the Xcode team works to integrate those changes retroactively. There's significant investment in Swift Build—necessary infrastructure work—but it doesn't address fragmentation at higher architectural layers. That fundamental question about how these systems should converge remains unanswered. #Swift #SwiftPM #Xcode #iOSDevelopment #BuildSystems #DeveloperTools #SoftwareEngineering
2 comentários -
Manos Ragiadakos
I heard a developer from Brazil couldn't clone a repository from github, his git requested to login on github to verify his age. Also I heard that Brazilian Arch linux users couldn't update their OS or download new software from the package manager. Maybe these are rumors or it is really happening. I wonder what Canonical, RedHat and Debian will do because Brazil's government and universities use these distros. Will they stop uploading security patches to them ? Also I wonder what producers of mobile phones will do.
Mais pessoas chamadas Atacílio Cunha
Mais 1 pessoa chamada Atacílio Cunha está no LinkedIn
Veja mais pessoas chamadas Atacílio Cunha