How to be an inefficient developer? - Petar Ducic (Infobip)

•

0 likes•206 views

You know that superstar in your company who does 5x more work than you? well, this is a talk with a few examples that will rationalize you your practices, so you can stay mediocre forever! or hopefully change that :)

Petar Ducic
how to be an
inefﬁcient engineer
🙃

40k
active
accounts
7bn
monthly
interactions
4,4bn
unique mobile
users
60+
offices
worldwide
1500+
great
employees

works in a team. scrum. planning. bug.
takes the task, “i’ll manage it on my own”.
starts developing a system to ﬁnd a bug. it’ll
be useful for ﬁnding bugs later on. 2 weeks
later - we still have a bug and a new
complicated system full of new bugs

comes from a great company to a startup
project. clean code, high availability, micro-
services, tests coverage, polyglot persistence.
no errors, ever. predicted all the possible use
cases that’ll occur in next 15 years.
“waiting for the clients to onboard”

don’t get emotionally
attached to your idea

works in a team. others take all interesting
tasks. he takes one nobody wants. he is a
nice guy. never wrote one line beside work.
never gave a suggestion for improvement
because the POs and TLs should do that

choose with who are
you spending your time

don't get burnt-out
while chasing efficiency

* Edmond Lau: Effective engineer
* Lot of Google guys: Site Reliability Engineering 
* Robert Cecil Martin: Clean code
* Kent Beck: Simple design
* Damir Prusac: On the Trace of Agile Leadership
* Roko Roić: Agilni razvoj softvera
* Jocko Willink, Leif Babin: Extreme ownership

Remember when the internet was pure and unspoiled? In our innocence we saw the promise of renewal of the world through connecting, sharing, and creating online. We became developers and hackers because we wanted to understand how things work, to take them apart, and build quirky (and sometimes useful) things just for the pleasure of it. In the earliest decades of the Internet Epoch the Internet was a playground. We happily coded directly on production systems. And it was fine, as many Great Things were created. But the Internet has matured, and has now become Big Business. Developers have matured too, and good thing they did! So many people now rely on what we’ve built, for security, for privacy, for the paycheck at the end of the month. We matter. Maturity has come at a price though, and deploying well tested code into complex applications with polyglot teams working with heterogeneous stacks, all while maintaining compliance with GDPR, HIPAA, PCI, etc. has taken all of the childhood innocence out of the web. Now even the simplest website seems like Hard Work. In this talk I will show how we can, and should, regain our joyful demeanor, how we can use the maturity of the most innovative tools around us to start hacking like crazy again. Without regressing on agility, testing, compliance, scalability or robustness. I use the metaphor of childhood innocence to explain how the complexity of modern cloud computing, in combination with increasing quality expectations and compliancy, has curtailed the creative freedom of developers, and as a whole, organisational motivation. Together with a lack of resources and idea time, this leads to lower and slower product innovation. We are, however, at the brink of a paradigm shift in cloud computing that will give developers and hackers their mojo again. This talk will zoom into the key elements of this paradigm shift, and provide an overview of the basic concepts and operational practices of the new age of developer innocence. https://drupalcampkyiv.org/node/81

10 ways to accelerate software development by dave thomas at yow! nights hk

Tze Chin Tang

Agile principles and practices

Vipin Jose

Software Sucks

Hans-Jörg Schnedlitz

Slides from my DevOpsExpo London talk "From oops to NoOps". They tell you in these conferences that DevOps is not about tools, but about culture. And they are partially right. I am going to tell you that it’s not only about culture or tools but also abstractions. It is a lot about how you see software and its value. About our mental model of what software is: how it runs, evolves, and interacts with the other facets of an enterprise. We used to view software as code. As a state of code. Now we think about software as change, as a flow. A dynamic system where people, machines, and processes interact continuously. At Platform.sh we spend a bunch of time asking ourselves not “How do you build?” - or even “How do you build consistently?” - but rather “What does it mean to consistently build in a world where change is good?” A world that lets you push security fixes into production as soon as they’re available because you don’t want to be an Equifax but you do want stability. In this presentation, I will go over what we think software is and why having the right ideas about software will help you get your culture right and your tooling aligned, as well as gain in productivity, and general happiness and well-being.

