go

Recursos de programación de go
I'm going to be telling you about what happens after your code reaches production, and how we can make that better. So as developers, we like to solve problems. We like to write code in order to feel like we're having an impact on the world. But the problem is that solving problems doesn't really just stop from the moment that we commit our code and land it into Git. We have to actually make sure that it's serving our users and making them happy. And as our systems grow more and more complex, it's much more difficult to understand what's actually going on. How can we make sure that our customers are having good experiences? How can we be sure that when things actually get deployed into production, for instance, when they're running on someone's Android device, or when they're running on millions of web browsers, how do we make sure that everything is still working as we planned? And what does it even mean for a system to be up or down? [...] Don't waste your time working on things that are not important. Work on your system to make it just reliable enough, and then go back to working on features. But then be prepared to go back to working on reliability when you need to. But a thing that people commonly overlook is that if you do not have observability, that is a systematic risk. That is a risk that adds to the length of every outage that you have. If you are spending the first 20 or 30 minutes out of every outage trying to figure out what's going on, and how to make it stop, that's a lot of unhappy users. So that's a systemic risk. And that's something that you may need to think about addressing. The other thing that's a hidden risk is a lack of collaboration. You may not necessarily see it directly when you do this risk analysis, but if your customer support team doesn't feel comfortable raising issues, then you're going to have issues last a lot longer before you even start working on them.
IT companies are addicted to exponential growth. But is this good for our planet, our society, and ourselves? Social entrepreneurship claims to offer an alternative - but something still doesn't feel right. This talk will combine my practical experience building "nonprofit businesses" with the macroeconomic theory of "post-growth" economists like Tim Jackson and Kate Raworth. This talk will question everything that you know about entrepreneurship, provide practical tools to build something different, and then offer you a blue pill and a red pill. Can you go back to "business as usual" again?
These are the best podcast/talks/ebooks I've seen/listen to recently.PodcastsScreaming in the cloud: How to Grade DevOps Teams with Nicole Forsgren, PhD Software Engineering Daily Facebook Engineering Process with Kent BeckSoftware Engineering Daily Facebook Parse Acquisition (Part 1) with Charity Majorshttps://www.infoq.com/podcasts/high-performance-cultures/ Randy Shoup on Creating High-Performance Cultures InfoQ Culture podcastDevops / Agile cultureBetter value sooner...
Un software de curación de contenidos suena a poca cosa hasta que ves las "tripas" de esta plataforma. Primer episodio de la tercera temporada del podcast. Gracias a todos por seguir ahí durante el verano escuchando con tanta atención. 100 episodios Recomiendo, por si te lo has saltado, volver al episodio 100. Aunque fuera en plena semana de vacaciones, ahí lo doy todo. Es un resumen en forma de compromiso de lo que he compartido con vosotros en los 99 primeros episodios. Puedes escuchar...
Google Cloud, in partnership with Codemotion, is proud to release this unique online training program, available for free, to help developers learn about the services in Google Cloud Platform and show them how to get the most out of each service. Get more info and apply here: http://bit.ly/GCPDevs What is GCP? Google Cloud Platform is a suite of cloud computing services offered by Google and based on the same infrastructure that Google uses for its own products, such as Gmail, YouTube or Google Search. Since we are talking about the company that runs the most widely used search engine in the world, the ability to tap into its own infrastructure represents a guarantee of reliability and scalability. As an extra added value, Google has always focused on innovation and has had to develop new technologies over time to meet unique requirements in terms of volume of data and the capacity needed to process it. Take a quick look at all the benefits you can receive using GCP. About GCP Developer Enablement Program The course is aimed at everyone who has already chosen GCP, but also at those who are yet to make that choice, or anyone who is simply interested in the platform and what it has to offer. The program consists of 3 independent courses, where two Google Cloud Certified trainers go into the basics of the platform and its offering, through a combination of presentations, demos, and case studies. Course 1: Core Intro to GCP: What is it? What are its advantages and main services? Course 2: Big Data What’s the offering for Big Data and Machine Learning on GCP? Course 3: Kubernetes Orchestrating containers with Kubernetes GCP Test your knowledge at the end of each course with an in-depth related quiz. What can I expect on completion of the program? Once you have completed all the courses in this learning program and have successfully passed the related quizzes, you will receive: - a certificate of online attendance and a digital badge that you can share on your social networks and your LinkedIn profile - 100 credits on the Qwiklabs platform, that give you access to up to 5 courses for a deeper understanding of GCP - a free course on Google Cloud with Coursera For any further info feel free to contact us at training@codemotion.it Get more info and apply here: http://bit.ly/GCPDevs
VP of Engineering at Ebury Victor is the VP of Engineering for Ebury, comes from managing international software development teams creating operating systems and applications for Mobiles and Cloud solutions. More recently worked as Director of Engineering at Bitnami (YC'13) and VP of Commercial Engineering at Canonical (sponsors of Ubuntu Linux). Victor is passionate about System Reliability and he is a go and Kubernetes enthusiast.
Software Engineer at Google Jaana B. Dogan works on making Google production services more monitorable and debuggable. Previously, she worked on the Go programming language at Google and has a decade-long experience in building developer platforms and tools.
Novedades en el mundo del desarrollo. Primer streaming de "#laFunciónCodelyTV()" con: * Dominios io en peligro * KPIs para equipos de desarrollo * Novedades de la #WWDC * #GitHub Desktop 2.0 * Normativa de pagos online #SCA * Machine Learning aplicado a código con #FacebookAroma * Sorpresitas varias 🙂 🔗 Enlaces relacionados: 🎓 Cursos CodelyTV Pro: |-- 💸 Oferta lanzamiento curso Go: http://bit.ly/oferta-go |-- 🐨 Curso "Introducción a Go: Tu primera app": https://bit.ly/go-codelytv |-- 📕 Catálogo cursos: https://bit.ly/cursos-codely {▶️} CodelyTV |-- 🎥 Suscríbete a nuestro canal: https://www.youtube.com/c/CodelyTV?sub_confirmation=1 |-- 𝐟 Facebook: https://facebook.com/CodelyTV/ |-- 📸 Instagram: https://instagram.com/CodelyTV/ |-- 🐦 Twitter: https://twitter.com/CodelyTV
Complexity in systems should be defeated if it is possible to do. But the default nature of our computer systems are complex and servers are doomed to fail. In this talk, we will go through new approaches in modern architectures to design and evaluate new computer systems.
Thinking of moving to Microservices? Watch out! That quest is full of traps, social traps. If you are not able to handle it, you may be blocked by meetings, frustration, endless challenges that will make you miss the monolith. In this talk, I share my experience and mistakes, so you can avoid them. Creating or migrating to a Microservices architecture might easily become a big mess, not only due to technical challenges but mostly because of human factors: it’s a major change in the software culture of a company. In this talk, I’ll share my past experience as the technical lead of an ambitious Microservices-based product, I’ll go through the parts we struggled with, and give you some advice on how to deal with what I call the Six Pitfalls: The Common Patterns Phobia The Book Club Cult The Never-Decoupled Story The Buzz Words Syndrome The Agile Trap The Conway’s Law Hackers