Improving code quality
3 likes929 views
The document discusses tips and tricks for improving code quality, including issues to avoid like mutable state and premature abstraction. It recommends outside-in development, starting with acceptance tests and unit testing using test-driven development. The use of immutable objects is emphasized to avoid temporal coupling and make code more maintainable. Additional techniques include smell-driven development to detect code smells and refactor as needed. Tools like rubocop, reek and mutant are also mentioned.
1 of 15
Downloaded 15 times
Ad
Recommended
Coderetreat @AgileFinland Tampere 2014 11 12
Coderetreat @AgileFinland Tampere 2014 11 12Adi Bolboaca The document describes a code retreat, which is a day-long event where developers improve their coding skills through pair programming. Developers are paired randomly and rotate partners every 45 minutes to work on simple problems under different constraints. The goal is to learn through practicing fundamentals, experimenting with new approaches, and getting out of one's comfort zone. Various coding exercises and techniques are outlined to help developers improve, including test-driven development, incremental design, and refactoring.
Basics of writing clean code
Basics of writing clean codeKnoldus Inc. 1) Clean code is easy to understand, extend, and refactor. It has small, single responsibility classes and methods that work as expected and are easily testable.
2) To write clean code, follow principles like SOLID and Law of Demeter. Name things clearly and use verbs for functions, nouns for classes.
3) Functions should be short and do one thing. Classes should contain related variables and functions. Handle errors gracefully and return exceptions. Write tests that are fast, independent, repeatable, and self-validating.
Writing Tests Effectively
Writing Tests EffectivelyPaul Boocock Part of the internal Codeweavers Development series from our Academy.
Writing Tests are a fundamental part of our development workflow but it's not easy to write them well. This talk dives into this and throws a few spanners in the works from what people traditionally think.
Evolutionary Design - Refactoring Heuristics
Evolutionary Design - Refactoring HeuristicsAdi Bolboaca Evolutionary Design seems to be one of the black arts of software development. Test Driven Development brought the need of understanding how to evolve the code in order to solve a problem. Evolving the code is not done by magic, we evolve the code, the programmers. And we need specific techniques for that.
This talk will be an interactive one, presenting some of the most useful refactoring techniques for Evolutionary Design.
Coderetreat @AgileFinland Helsinki 2014 11 13
Coderetreat @AgileFinland Helsinki 2014 11 13Adi Bolboaca The document describes a code retreat, which is a day-long event where developers pair program to practice coding fundamentals. Participants rotate through different coding partners and sessions with varying constraints to solve problems without finishing code. The goal is to learn through experimentation outside one's comfort zone. Sessions include test-driven development, object calisthenics rules, and taking baby steps with timers. At the end, participants reflect on their experience.
Multimedia a3
Multimedia a3Mick_Lin 3GPP specifications are difficult to study because they are interlinked across many technologies, do not provide examples, and some specifications are very large. To effectively understand 3GPP specifications, one should clearly identify the specific topic of interest, first read the main specification section before following any references, and take printouts to write notes and mark important points when needed. It is also recommended to fully research the topic on your own before asking others questions.
Plc2 2015 first time right coding
Plc2 2015 first time right codingSigasi This document discusses first time right coding, which involves writing code that compiles without errors from the first attempt. It recommends setting up automatic compilation when files are saved or typed to catch errors early. This prevents wasting time fixing errors and avoids checking in broken code. Various IDE tools are mentioned that can help with incremental compilation and catching syntax, type, and other errors at compile time rather than later.
Exam conditions
Exam conditionschrisseth The document outlines procedures and rules for a BMEC SLP exam. Candidates must turn off phones and enter the exam room silently. Only exam papers, rough paper, headphones, and stationery are permitted on desks. Candidates cannot communicate with others, bring notes into the exam, look at another's paper, or show their own paper. When finished, candidates must leave materials on their desk and leave silently without exiting early. The document defines cheating and states candidates will fail if caught cheating.
Effective Unit Testing
Effective Unit TestingEyal Kenig The document discusses best practices for effective unit testing. It covers the test pyramid, benefits of good tests, test schemas, tips and guidelines. The test pyramid emphasizes having more simple unit tests, fewer integration tests, and even fewer end-to-end tests. Good tests provide confidence, help design, document requirements and make code more robust. Tests should have clear names, single assertions, and arrange-act-assert structure. Edge cases, exceptions and return values should be prioritized. Tests should be readable and not rely on implementation details.
Misconceptions Of Unit Testing
Misconceptions Of Unit TestingTerry Yin Unit testing is commonly misunderstood to be about finding bugs, when its true purpose is to prevent bugs from being introduced. Writing unit tests requires designing code for testability from the beginning. The tests should focus on internal quality and design rather than just external requirements. Unit tests should be written by the same developers who write the code to leverage their domain knowledge, and they should be added as the code is written rather than as an afterthought. When done properly, unit testing leads to more stable, maintainable code and higher productivity over the long run.
Test driven development - why you should test first?
Test driven development - why you should test first?Abimbola Idowu My goal is to convince you to test your code the next time you are developing an application.
Introduction to test driven development
How to deliver the right software (Specification by example)
How to deliver the right software (Specification by example)Asier Barrenetxea Talk about Specification by Example. What's the problems it tries to tackle and how to solve them.
I gave this talk at Thoughtworks on a "lunch and learn" meeting for the company.
This is a new version of my previous presentation about "Specification by example"
https://www.slideshare.net/AsierBarrenetxea1/spec-byexample-v2
Coderetreat - Practice to Master Your Crafts
Coderetreat - Practice to Master Your CraftsLemi Orhan Ergin Coderetreat is a one day intense workshop for software developers for imporving their development skills by practicing. This is the material I presented at the beginning of coderetreat I facilitated on May 2014.
Unit Testing and TDD 2017
Unit Testing and TDD 2017Xavi Hidalgo Conferencia realizada en pasado enero'17 en las jornadas organizadas por expoqa. También usada en el grupo de meetup Agile-Lleida.
Working With Legacy Code
Working With Legacy CodeAndrea Polci The document discusses strategies for working with legacy code, which is code inherited from previous developers or older versions that often lacks tests and good documentation. It defines legacy code and outlines challenges like poor structure, dependencies, and lack of tests. It then provides approaches for modifying legacy code like identifying what to change and test, breaking dependencies, writing tests, and refactoring code in small, tested increments. Specific tactics are presented like using seams, sprouting methods, and interfaces to break dependencies and allow testing legacy code. The importance of understanding the system and increasing test coverage before making changes is emphasized.
Try harder or go home
Try harder or go homejaredhaight This document provides tips for taking the OSCP certification exam, focusing on reconnaissance, exploitation, and pivoting. It recommends aggressively scanning all ports with NMAP, using tools like Dirbuster for web enumeration, and saving all findings. Exploitation advice includes using Searchsploit and Metasploit carefully according to exam rules, and getting comfortable with buffer overflows. The document also suggests scripting commonly used exploits, thoroughly pillaging compromised systems, and pivoting networks through SSH port forwarding or ProxyChains. Organizing notes and completing the required lab report are also emphasized.
Test-Driven Development (TDD) in Swift
Test-Driven Development (TDD) in SwiftAmey Tavkar The document discusses test-driven development (TDD) in Swift. It explains that TDD involves writing tests before implementation to gain confidence and verify requirements are met. Automated tests allow for faster regression testing, easier refactoring, and continuous integration. The document recommends writing tests first to produce loosely coupled code aligned with requirements. It provides examples of TDD best practices and common pitfalls to avoid.
Tdd in swift
Tdd in swiftJaval Nanda 1. The document discusses test-driven development (TDD) in Swift, including why it is important to write tests before implementation. Automated tests provide confidence, verification of requirements, and help identify weak areas of code.
2. TDD involves writing tests first to define requirements before writing any code. This forces developers to think about design and creates loosely coupled, independent code modules.
3. Common pitfalls to avoid in TDD include not testing behaviors, having dependent tests, not refactoring code, and testing private methods or external libraries. Best practices include using a good architecture, protocols to isolate classes, and structured tests with arrange, act, assert format.
Writing clean scientific software Murphy cleancoding
Writing clean scientific software Murphy cleancodingsaber tabatabaee The document provides an overview of Nick Murphy's background and work on the PlasmaPy open source software project. Some key points:
- Nick Murphy grew up in Michigan and has a background in astronomy, having done his graduate work simulating magnetic reconnection.
- PlasmaPy is an open source Python software ecosystem for plasma research and education. It includes core functionality, affiliated packages, educational resources, and an active community.
- The talk outlines best practices for writing clean, readable scientific software, including using descriptive names, comments, functions, tests, and separating high-level and low-level code. The goal is to make software more reusable, understandable, and to improve the research experience.
Fast end-to-end-tests
Fast end-to-end-testsRikke Veng Petersen This document summarizes Lars Thorup's presentation on fast end-to-end tests. It discusses the drawbacks of traditional end-to-end tests like being slow, imprecise, complicated and fragile. Unit tests are faster but rely on mocked dependencies. The presentation demonstrates a way to automatically generate mocks to test applications from end-to-end very quickly while avoiding the downsides of mocks. The demo shows a Node.js app with front-end and back-end tested at almost 100 end-to-end tests per second.
Super fast end-to-end-tests
Super fast end-to-end-testsLars Thorup Automated end-to-end tests are often seen as a necessary evil. A common example is Selenium-based browser tests. This kind of testing has many drawbacks: 1) They take a long time to run. 2) They require complicated setup. 3) They are fragile. But it doesn't have to be like that!
In this talk I describe how we can write automated end-to-end tests that are 1) Superfast. 2) As easy to setup as unit tests. 3) As robust as unit tests.
This technique is leveraging existing unit testing techniques. Tests for lower layers (such as server code) is instrumented to record all requests and responses in a log file. Tests for higher layers (like client code) is extended with an mocking layer that automatically configures with the contents of that log file.
It is then possible to run a almost a hundred end-to-end tests every second.
From Gatekeeper to Partner by Kelsey Shannahan
From Gatekeeper to Partner by Kelsey ShannahanQA or the Highway The document discusses moving from a "gatekeeper" model of testing, where testing is done separately after development, to a "partner" model where testing is integrated into development and shared responsibility of the team. It provides tips for making this transition, such as fixing problems developers experience with testing, integrating testing into development workflows, and helping testers contribute to other parts of development to become true partners. The overall message is that testing is most effective when it is easy to do and an inherent part of the development process done collaboratively by the entire team.
Value of Unit Testing
Value of Unit TestingFerose Khan J This document discusses unit testing and provides guidance on how to implement it. It defines unit testing and explains why it is important for refactoring code with confidence, understanding code design, and creating living documentation. It provides steps for setting up, running, and verifying unit tests and recommends testing behavior rather than methods. Specific dos and don'ts are outlined such as making tests fast, fully automated, and writing informative messages. A conversation is included that emphasizes the importance of continuing to write tests.
Coding standard let’s do it
Coding standard let’s do itMinh Quang Trần This document discusses coding standards and guidelines to improve code readability, testability, and maintainability. It recommends avoiding duplicate code, using single exit points from functions instead of else blocks, wrapping primitive types in objects, having only one variable assignment per line, keeping classes small with a limited number of lines, methods and classes, and references the Object Calisthenics principles for improving code quality.
Xtreme Programming
Xtreme ProgrammingPrasad Kancharla The document discusses concepts in agile development and extreme programming (XP), focusing on pair programming, test-driven development (TDD), and continuous integration (CI). It defines pair programming as two developers working together on a single task, switching roles frequently between driver and navigator. Benefits include better design, knowledge sharing, and code quality. TDD involves writing tests before code to drive design and ensure code quality. CI aims to integrate code changes frequently to catch errors early.
Test driven development_and_puppet-cfgmgmtcamp_eu-20140402
Test driven development_and_puppet-cfgmgmtcamp_eu-20140402Johan De Wit The slides of the talk i did on cfgmgmtcamp.eu, frebruary 4th 2014, looking at test driven development. This part is focused on the development of a custom puppet type
Introduction to Continuous Delivery
Introduction to Continuous DeliveryGiovanni Toraldo What we have learn the last year while developing ClouDesire, presented at an Apericoder event organized by Coders TUG in Pisa.
Pen Testing, Red Teaming, and More
Pen Testing, Red Teaming, and MoreCTruncer This is the slide deck that I used when presenting at FSU's Cyber Security Club. This presentation was supposed to give a description of what Red Teaming, Pen Testing, and other roles do.
Ad
More Related Content
Similar to Improving code quality (20)
Effective Unit Testing
Effective Unit TestingEyal Kenig The document discusses best practices for effective unit testing. It covers the test pyramid, benefits of good tests, test schemas, tips and guidelines. The test pyramid emphasizes having more simple unit tests, fewer integration tests, and even fewer end-to-end tests. Good tests provide confidence, help design, document requirements and make code more robust. Tests should have clear names, single assertions, and arrange-act-assert structure. Edge cases, exceptions and return values should be prioritized. Tests should be readable and not rely on implementation details.
Misconceptions Of Unit Testing
Misconceptions Of Unit TestingTerry Yin Unit testing is commonly misunderstood to be about finding bugs, when its true purpose is to prevent bugs from being introduced. Writing unit tests requires designing code for testability from the beginning. The tests should focus on internal quality and design rather than just external requirements. Unit tests should be written by the same developers who write the code to leverage their domain knowledge, and they should be added as the code is written rather than as an afterthought. When done properly, unit testing leads to more stable, maintainable code and higher productivity over the long run.
Test driven development - why you should test first?
Test driven development - why you should test first?Abimbola Idowu My goal is to convince you to test your code the next time you are developing an application.
Introduction to test driven development
How to deliver the right software (Specification by example)
How to deliver the right software (Specification by example)Asier Barrenetxea Talk about Specification by Example. What's the problems it tries to tackle and how to solve them.
I gave this talk at Thoughtworks on a "lunch and learn" meeting for the company.
This is a new version of my previous presentation about "Specification by example"
https://www.slideshare.net/AsierBarrenetxea1/spec-byexample-v2
Coderetreat - Practice to Master Your Crafts
Coderetreat - Practice to Master Your CraftsLemi Orhan Ergin Coderetreat is a one day intense workshop for software developers for imporving their development skills by practicing. This is the material I presented at the beginning of coderetreat I facilitated on May 2014.
Unit Testing and TDD 2017
Unit Testing and TDD 2017Xavi Hidalgo Conferencia realizada en pasado enero'17 en las jornadas organizadas por expoqa. También usada en el grupo de meetup Agile-Lleida.
Working With Legacy Code
Working With Legacy CodeAndrea Polci The document discusses strategies for working with legacy code, which is code inherited from previous developers or older versions that often lacks tests and good documentation. It defines legacy code and outlines challenges like poor structure, dependencies, and lack of tests. It then provides approaches for modifying legacy code like identifying what to change and test, breaking dependencies, writing tests, and refactoring code in small, tested increments. Specific tactics are presented like using seams, sprouting methods, and interfaces to break dependencies and allow testing legacy code. The importance of understanding the system and increasing test coverage before making changes is emphasized.
Try harder or go home
Try harder or go homejaredhaight This document provides tips for taking the OSCP certification exam, focusing on reconnaissance, exploitation, and pivoting. It recommends aggressively scanning all ports with NMAP, using tools like Dirbuster for web enumeration, and saving all findings. Exploitation advice includes using Searchsploit and Metasploit carefully according to exam rules, and getting comfortable with buffer overflows. The document also suggests scripting commonly used exploits, thoroughly pillaging compromised systems, and pivoting networks through SSH port forwarding or ProxyChains. Organizing notes and completing the required lab report are also emphasized.
Test-Driven Development (TDD) in Swift
Test-Driven Development (TDD) in SwiftAmey Tavkar The document discusses test-driven development (TDD) in Swift. It explains that TDD involves writing tests before implementation to gain confidence and verify requirements are met. Automated tests allow for faster regression testing, easier refactoring, and continuous integration. The document recommends writing tests first to produce loosely coupled code aligned with requirements. It provides examples of TDD best practices and common pitfalls to avoid.
Tdd in swift
Tdd in swiftJaval Nanda 1. The document discusses test-driven development (TDD) in Swift, including why it is important to write tests before implementation. Automated tests provide confidence, verification of requirements, and help identify weak areas of code.
2. TDD involves writing tests first to define requirements before writing any code. This forces developers to think about design and creates loosely coupled, independent code modules.
3. Common pitfalls to avoid in TDD include not testing behaviors, having dependent tests, not refactoring code, and testing private methods or external libraries. Best practices include using a good architecture, protocols to isolate classes, and structured tests with arrange, act, assert format.
Writing clean scientific software Murphy cleancoding
Writing clean scientific software Murphy cleancodingsaber tabatabaee The document provides an overview of Nick Murphy's background and work on the PlasmaPy open source software project. Some key points:
- Nick Murphy grew up in Michigan and has a background in astronomy, having done his graduate work simulating magnetic reconnection.
- PlasmaPy is an open source Python software ecosystem for plasma research and education. It includes core functionality, affiliated packages, educational resources, and an active community.
- The talk outlines best practices for writing clean, readable scientific software, including using descriptive names, comments, functions, tests, and separating high-level and low-level code. The goal is to make software more reusable, understandable, and to improve the research experience.
Fast end-to-end-tests
Fast end-to-end-testsRikke Veng Petersen This document summarizes Lars Thorup's presentation on fast end-to-end tests. It discusses the drawbacks of traditional end-to-end tests like being slow, imprecise, complicated and fragile. Unit tests are faster but rely on mocked dependencies. The presentation demonstrates a way to automatically generate mocks to test applications from end-to-end very quickly while avoiding the downsides of mocks. The demo shows a Node.js app with front-end and back-end tested at almost 100 end-to-end tests per second.
Super fast end-to-end-tests
Super fast end-to-end-testsLars Thorup Automated end-to-end tests are often seen as a necessary evil. A common example is Selenium-based browser tests. This kind of testing has many drawbacks: 1) They take a long time to run. 2) They require complicated setup. 3) They are fragile. But it doesn't have to be like that!
In this talk I describe how we can write automated end-to-end tests that are 1) Superfast. 2) As easy to setup as unit tests. 3) As robust as unit tests.
This technique is leveraging existing unit testing techniques. Tests for lower layers (such as server code) is instrumented to record all requests and responses in a log file. Tests for higher layers (like client code) is extended with an mocking layer that automatically configures with the contents of that log file.
It is then possible to run a almost a hundred end-to-end tests every second.
From Gatekeeper to Partner by Kelsey Shannahan
From Gatekeeper to Partner by Kelsey ShannahanQA or the Highway The document discusses moving from a "gatekeeper" model of testing, where testing is done separately after development, to a "partner" model where testing is integrated into development and shared responsibility of the team. It provides tips for making this transition, such as fixing problems developers experience with testing, integrating testing into development workflows, and helping testers contribute to other parts of development to become true partners. The overall message is that testing is most effective when it is easy to do and an inherent part of the development process done collaboratively by the entire team.
Value of Unit Testing
Value of Unit TestingFerose Khan J This document discusses unit testing and provides guidance on how to implement it. It defines unit testing and explains why it is important for refactoring code with confidence, understanding code design, and creating living documentation. It provides steps for setting up, running, and verifying unit tests and recommends testing behavior rather than methods. Specific dos and don'ts are outlined such as making tests fast, fully automated, and writing informative messages. A conversation is included that emphasizes the importance of continuing to write tests.
Coding standard let’s do it
Coding standard let’s do itMinh Quang Trần This document discusses coding standards and guidelines to improve code readability, testability, and maintainability. It recommends avoiding duplicate code, using single exit points from functions instead of else blocks, wrapping primitive types in objects, having only one variable assignment per line, keeping classes small with a limited number of lines, methods and classes, and references the Object Calisthenics principles for improving code quality.
Xtreme Programming
Xtreme ProgrammingPrasad Kancharla The document discusses concepts in agile development and extreme programming (XP), focusing on pair programming, test-driven development (TDD), and continuous integration (CI). It defines pair programming as two developers working together on a single task, switching roles frequently between driver and navigator. Benefits include better design, knowledge sharing, and code quality. TDD involves writing tests before code to drive design and ensure code quality. CI aims to integrate code changes frequently to catch errors early.
Test driven development_and_puppet-cfgmgmtcamp_eu-20140402
Test driven development_and_puppet-cfgmgmtcamp_eu-20140402Johan De Wit The slides of the talk i did on cfgmgmtcamp.eu, frebruary 4th 2014, looking at test driven development. This part is focused on the development of a custom puppet type
Introduction to Continuous Delivery
Introduction to Continuous DeliveryGiovanni Toraldo What we have learn the last year while developing ClouDesire, presented at an Apericoder event organized by Coders TUG in Pisa.
Pen Testing, Red Teaming, and More
Pen Testing, Red Teaming, and MoreCTruncer This is the slide deck that I used when presenting at FSU's Cyber Security Club. This presentation was supposed to give a description of what Red Teaming, Pen Testing, and other roles do.
More from Jano Suchal (20)
Beyond search queries
Beyond search queriesJano Suchal This document discusses search quality and optimization. It covers various metrics used to measure search quality like mean average precision and expected reciprocal rank. It also discusses using clickthrough data and implicit feedback to optimize search engines by analyzing query chains, repeated results, and A/B testing with interleaving. The document promotes a service called searchd.co that provides search analytics to help identify problems, test changes safely, and improve the search experience.
Rank all the things!
Rank all the things!Jano Suchal This document discusses various topics related to machine learning including recommender systems, search engines, academic papers, and challenges. It also provides biographical information about the author, their work experience including with recommender engines and news recommendations, and their invitation for others to contact them to discuss serious recommenders and search.
Rank all the (geo) things!
Rank all the (geo) things!Jano Suchal This document discusses machine learning techniques for ranking and recommending information. It covers several academic papers on learning to rank, optimizing search engines using click data, and challenges in diversification, group recommendations, and context-aware recommendations. Examples of context include time of day, device, mood, season, and location. The document encourages getting in touch to discuss serious recommenders and search.
Bonetics: Mastering Puppet Workshop
Bonetics: Mastering Puppet WorkshopJano Suchal This document provides an overview and walkthrough for mastering puppet configuration management. It introduces puppet and compares it to other solutions like Chef and CFEngine. It outlines puppet's client/server model and covers setting up the master directory structure and configuring agents. The document explains puppet's resource types and manifest syntax. It also provides instructions for setting up an environment and implementing a sample configuration for packages, services, and files.
Peter Mihalik: Puppet
Peter Mihalik: PuppetJano Suchal Hammer of the Sysadmins based on puppet, git and redmine. Managing complex infrastructure producing 1/3 of slovak peering traffic in peaks. joj.sk, noviny.sk, huste.tv, tipsportextraliga.sk, prohokej.sk
Tomáš Čorej: Configuration management & CFEngine3
Tomáš Čorej: Configuration management & CFEngine3Jano Suchal CFEngine is the oldest tool for configuration management that inspired Puppet & Chef. Features like model-based monitoring, promise theory and knowledge management support makes it an reasonable alternative for IT system automatization.
SQL: Query optimization in practice
SQL: Query optimization in practiceJano Suchal How the query planner in PostgreSQL works? Index access methods, join execution types, aggregation & pipelining. Optimizing queries with WHERE conditions, ORDER BY and GROUP BY. Composite indexes, partial and expression indexes. Exploiting assumptions about data and denormalization.
Garelic: Google Analytics as App Performance monitoring
Garelic: Google Analytics as App Performance monitoringJano Suchal This document describes Garelic, an open source tool that allows using Google Analytics for app performance monitoring. It explains how Garelic uses Google Analytics features like User Timing and Custom Variables to track metrics like controller and ActiveRecord response times. Garelic implements this by monkey patching Rails and subscribing to ActiveSupport notifications to capture timing data and report it to Google Analytics. Some limitations are that it can't track redirects, AJAX, or jobs, and page caching breaks reports. Ideas for future work include error tracking and thresholding for slow responses only.
Miroslav Šimulčík: Temporálne databázy
Miroslav Šimulčík: Temporálne databázyJano Suchal Temporálne databázy umožňujú zachytávať históriu biznisových a systémových zmien dát a poskytujú prostriedky na pohodlnú prácu s historickými dátami. Majú široké uplatnenie v rôznych sektoroch ako napríklad poisťovníctvo, bankovníctvo či rezervačné systémy. Umožňujú jednoduché kontrolovanie vykonaných zmien, návrat k predchádzajúcim stavom dát a rôzne analytické dotazy nad históriou. V rámci prezentácie sa budem venovať všeobecnému prehľadu oblasti, existujúcim štandardom (napr. SQL:2011) a riešeniam a na jednoduchých príkladoch predvediem hlavnú funkcionalitu temporálnych databáz. Nakoniec ešte načrtnem možnosti pridania temporálnej podpory do Postgresql a porozprávam aj o tom, ako sa snažím temporálnu podporu dostať do oficiálneho release a čo všetko také niečo obnáša.
Profiling and monitoring ruby & rails applications
Profiling and monitoring ruby & rails applicationsJano Suchal The document discusses profiling and monitoring Ruby on Rails applications. It provides examples of using the ruby-prof gem to profile a Ruby script and identify bottlenecks. It also discusses using NewRelic to monitor production applications and track metrics like web transactions, SQL queries, background jobs, and errors. Common performance issues mentioned include the N+1 query problem, lack of indexing, unnecessary ActiveRecord loading, default GC parameters, and unknown abstraction internals.
Metaprogramovanie #1
Metaprogramovanie #1Jano Suchal The document discusses the key concepts of metaprogramming in Ruby including dynamic method lookup, open classes, modules, callbacks, and dynamic method definition. Some examples provided include defining accessor methods using modules, extending classes with module methods, defining instance and class methods dynamically, and hooking into callbacks to add functionality. Metaprogramming allows code to generate and modify code at runtime enabling powerful abstractions.
PostgreSQL: Advanced features in practice
PostgreSQL: Advanced features in practiceJano Suchal The document discusses several advanced features of PostgreSQL including:
1) Transactional DDL which allows DDL statements to be executed transactionally.
2) Cost-based query optimization and graphical EXPLAIN plans which help choose the most efficient query plan.
3) Features like partial indexes, function indexes, k-nearest search, views, and window functions which provide powerful ways to query and analyze data.
Ad
Recently uploaded (20)
Enhancing ICU Intelligence: How Our Functional Testing Enabled a Healthcare I...
Enhancing ICU Intelligence: How Our Functional Testing Enabled a Healthcare I...Impelsys Inc. Impelsys provided a robust testing solution, leveraging a risk-based and requirement-mapped approach to validate ICU Connect and CritiXpert. A well-defined test suite was developed to assess data communication, clinical data collection, transformation, and visualization across integrated devices.
IEDM 2024 Tutorial2_Advances in CMOS Technologies and Future Directions for C...
IEDM 2024 Tutorial2_Advances in CMOS Technologies and Future Directions for C...organizerofv IEDM 2024 Tutorial2
Cyber Awareness overview for 2025 month of security
Cyber Awareness overview for 2025 month of securityriccardosl1 Cyber awareness training educates employees on risk associated with internet and malicious emails
Role of Data Annotation Services in AI-Powered Manufacturing
Role of Data Annotation Services in AI-Powered ManufacturingAndrew Leo From predictive maintenance to robotic automation, AI is driving the future of manufacturing. But without high-quality annotated data, even the smartest models fall short.
Discover how data annotation services are powering accuracy, safety, and efficiency in AI-driven manufacturing systems.
Precision in data labeling = Precision on the production floor.
AI Changes Everything – Talk at Cardiff Metropolitan University, 29th April 2...
AI Changes Everything – Talk at Cardiff Metropolitan University, 29th April 2...Alan Dix Talk at the final event of Data Fusion Dynamics: A Collaborative UK-Saudi Initiative in Cybersecurity and Artificial Intelligence funded by the British Council UK-Saudi Challenge Fund 2024, Cardiff Metropolitan University, 29th April 2025
https://alandix.com/academic/talks/CMet2025-AI-Changes-Everything/
Is AI just another technology, or does it fundamentally change the way we live and think?
Every technology has a direct impact with micro-ethical consequences, some good, some bad. However more profound are the ways in which some technologies reshape the very fabric of society with macro-ethical impacts. The invention of the stirrup revolutionised mounted combat, but as a side effect gave rise to the feudal system, which still shapes politics today. The internal combustion engine offers personal freedom and creates pollution, but has also transformed the nature of urban planning and international trade. When we look at AI the micro-ethical issues, such as bias, are most obvious, but the macro-ethical challenges may be greater.
At a micro-ethical level AI has the potential to deepen social, ethnic and gender bias, issues I have warned about since the early 1990s! It is also being used increasingly on the battlefield. However, it also offers amazing opportunities in health and educations, as the recent Nobel prizes for the developers of AlphaFold illustrate. More radically, the need to encode ethics acts as a mirror to surface essential ethical problems and conflicts.
At the macro-ethical level, by the early 2000s digital technology had already begun to undermine sovereignty (e.g. gambling), market economics (through network effects and emergent monopolies), and the very meaning of money. Modern AI is the child of big data, big computation and ultimately big business, intensifying the inherent tendency of digital technology to concentrate power. AI is already unravelling the fundamentals of the social, political and economic world around us, but this is a world that needs radical reimagining to overcome the global environmental and human challenges that confront us. Our challenge is whether to let the threads fall as they may, or to use them to weave a better future.
Increasing Retail Store Efficiency How can Planograms Save Time and Money.pptx
Increasing Retail Store Efficiency How can Planograms Save Time and Money.pptxAnoop Ashok In today's fast-paced retail environment, efficiency is key. Every minute counts, and every penny matters. One tool that can significantly boost your store's efficiency is a well-executed planogram. These visual merchandising blueprints not only enhance store layouts but also save time and money in the process.
Noah Loul Shares 5 Steps to Implement AI Agents for Maximum Business Efficien...
Noah Loul Shares 5 Steps to Implement AI Agents for Maximum Business Efficien...Noah Loul Artificial intelligence is changing how businesses operate. Companies are using AI agents to automate tasks, reduce time spent on repetitive work, and focus more on high-value activities. Noah Loul, an AI strategist and entrepreneur, has helped dozens of companies streamline their operations using smart automation. He believes AI agents aren't just tools—they're workers that take on repeatable tasks so your human team can focus on what matters. If you want to reduce time waste and increase output, AI agents are the next move.
TrustArc Webinar: Consumer Expectations vs Corporate Realities on Data Broker...
TrustArc Webinar: Consumer Expectations vs Corporate Realities on Data Broker...TrustArc Most consumers believe they’re making informed decisions about their personal data—adjusting privacy settings, blocking trackers, and opting out where they can. However, our new research reveals that while awareness is high, taking meaningful action is still lacking. On the corporate side, many organizations report strong policies for managing third-party data and consumer consent yet fall short when it comes to consistency, accountability and transparency.
This session will explore the research findings from TrustArc’s Privacy Pulse Survey, examining consumer attitudes toward personal data collection and practical suggestions for corporate practices around purchasing third-party data.
Attendees will learn:
- Consumer awareness around data brokers and what consumers are doing to limit data collection
- How businesses assess third-party vendors and their consent management operations
- Where business preparedness needs improvement
- What these trends mean for the future of privacy governance and public trust
This discussion is essential for privacy, risk, and compliance professionals who want to ground their strategies in current data and prepare for what’s next in the privacy landscape.
Into The Box Conference Keynote Day 1 (ITB2025)
Into The Box Conference Keynote Day 1 (ITB2025)Ortus Solutions, Corp This is the keynote of the Into the Box conference, highlighting the release of the BoxLang JVM language, its key enhancements, and its vision for the future.
Quantum Computing Quick Research Guide by Arthur Morgan
Quantum Computing Quick Research Guide by Arthur MorganArthur Morgan This is a Quick Research Guide (QRG).
QRGs include the following:
- A brief, high-level overview of the QRG topic.
- A milestone timeline for the QRG topic.
- Links to various free online resource materials to provide a deeper dive into the QRG topic.
- Conclusion and a recommendation for at least two books available in the SJPL system on the QRG topic.
QRGs planned for the series:
- Artificial Intelligence QRG
- Quantum Computing QRG
- Big Data Analytics QRG
- Spacecraft Guidance, Navigation & Control QRG (coming 2026)
- UK Home Computing & The Birth of ARM QRG (coming 2027)
Any questions or comments?
- Please contact Arthur Morgan at [email protected].
100% human made.
Technology Trends in 2025: AI and Big Data Analytics
Technology Trends in 2025: AI and Big Data AnalyticsInData Labs At InData Labs, we have been keeping an ear to the ground, looking out for AI-enabled digital transformation trends coming our way in 2025. Our report will provide a look into the technology landscape of the future, including:
-Artificial Intelligence Market Overview
-Strategies for AI Adoption in 2025
-Anticipated drivers of AI adoption and transformative technologies
-Benefits of AI and Big data for your business
-Tips on how to prepare your business for innovation
-AI and data privacy: Strategies for securing data privacy in AI models, etc.
Download your free copy nowand implement the key findings to improve your business.
AI EngineHost Review: Revolutionary USA Datacenter-Based Hosting with NVIDIA ...
AI EngineHost Review: Revolutionary USA Datacenter-Based Hosting with NVIDIA ...SOFTTECHHUB I started my online journey with several hosting services before stumbling upon Ai EngineHost. At first, the idea of paying one fee and getting lifetime access seemed too good to pass up. The platform is built on reliable US-based servers, ensuring your projects run at high speeds and remain safe. Let me take you step by step through its benefits and features as I explain why this hosting solution is a perfect fit for digital entrepreneurs.
Designing Low-Latency Systems with Rust and ScyllaDB: An Architectural Deep Dive
Designing Low-Latency Systems with Rust and ScyllaDB: An Architectural Deep DiveScyllaDB Want to learn practical tips for designing systems that can scale efficiently without compromising speed?
Join us for a workshop where we’ll address these challenges head-on and explore how to architect low-latency systems using Rust. During this free interactive workshop oriented for developers, engineers, and architects, we’ll cover how Rust’s unique language features and the Tokio async runtime enable high-performance application development.
As you explore key principles of designing low-latency systems with Rust, you will learn how to:
- Create and compile a real-world app with Rust
- Connect the application to ScyllaDB (NoSQL data store)
- Negotiate tradeoffs related to data modeling and querying
- Manage and monitor the database for consistently low latencies
What is Model Context Protocol(MCP) - The new technology for communication bw...
What is Model Context Protocol(MCP) - The new technology for communication bw...Vishnu Singh Chundawat The MCP (Model Context Protocol) is a framework designed to manage context and interaction within complex systems. This SlideShare presentation will provide a detailed overview of the MCP Model, its applications, and how it plays a crucial role in improving communication and decision-making in distributed systems. We will explore the key concepts behind the protocol, including the importance of context, data management, and how this model enhances system adaptability and responsiveness. Ideal for software developers, system architects, and IT professionals, this presentation will offer valuable insights into how the MCP Model can streamline workflows, improve efficiency, and create more intuitive systems for a wide range of use cases.
Procurement Insights Cost To Value Guide.pptx
Procurement Insights Cost To Value Guide.pptxJon Hansen Procurement Insights integrated Historic Procurement Industry Archives, serves as a powerful complement — not a competitor — to other procurement industry firms. It fills critical gaps in depth, agility, and contextual insight that most traditional analyst and association models overlook.
Learn more about this value- driven proprietary service offering here.
Manifest Pre-Seed Update | A Humanoid OEM Deeptech In France
Manifest Pre-Seed Update | A Humanoid OEM Deeptech In Francechb3 The latest updates on Manifest's pre-seed stage progress.
2025-05-Q4-2024-Investor-Presentation.pptx
2025-05-Q4-2024-Investor-Presentation.pptxSamuele Fogagnolo Cloudflare Q4 Financial Results Presentation
HCL Nomad Web – Best Practices and Managing Multiuser Environments
HCL Nomad Web – Best Practices and Managing Multiuser Environmentspanagenda Webinar Recording: https://www.panagenda.com/webinars/hcl-nomad-web-best-practices-and-managing-multiuser-environments/
HCL Nomad Web is heralded as the next generation of the HCL Notes client, offering numerous advantages such as eliminating the need for packaging, distribution, and installation. Nomad Web client upgrades will be installed “automatically” in the background. This significantly reduces the administrative footprint compared to traditional HCL Notes clients. However, troubleshooting issues in Nomad Web present unique challenges compared to the Notes client.
Join Christoph and Marc as they demonstrate how to simplify the troubleshooting process in HCL Nomad Web, ensuring a smoother and more efficient user experience.
In this webinar, we will explore effective strategies for diagnosing and resolving common problems in HCL Nomad Web, including
- Accessing the console
- Locating and interpreting log files
- Accessing the data folder within the browser’s cache (using OPFS)
- Understand the difference between single- and multi-user scenarios
- Utilizing Client Clocking
DevOpsDays Atlanta 2025 - Building 10x Development Organizations.pptx
DevOpsDays Atlanta 2025 - Building 10x Development Organizations.pptxJustin Reock Building 10x Organizations with Modern Productivity Metrics
10x developers may be a myth, but 10x organizations are very real, as proven by the influential study performed in the 1980s, ‘The Coding War Games.’
Right now, here in early 2025, we seem to be experiencing YAPP (Yet Another Productivity Philosophy), and that philosophy is converging on developer experience. It seems that with every new method we invent for the delivery of products, whether physical or virtual, we reinvent productivity philosophies to go alongside them.
But which of these approaches actually work? DORA? SPACE? DevEx? What should we invest in and create urgency behind today, so that we don’t find ourselves having the same discussion again in a decade?
What is Model Context Protocol(MCP) - The new technology for communication bw...
What is Model Context Protocol(MCP) - The new technology for communication bw...Vishnu Singh Chundawat
Ad
Improving code quality
- 2. Issues 1. Doing the wrong thing 2. Excessive coupling 3. Mutable state 4. Premature abstraction 5. Edge conditions
- 4. Outside-in development ● Start at the very top ○ discover dependencies ○ avoids unit interface incompatibility problem ○ how would I test this? ● Programming by wishful thinking ○ design usage, review/discuss, implement later, refactor a lot later ○ do / refactor mode
- 5. TDD ● Acceptance (end-to-end) tests ○ start here! ○ nonexhaustive (avoid exponential blowup) ● Unit tests ○ a design tool ○ a testing tool
- 8. Immutable OO ● Best trick for maintainable code, by far! ● All fields immutable ● Mental trick ○ obj.method(*args) == method(Class obj, *args) ● Code smells are obvious ● Temporal coupling is impossible ● OOP finally makes sense
- 9. Smell-Driven Development ● private / protected ○ missing collaborator, extract & inject ● not using all fields ○ class doing too much, split ● prefixes ○ missing abstraction, extract & inject ● returning self or void ○ mutable state, avoid! ● duplicated logic in parent method ○ inject listener/responder
- 10. Smell-Driven Development (2) ● Law of Demeter (one dot rule) ○ getters are ok! ● Avoid global constants ○ a.k.a. implicit dependencies ○ yes, class name is a constant ● Data Clump, Feature Envy ● Test smells
- 11. Premature abstraction ● “Third time is the charm.” ● KISS ● YAGNI
- 12. Tools ● rubocop ○ the code style grammar nazi ● reek ○ code smell detection ● mutant ○ mutation testing ● mbj/devtools ○ the CI task!