Chaos Engineering Without Observability ... Is Just Chaos

Charity Majors

RedisConf17 - Observability and the Glorious Future

Redis Labs

Crime File System

IJARIIT

the project is aimed to develop a crime file for maintain a computerized record of all the F.I.R against crime .The system is desktop application that can be access throughout the police department. This system can be used as an application for the crime file of the police department to manage the records of different activity of related to first information report .In such desktop Crime file system we will manage all such activities (like registration of the complaint updating information, search of particular viewing of the respective reports of crimes) that will save time, manpower. This software is for police station which provides facility for reporting crimes, complaints, FIR, charge sheet, prisoner records, and show most wanted criminal’s details. This system will provide better prospective for the enhancement of organization regarding to quality and transparency

SRE Topics with Charity Majors and Liz Fong-Jones of Honeycomb

Daniel Zivkovic

Charity's words make you think while Liz's words make you act, so when you combine them, you get one of the best meetups on Elite DevOps Performance, SRE and Observability topics – ever! Google Meet recording stopped working, so this *noisy* DIY-copy is the best we got: https://youtu.be/geqoOg4WXcQ. Still, the video is worth your time because you will see how empathy, and simple focus shift 1) from Dev and Ops to your Users, 2) from APM tools to Observability, can make your workdays more productive, enjoyable and meaningful. To learn how to define your first SLO, go to Honeycomb's 3-part SRE Crash Course https://go.hny.co/serverlessToronto.

From DevOps to NoOps how not to get Equifaxed Apidays

Ori Pekelman

How to explain DevOps to your mom

Andreas Grabner

These are the slides used in my #devone (www.devone.at) keynote presentation: DevOps is one of the most abused and overrated marketing terms in the last years! That’s not an alternative fact! It’s just Andi’s opinion! Yet - it is a very real thing that allowed many software companies to transform the way they think about software engineering. DevOps can mean something totally different thought depending on who you are and what type of business your company is doing. To clarify things, Andi gives us insights on how he explains the benefits to “DevOps Newbies” and how software companies around the world implement it in their own ways. Andi will answer: What does it really mean for developers, testers and operators? What will change? How does Facebook deploy twice a day without big issues? How does DevOps work in financial, government or healthcare where you have tight regulations? Does it mean Devs are responsible for Ops? Does it only work in the cloud? Or can we apply it to “old fashioned” on premise software as well? Learn for yourself and make up your own mind on whether DevOps is just a marketing term or something that can benefit you!

More fun using Kautilya

Nikhil Mittal

Originate - Think In Hours Not Sprints

Rob Meadows

Fixing security by fixing software development

Nick Galbreath

Fixing Security by Fixing Software Development Using Continuous Deployment Do you have an effective release cycle? Is your process long and archaic? Long release cycle are typically based on assumptions we haven't seen since the 1980s and require very mature organizations to implement successfully. They can also disenfranchise developers from caring or even knowing about security or operational issues. Attend this session to learn more about an alternative approach to managing deployments through Continuous Deployment, otherwise known as Continuous Delivery. Find out how small, but frequent changes to the production environment can transform an organization’s development process to truly integrate security. Learn how to get started with continuous deployment and what tools and process are needed to make implementation within your organization a (security) success.

ROOTS2011 Continuous Delivery

Ole Christian Rynning

Continuous Delivery

Stein Inge Morisbak

Getting software released to users can be risky, time-consuming and painful. The solution is the ability to deliver reliable software continuously through build, test and deployment automation, and through improved collaboration between developers, testers and operations. In this tutorial we will present principles and technical practices that enable teams to incrementally deliver software of high quality and value into production whenever they want, and extremely fast. The size of the project or the complexity of its code base does not matter. In the first half of the tutorial we will introduce the concepts of continuous delivery, through continuous integration; and automation of the build, test and deployment process. We will also go through som basic principles and patterns for building automatable applications (architecture). We will cover experiences on team collaboration patterns and lastly; techniques for solving tasks such as an easy and comprehendible version control strategy. The second half of the tutorial we will be working with automated provisioning of agile infrastructure, including the use of tools (puppet) to automate the management of testing and production environments. We will go through some scripting lessons examplifying how to implement zero-downtime deploys (… and rollback – if something goes wrong!), with examples in both bash and Ruby. Along with controlling the start, stop, restart lifecycles during deploys, we will also show some simple techniques for backups, logging, error handling, monitoring and verification of application health that can make the automation more robust. We will also use servers "in the cloud" to demonstrate different techniques, and we hope to make it a fun day and to deliver software (examples) several times throughout the workshop. Required knowledge: Agile/Lean basics, Linux basics, version control basics, maven basics.

Humane assessment on cards

Tudor Girba

Dead codepresentation 0drewz lin

Product Vs Craft

MagenTys

Week 4 Assignment - Software Development PlanScenario-Your team has be.docx

estefana2345678

Week 4 Assignment - Software Development Plan Scenario: Your team has been tasked with delivering a Section 508-validated application for U.S. Department of Homeland Security field officers to check potential immigrants for connections to criminal or terrorist behavior. This application must meet these requirements: Â· Conform with Section-508 accessibility guidelines. Â· Allow wireless real-time bidirectional data transfer and database queries with secure servers. Â· Have a secure login and, after two minutes of non-use, have autolocking that reactivates a secure login. Â· Allow for officers working on any day and at any time in offices, from vehicles, and on foot along the U.S. border and in cities across the country. Overview In Week 2, you defined how you will determine user applicability and needs. This week, you will map out a plan for your project. Instructions: Create a 2â€“3-page software development plan for the application you are developing. Include the following: Â· List 8â€“10 steps the project will follow from proposal to post-implementation stages for proper design of the application. Be sure to account for all application constraints in the project planning steps. Â· Explain the outcome, process, and resources involved in accomplishing each step. Incorporate at least 3 credible and relevant resources to support your statements. Â· Create a Gantt chart that includes each step in the process, the resources involved, and the estimated duration of time it will take to complete each step. It is recommended that you use Microsoft Excel to create your chart. You may copy and paste it into your software development plan document or submit a separate file. Â· Remember, your audience is your companyâ€™s IT executive. Your writing should be professional and free of grammar, punctuation, and spelling errors. Figure 1. The evolution of the Waterfall Model (a) and its long development cycles (analysis, design, implementation, test) to the shorter, iterative development cycles within, for example, the Spiral Model (b) to Extreme Programmingâ€™s (c) blending of all these activities, a little at a time, throughout the entire software development process. 0018-9162/99/$10.00 Â© 1999 IEEE70 Computer I n the beginning was the waterfall (Figure 1a). We would get the users to tell us once and for all exactly what they wanted. We would design the system that would deliver those features. We would code it. We would test to make sure the features were delivered. All would be well. All was not well. The users didnâ€™t tell us once and for all exactly what they wanted. They didnâ€™t know. They contradicted themselves. They changed their minds. And the users werenâ€™t the only problem. We programmers could think we were making great progress only to discover three-fourths of the way through that we were one-third of the way through. If long development cycles were bad because they couldnâ€™t adapt to changes, perhaps what we needed was to make shorter.

TxJS 2011

Brian LeRoux

Continuous integration

Boris Dominic

Empowered productivity

Giedrius Rimkus

corporateJavascript

climboid

Shift Remote: AI: How Does Face Recognition Work (ars futura)