What do software engineers do
•
0 likes•52 views
Software engineers design, develop, test, and maintain software applications. They analyze user needs to determine requirements, design and code software solutions, conduct testing, and release updates. Common roles include front-end engineers who work on user interfaces, back-end engineers who focus on server-side code, full-stack engineers who work across front-end and back-end, QA engineers who test software, DevOps engineers who manage infrastructure, and security engineers who ensure software safety. A typical day involves researching solutions, writing code, collaborating with others, and releasing updates.
Report
Share
Report
Share
Download to read offline
Recommended
How to code in the XXI century without losing your head
This document discusses how to code effectively in the 21st century without being distracted by unnecessary noise. It identifies several types of noise that can prevent developers from delivering quality products, such as debates over programming languages and frameworks, premature optimization, editor preferences, and testing methodologies. The document recommends focusing on quality over optimization or new technologies, using the right tools for the job, implementing some testing, and agreeing on style guidelines to streamline collaboration. Overall, it encourages blocking out distracting debates and prioritizing effective development practices suited to the project.
Simple vs Easy
This document discusses the differences between simple and easy in software development. It argues that while ease provides initial speed, simplicity is better for long-term development and maintenance. Simple software uses single roles, tasks, concepts and dimensions, is objective, and is within our skills and capabilities. The document recommends writing simple code using constructs that generate simple artifacts, abstracting to simplify problems, and not over-engineering solutions. Overall it promotes composing simple components and modularity to achieve strong, maintainable software through simplicity rather than complexity.
Open source software best practices
This document discusses best practices for open source software. It defines open source software as software with source code that is publicly accessible and modifiable. Open source software is characterized by its community, collaboration, transparency, and innovation. However, it also carries risks related to licensing, operations, and security that must be managed. The document provides recommendations for open source risk mitigation and best practices for both utilizing and contributing to open source projects.
Improve your TDD skills
An amazing opportunity for all the coders to improve their TDD skills in a safe and thrilling environment. Our lab is a 3 hours intensive practice event, focusing on the practice of TDD, essential for software development and design, away from the pressures of ‘getting things done’.
Functional Prototyping For Mobile Apps
This document discusses functional prototyping for mobile apps. It begins by defining various types of prototypes like paper drawings, wireframes, and mockups. It then outlines several popular prototyping tools like POP, Balsamiq, Flinto, and Marvel. The document emphasizes that prototyping can save significant money on app development projects by clarifying requirements and creating a unified vision. It also argues for cross-functional teams that include disciplines like security, testing, and operations from the beginning rather than as an afterthought. Finally, it provides some resources for prototyping with Sketch and Framer.
Run your project like it's an OpenSource project
Use the lessons learned from open source projects for all your projects, even internal ones.
In this talk, we discuss the three challenges all software projects face and how open source addresses these challenges.
The Software Craftsman (2nd edition)
The document discusses the need for "Software Craftsmen" who take pride in their work and continuously hone their skills. A Software Craftsman will choose quality over speed and takes responsibility for their work. The document outlines tips for becoming a Software Craftsman, such as learning techniques like test-driven development, practicing through code katas and dojos, and working on real projects. Software Craftsmen are needed because they avoid producing bad code through deliberate practice and skill development.
The Software Craftsman
This document discusses the need for software craftsmen and their characterization. It defines a software craftsman as someone who chooses to "get it right" over just "getting it done", takes responsibility for their work, and is a continuous learner. It recommends ways for developers to become craftsmen, such as practicing techniques like TDD, refactoring, and contributing to the community.
Recommended
How to code in the XXI century without losing your head
This document discusses how to code effectively in the 21st century without being distracted by unnecessary noise. It identifies several types of noise that can prevent developers from delivering quality products, such as debates over programming languages and frameworks, premature optimization, editor preferences, and testing methodologies. The document recommends focusing on quality over optimization or new technologies, using the right tools for the job, implementing some testing, and agreeing on style guidelines to streamline collaboration. Overall, it encourages blocking out distracting debates and prioritizing effective development practices suited to the project.
Simple vs Easy
This document discusses the differences between simple and easy in software development. It argues that while ease provides initial speed, simplicity is better for long-term development and maintenance. Simple software uses single roles, tasks, concepts and dimensions, is objective, and is within our skills and capabilities. The document recommends writing simple code using constructs that generate simple artifacts, abstracting to simplify problems, and not over-engineering solutions. Overall it promotes composing simple components and modularity to achieve strong, maintainable software through simplicity rather than complexity.
Open source software best practices
This document discusses best practices for open source software. It defines open source software as software with source code that is publicly accessible and modifiable. Open source software is characterized by its community, collaboration, transparency, and innovation. However, it also carries risks related to licensing, operations, and security that must be managed. The document provides recommendations for open source risk mitigation and best practices for both utilizing and contributing to open source projects.
Improve your TDD skills
An amazing opportunity for all the coders to improve their TDD skills in a safe and thrilling environment. Our lab is a 3 hours intensive practice event, focusing on the practice of TDD, essential for software development and design, away from the pressures of ‘getting things done’.
Functional Prototyping For Mobile Apps
This document discusses functional prototyping for mobile apps. It begins by defining various types of prototypes like paper drawings, wireframes, and mockups. It then outlines several popular prototyping tools like POP, Balsamiq, Flinto, and Marvel. The document emphasizes that prototyping can save significant money on app development projects by clarifying requirements and creating a unified vision. It also argues for cross-functional teams that include disciplines like security, testing, and operations from the beginning rather than as an afterthought. Finally, it provides some resources for prototyping with Sketch and Framer.
Run your project like it's an OpenSource project
Use the lessons learned from open source projects for all your projects, even internal ones.
In this talk, we discuss the three challenges all software projects face and how open source addresses these challenges.
The Software Craftsman (2nd edition)
The document discusses the need for "Software Craftsmen" who take pride in their work and continuously hone their skills. A Software Craftsman will choose quality over speed and takes responsibility for their work. The document outlines tips for becoming a Software Craftsman, such as learning techniques like test-driven development, practicing through code katas and dojos, and working on real projects. Software Craftsmen are needed because they avoid producing bad code through deliberate practice and skill development.
The Software Craftsman
This document discusses the need for software craftsmen and their characterization. It defines a software craftsman as someone who chooses to "get it right" over just "getting it done", takes responsibility for their work, and is a continuous learner. It recommends ways for developers to become craftsmen, such as practicing techniques like TDD, refactoring, and contributing to the community.
Ssi maintainers
The document discusses enabling smooth transitions between software maintainers. It suggests that when inducting a new maintainer, an experienced maintainer should discuss the software's design, develop code together, and walk through the code. For self-guided learning, documentation like user docs, tests, design docs and commented source code can help navigate understanding. When inheriting a large codebase, inspecting the code, documenting assumptions and designs, and writing tests and user docs creates resources to help future maintainers. Well structured code with tests that demonstrate functionality form a minimal effective handover.
Menggapai Paripurna Rekayasa
“Engineering Excellence”
Menggapai Paripurna Rekayasa
by
Ariya Hidayat
Former VP Engineering at Shape Security
PhantomJS Creator
Engineering Excellence!
22-Jan-2019 18:00-21:00
@ PRASMUL University Prasetiya Mulya University, Campus Cilandak Cilandak Barat, RT.14/RW.6, Jl. R.A.Kartini, RT.14/RW.6, Cilandak
Organizer by Software Architect Indonesia Community (SARCCOM)
https://sarccom.org
TDD with Rails
Andrzej Krzywda is a software developer who has been using Test Driven Development (TDD) since 2001. TDD involves writing tests before production code to help visualize goals and requirements. The tests help achieve project goals and requirements by ensuring the code works as intended. TDD uses both acceptance tests to verify functionality meets requirements, and unit tests to ensure code quality.
Встреча Quality built in @Spotify от Андрея Дзыни : как стать лучшим тестиров...
This document summarizes Spotify's approach to continuous delivery and building quality into software development. It discusses that quality involves meeting stakeholder expectations, and the importance of quality to reduce costs from bugs. Spotify emphasizes automated testing from unit to integration levels. They implement a delivery pipeline to continuously integrate and deploy code. Other practices include code reviews, monitoring, and allowing employees time for experiments.
Kung fu Programming
The document discusses principles for agile programming based on lessons from Kung Fu Panda. It recommends frequently testing code through a variety of automated tests. Programmers should integrate code daily and follow common coding standards and conventions as a team. Pair programming and collaboration are emphasized to reduce bugs and spread knowledge. Simplicity and shipping working code each sprint are priorities over unnecessary features. Finding a balance with occasional refactoring is important for maintaining focus.
A Test Manifesto 2014.03.26
Last year we were challenged to build an agile test team to work in different products and technologies for 8 distributed teams from 3 to 7 people. We had to break with legacy assumptions on how testing should be enacted while keeping company policies. And most of all, we had to make sure everyone is enabled to do the best possible job.
Enabling a team is about motivation, trust and simplifying decision making processes. The test team as a whole has to scale and fit for multiple scenarios and projects. Every team member had a different background and needs so no policies would really apply to all. Or worst, we would be spending time twisting the rules to fit each case.
First, we decided to coordinate as a guild. Second, we issued this Test Manifest as a declaration of purpose and discipline.
TDD for Testers
This document provides an overview of test driven development (TDD) principles and benefits. It discusses how TDD can be applied to both new and legacy code projects. The key benefits of TDD include better test coverage, less debugging, and improved design. Applying TDD requires discipline to write tests before code in small incremental steps. The document concludes that TDD is a valuable technique for all types of projects that requires persistence.
16 Favorite Behavioral Interview Questions for Technical Roles
It’s important to note that when you ask these questions, it’s vital to ensure they are fully answered so that you get complete behavioral examples. We recommend using the SCOPE Model. If a candidate doesn’t complete components of SCOPE for a given question, ask a follow-up question to get the information you need.
For the full blog: https://bit.ly/2SYmMKY
Test Driven Development
Test-driven development allows developers to find and fix bugs more quickly by writing automated tests before developing code. This reduces debugging time and improves productivity. Constant testing is crucial for short release cycles and gives developers confidence to refactor and improve code quality throughout development. Automated testing enables developers to test thoroughly without losing focus.
[XPday.vn] Legacy code workshop (at) [XP Day Vietnam 2015]
Stanly Lau is an agile coach and software developer based in Singapore who has worked with companies of various sizes in industries such as insurance, mobile safety, education, logistics, and banking. The document discusses legacy code and provides tips on how to deal with it. Legacy code is defined as code without unit tests that is difficult to change and prone to bugs. It recommends adopting modern engineering practices like test-driven development and refactoring. It also outlines an approach for identifying change points, breaking dependencies, writing tests, and then making changes to legacy code in a safe manner.
Collaboration, Languages and Big Data, Anne Sophie Roessler, Deployment Strat...
"Collaboration, Languages and Big Data", Anne Sophie Roessler, Deployment Strategist at Dataiku
YouTube Link: https://www.youtube.com/watch?v=9_pBIWOw3y0
Watch more from Data Natives 2015
Visit the conference website to learn more: www.datanatives.io
Subscribe to Data Natives on YouTube!
Stay Connected to Dataconomy Media by Email: Subscribe to our weekly newsletter to never miss out! (http://goo.gl/JX2GWw)
Follow Dataconomy Media:
https://plus.google.com/+Dataconomy1/videos
https://www.facebook.com/DataconomyMedia
https://twitter.com/DataconomyMedia
Software Craftsmanship @ Ntnu
The document discusses software craftsmanship and test-driven development (TDD). It notes that software craftsmanship is about raising the bar, taking pride in work, discipline, continuous learning, and deliberate practice. TDD's goal is to write clean code that works, following the Red-Green-Refactor mantra of writing a failing test, making it pass quickly, and refactoring code. The document promotes writing clean code because it is less expensive to maintain and leads to better programmers and productivity.
Taming scary production code that nobody wants to touch
This document discusses strategies for working with legacy code that lacks tests, which is considered risky to change. It recommends using core refactorings to safely introduce tests and characterization tests to describe and protect existing behavior without changing it. Peeling away dependencies and slicing code into testable units also helps reduce risk when modifying untested code. The goal is to make legacy code less scary and easier to change over time by adding tests and refactoring carefully.
Software testing Basic
Nghi Nguyen will present on software testing, including an overview of the software testing life cycle, levels and types of testing, characteristics of a great tester, and how to deal with developers. The presentation will cover requirements analysis, test planning, test case development, test execution, and test closure. It will discuss functional and non-functional testing and characteristics like being honest, open, and using a bug tracker when working with developers.
What would Jesus Developer do?
This document discusses applying developer best practices to digital analytics work. It recommends:
1) Using local development with Node.js, build tools, and IDEs to avoid copy-pasting code and work offline.
2) Implementing version control like Git for change history, issue tracking, and teamwork.
3) Writing modular, reusable code through organization conventions and build tools to localize issues.
4) Taking an API-based approach can create a single codebase for multiple properties with continuous integration and auto-generated documentation.
Introduction to unit testing
This document introduces unit testing and its benefits. It discusses different types of testing, including manual testing and unit testing. Unit testing provides quick feedback, confidence to refactor code, and knowledge that code works before QA testing. The document recommends using xUnit frameworks for unit testing in .NET and promotes test-driven development as a way to achieve great test coverage and improved code design. It concludes with inviting questions.
DevOps for Engineers
The main goal of this session is to answer what DevOps is, why it started, and how it will help you. It sheds some light on DevOps in action.
This session was part of Talents Arena's virtual tech job fair 2020.
Unwritten Manual for Pair Programming
This document discusses pair programming and provides guidance on how to effectively implement it. It begins by explaining the purpose of pair programming is to produce high quality software. It then discusses various pairing techniques like ping-pong pairing and mob programming. The document also identifies benefits like higher quality code and faster defect removal, as well as challenges like being tiring. Finally, it provides tips for making pairing work well such as starting with a defined task, switching roles frequently, and not forcing people who strongly dislike pairing.
Use The Source Join The Force by Mark Steve Samson | DevCon Summit 2015 #GoO...
This document provides guidance on contributing to open source software projects. It discusses reasons to contribute such as sharing knowledge, career opportunities, learning, and scratching personal itches. The document also provides tips on finding projects to contribute to, such as contributing to projects you already use or following notable developers. Finally, it outlines various ways to contribute, including contributing code, submitting bug reports and feature requests, improving documentation, providing support, and donating money. The overall message is that open source development benefits both individual developers and society by promoting collaboration and advancing technology.
Getting to production
This document discusses lessons learned about getting software to production. It introduces Mike, a student of deploying software easily, and covers configuration management, the roles of developers and operations staff, and why communication between the two is important. Typical project lifecycles are discussed along with common problems that arise when developers don't consider operational needs or when operations rejects changes too often. The document promotes establishing a simple, repeatable release process and provides reading recommendations on the topic.
Agile Development: Key to smart software development
The document discusses key aspects of adopting an agile development workflow including having daily stand up meetings to discuss progress, taking an iterative development approach with working software delivered each sprint, and conducting retrospectives at the end of each sprint to improve. Adopting agile practices helps ensure working software is delivered frequently for stakeholder feedback, allows skills and the product to evolve together, and prevents waste through continuous testing.
Software engineer.pdf
A software engineer designs and creates computer systems and applications to solve real-world problems. Their responsibilities include designing and maintaining software systems, evaluating and testing new programs, optimizing software, writing and testing code, and consulting with security specialists. A chief architect provides the best work environment and allows teams to work integrated using technologies. As chief architect, they understand software programs and technology to develop solutions like LANs, WANs, and intranets for a company, while assisting employees with technology use and information.
More Related Content
What's hot
Ssi maintainers
The document discusses enabling smooth transitions between software maintainers. It suggests that when inducting a new maintainer, an experienced maintainer should discuss the software's design, develop code together, and walk through the code. For self-guided learning, documentation like user docs, tests, design docs and commented source code can help navigate understanding. When inheriting a large codebase, inspecting the code, documenting assumptions and designs, and writing tests and user docs creates resources to help future maintainers. Well structured code with tests that demonstrate functionality form a minimal effective handover.
Menggapai Paripurna Rekayasa
“Engineering Excellence”
Menggapai Paripurna Rekayasa
by
Ariya Hidayat
Former VP Engineering at Shape Security
PhantomJS Creator
Engineering Excellence!
22-Jan-2019 18:00-21:00
@ PRASMUL University Prasetiya Mulya University, Campus Cilandak Cilandak Barat, RT.14/RW.6, Jl. R.A.Kartini, RT.14/RW.6, Cilandak
Organizer by Software Architect Indonesia Community (SARCCOM)
https://sarccom.org
TDD with Rails
Andrzej Krzywda is a software developer who has been using Test Driven Development (TDD) since 2001. TDD involves writing tests before production code to help visualize goals and requirements. The tests help achieve project goals and requirements by ensuring the code works as intended. TDD uses both acceptance tests to verify functionality meets requirements, and unit tests to ensure code quality.
Встреча Quality built in @Spotify от Андрея Дзыни : как стать лучшим тестиров...
This document summarizes Spotify's approach to continuous delivery and building quality into software development. It discusses that quality involves meeting stakeholder expectations, and the importance of quality to reduce costs from bugs. Spotify emphasizes automated testing from unit to integration levels. They implement a delivery pipeline to continuously integrate and deploy code. Other practices include code reviews, monitoring, and allowing employees time for experiments.
Kung fu Programming
The document discusses principles for agile programming based on lessons from Kung Fu Panda. It recommends frequently testing code through a variety of automated tests. Programmers should integrate code daily and follow common coding standards and conventions as a team. Pair programming and collaboration are emphasized to reduce bugs and spread knowledge. Simplicity and shipping working code each sprint are priorities over unnecessary features. Finding a balance with occasional refactoring is important for maintaining focus.
A Test Manifesto 2014.03.26
Last year we were challenged to build an agile test team to work in different products and technologies for 8 distributed teams from 3 to 7 people. We had to break with legacy assumptions on how testing should be enacted while keeping company policies. And most of all, we had to make sure everyone is enabled to do the best possible job.
Enabling a team is about motivation, trust and simplifying decision making processes. The test team as a whole has to scale and fit for multiple scenarios and projects. Every team member had a different background and needs so no policies would really apply to all. Or worst, we would be spending time twisting the rules to fit each case.
First, we decided to coordinate as a guild. Second, we issued this Test Manifest as a declaration of purpose and discipline.
TDD for Testers
This document provides an overview of test driven development (TDD) principles and benefits. It discusses how TDD can be applied to both new and legacy code projects. The key benefits of TDD include better test coverage, less debugging, and improved design. Applying TDD requires discipline to write tests before code in small incremental steps. The document concludes that TDD is a valuable technique for all types of projects that requires persistence.
16 Favorite Behavioral Interview Questions for Technical Roles
It’s important to note that when you ask these questions, it’s vital to ensure they are fully answered so that you get complete behavioral examples. We recommend using the SCOPE Model. If a candidate doesn’t complete components of SCOPE for a given question, ask a follow-up question to get the information you need.
For the full blog: https://bit.ly/2SYmMKY
Test Driven Development
Test-driven development allows developers to find and fix bugs more quickly by writing automated tests before developing code. This reduces debugging time and improves productivity. Constant testing is crucial for short release cycles and gives developers confidence to refactor and improve code quality throughout development. Automated testing enables developers to test thoroughly without losing focus.
[XPday.vn] Legacy code workshop (at) [XP Day Vietnam 2015]
Stanly Lau is an agile coach and software developer based in Singapore who has worked with companies of various sizes in industries such as insurance, mobile safety, education, logistics, and banking. The document discusses legacy code and provides tips on how to deal with it. Legacy code is defined as code without unit tests that is difficult to change and prone to bugs. It recommends adopting modern engineering practices like test-driven development and refactoring. It also outlines an approach for identifying change points, breaking dependencies, writing tests, and then making changes to legacy code in a safe manner.
Collaboration, Languages and Big Data, Anne Sophie Roessler, Deployment Strat...
"Collaboration, Languages and Big Data", Anne Sophie Roessler, Deployment Strategist at Dataiku
YouTube Link: https://www.youtube.com/watch?v=9_pBIWOw3y0
Watch more from Data Natives 2015
Visit the conference website to learn more: www.datanatives.io
Subscribe to Data Natives on YouTube!
Stay Connected to Dataconomy Media by Email: Subscribe to our weekly newsletter to never miss out! (http://goo.gl/JX2GWw)
Follow Dataconomy Media:
https://plus.google.com/+Dataconomy1/videos
https://www.facebook.com/DataconomyMedia
https://twitter.com/DataconomyMedia
Software Craftsmanship @ Ntnu
The document discusses software craftsmanship and test-driven development (TDD). It notes that software craftsmanship is about raising the bar, taking pride in work, discipline, continuous learning, and deliberate practice. TDD's goal is to write clean code that works, following the Red-Green-Refactor mantra of writing a failing test, making it pass quickly, and refactoring code. The document promotes writing clean code because it is less expensive to maintain and leads to better programmers and productivity.
Taming scary production code that nobody wants to touch
This document discusses strategies for working with legacy code that lacks tests, which is considered risky to change. It recommends using core refactorings to safely introduce tests and characterization tests to describe and protect existing behavior without changing it. Peeling away dependencies and slicing code into testable units also helps reduce risk when modifying untested code. The goal is to make legacy code less scary and easier to change over time by adding tests and refactoring carefully.
Software testing Basic
Nghi Nguyen will present on software testing, including an overview of the software testing life cycle, levels and types of testing, characteristics of a great tester, and how to deal with developers. The presentation will cover requirements analysis, test planning, test case development, test execution, and test closure. It will discuss functional and non-functional testing and characteristics like being honest, open, and using a bug tracker when working with developers.
What would Jesus Developer do?
This document discusses applying developer best practices to digital analytics work. It recommends:
1) Using local development with Node.js, build tools, and IDEs to avoid copy-pasting code and work offline.
2) Implementing version control like Git for change history, issue tracking, and teamwork.
3) Writing modular, reusable code through organization conventions and build tools to localize issues.
4) Taking an API-based approach can create a single codebase for multiple properties with continuous integration and auto-generated documentation.
Introduction to unit testing
This document introduces unit testing and its benefits. It discusses different types of testing, including manual testing and unit testing. Unit testing provides quick feedback, confidence to refactor code, and knowledge that code works before QA testing. The document recommends using xUnit frameworks for unit testing in .NET and promotes test-driven development as a way to achieve great test coverage and improved code design. It concludes with inviting questions.
DevOps for Engineers
The main goal of this session is to answer what DevOps is, why it started, and how it will help you. It sheds some light on DevOps in action.
This session was part of Talents Arena's virtual tech job fair 2020.
Unwritten Manual for Pair Programming
This document discusses pair programming and provides guidance on how to effectively implement it. It begins by explaining the purpose of pair programming is to produce high quality software. It then discusses various pairing techniques like ping-pong pairing and mob programming. The document also identifies benefits like higher quality code and faster defect removal, as well as challenges like being tiring. Finally, it provides tips for making pairing work well such as starting with a defined task, switching roles frequently, and not forcing people who strongly dislike pairing.
Use The Source Join The Force by Mark Steve Samson | DevCon Summit 2015 #GoO...
This document provides guidance on contributing to open source software projects. It discusses reasons to contribute such as sharing knowledge, career opportunities, learning, and scratching personal itches. The document also provides tips on finding projects to contribute to, such as contributing to projects you already use or following notable developers. Finally, it outlines various ways to contribute, including contributing code, submitting bug reports and feature requests, improving documentation, providing support, and donating money. The overall message is that open source development benefits both individual developers and society by promoting collaboration and advancing technology.
Getting to production
This document discusses lessons learned about getting software to production. It introduces Mike, a student of deploying software easily, and covers configuration management, the roles of developers and operations staff, and why communication between the two is important. Typical project lifecycles are discussed along with common problems that arise when developers don't consider operational needs or when operations rejects changes too often. The document promotes establishing a simple, repeatable release process and provides reading recommendations on the topic.
What's hot (20)
Встреча Quality built in @Spotify от Андрея Дзыни : как стать лучшим тестиров...
Встреча Quality built in @Spotify от Андрея Дзыни : как стать лучшим тестиров...
16 Favorite Behavioral Interview Questions for Technical Roles
16 Favorite Behavioral Interview Questions for Technical Roles
[XPday.vn] Legacy code workshop (at) [XP Day Vietnam 2015]
[XPday.vn] Legacy code workshop (at) [XP Day Vietnam 2015]
Collaboration, Languages and Big Data, Anne Sophie Roessler, Deployment Strat...
Collaboration, Languages and Big Data, Anne Sophie Roessler, Deployment Strat...
Taming scary production code that nobody wants to touch
Taming scary production code that nobody wants to touch
Use The Source Join The Force by Mark Steve Samson | DevCon Summit 2015 #GoO...
Use The Source Join The Force by Mark Steve Samson | DevCon Summit 2015 #GoO...
Similar to What do software engineers do
Agile Development: Key to smart software development
The document discusses key aspects of adopting an agile development workflow including having daily stand up meetings to discuss progress, taking an iterative development approach with working software delivered each sprint, and conducting retrospectives at the end of each sprint to improve. Adopting agile practices helps ensure working software is delivered frequently for stakeholder feedback, allows skills and the product to evolve together, and prevents waste through continuous testing.
Software engineer.pdf
A software engineer designs and creates computer systems and applications to solve real-world problems. Their responsibilities include designing and maintaining software systems, evaluating and testing new programs, optimizing software, writing and testing code, and consulting with security specialists. A chief architect provides the best work environment and allows teams to work integrated using technologies. As chief architect, they understand software programs and technology to develop solutions like LANs, WANs, and intranets for a company, while assisting employees with technology use and information.
Software Development Simplified - A Beginner's Guide.pdf
Software development isn't a haphazard process. It adheres to a methodical process called the Software Development Life Cycle. The SDLC is a roadmap that outlines the various stages a software project goes through, starting from conception to include deployment and maintenance.
whatiscodingslideshare-180406204414.pptx
Coding involves writing instructions in programming languages that computers can understand and execute. Programming languages make it easier for humans to write code by using words and structure instead of binary numbers. There are many popular coding languages like JavaScript, Python, and Java that are each suited for different purposes like web development, mobile apps, or scientific applications.
Code learning
Remember your first glance at a screenful of computer code? It probably felt like reading another language. Some words may have looked familiar, such as “print” and “input,” but they were surrounded by symbols and numbers that looked completely new.
https://codelearning4.wordpress.com/
What is Coding
Coding is new literacy and you shouldn't miss the chance to learn to code. Not only you but your children should learn to code. Learn more about coding in a fun and easy way with RoboGarden.
RoboGarden is an easy to understand, hands-on educational app where students take part in active learning. Fully equipped to teach coding literacy from scratch, RoboGarden reduces the need for a tech-savvy teacher.
For More info Please visit: www.robogarden.ca
The Role of Testing in DevOps
The document discusses the role of testing in DevOps. It emphasizes that testing should happen at all stages of development from unit tests to acceptance tests to load and performance tests. Modern testing approaches advocate for automating tests and avoiding manual repetition through techniques like fractal testing. The goal is to shift testing left and catch bugs earlier to improve code quality and allow developers to focus on writing new code instead of fixing old bugs.
Quick Intro to Clean Coding
This document provides an introduction to clean coding principles including identifying bad code through code smells, writing tests, and refactoring code. It outlines good practices for writing transparent, reasonable, and usable code and emphasizes writing tests as a safety belt and leaving the codebase in better condition. The document presents object-oriented design patterns, principles, knowledge of languages and libraries, code smells, testing, and code reviews/refactoring as tools for writing clean code. It links to an example of refactoring code in a step-by-step manner and emphasizes writing tests as the starting point and keeping them as the grammar for the system.
Pr.SE2.361101659.pptx
The document discusses the history and definition of software engineering. It began in the 1940s and was formally recognized as an engineering discipline in the 1960s. Software engineering aims to address issues with low-quality software projects by applying engineering principles to the design, development, testing and maintenance of software. The key difference between a software engineer and developer is that engineers work collaboratively on large-scale problems, while developers work more independently on apps and programs. Software engineers are proficient in programming, computer science fundamentals, design, algorithms, testing and debugging software.
Software Engineer Task and Responsibilities Lode Palle.pptx
A software engineer designs and creates computer systems and apps to address real-world issues. Also called software developers, they develop software for computers as well as apps. If you are an analytical thinker who loves solving problems and creating digital products that are easier to use, you might find a job as a software engineer rewarding. Software engineers make software for apps and computers. This is for you if you are an analytical thinker who loves solving problems and creating digital products.
Best 5 Swift IDEs and Code Editors for Your Next iOS Project.pdf
"Unlock your iOS project's potential with the best Swift IDEs and code editors at your fingertips! 📱✨ Elevate your coding experience, boost productivity, and watch your ideas come to life. 🚀 Which one will become your new favorite?
Best Practices For Writing Super Readable Code
The document provides best practices for writing readable code, including commenting code, consistent indentation and naming schemes, avoiding duplication through the DRY principle, and limiting deep nesting. It also recommends organizing files and folders logically, using both object-oriented and procedural programming appropriately, learning from open source code, and refactoring code to improve readability without changing functionality.
BDD presentation
The document discusses best practices for writing software that matters through techniques like behavior-driven development (BDD). It compares test-driven development (TDD) to BDD, noting that BDD shifts the focus from verification to specification by describing desired behaviors. The document also provides examples of how to structure user stories and define scenarios using a given-when-then format to plan development around customer needs.
AI in Code Generation - March User Group
Join our March user group meeting where Peter Caitens takes us through AI tools we can use to enhance our developer skills.
2024.04 - AI in Code Generation - April User Group Meeting
Explore the slides for the April Brisbane Developers User Group as Peter explores your options for generating Apex code for Salesforce.
Next-gen IDE v2 - OpenSlava 2013-10-11
Slides for my talk at OpenSlava conference 2013-10-11.
Abstract: Integrated Development Environments are at the neuralgic centre of developer activities. For many of us it’s unconceivable to work in complex developments leveraging multiple heterogeneous tools for design, build and test activities without the IDE connecting them all.
IDEs are powerful tools, capable of handling many types of tasks. In many cases, IDEs are perceived as a commodity but this is a naïve approach that ignores the many brilliant features that IDEs can be used for: debugging, code generation, test automation, version control, quality assurance, task & issue management, etc.
During this talk, participants will get an overview of what IDEs mean today, for the newbie, the enterprise and the hard-core developer, will get introduced to key IDE features that every one of us should be using, and will participate on an open discussion about what next-generation IDEs should look like.
Types Of Coding Languages: A Complete Guide To Master Programming
Are you confused about types of coding languages? In this article, we have discussed everything about different types of programming languages in detail.
Coding Introductory Lesson Upper Elementary
The document provides an overview of a coding lesson plan that includes:
1) Reviewing what is already known about computers and coding through examples.
2) Learning about coding and programming concepts such as programming languages.
3) Hands-on coding activities using a block-based visual programming language on code.org to write code for games like Angry Birds.
Learning to code in 2020
This document provides guidance for high school and college students on learning to code. It discusses the benefits of coding skills, different types of coding careers, and what coding and software development entail. It then covers considerations for choosing a first programming language, including options for learning functional programming first or starting with Python. The document predicts that Rust will be in high demand in the coming years for developing embedded systems and web applications due to its safety and growing adoption. It recommends students learn foundational concepts in a beginner-friendly language before potentially specializing in Rust.
WeActuallyBuildStuff - Extreme Programming Live
The document summarizes an "Extreme Programming" talk given by Johannes Brodwall. The talk introduces concepts like test-driven development (TDD), pair programming, and refactoring. A demonstration of pair programming on a coding kata is shown. The key points emphasized are that practicing TDD in small iterative steps, pairing with others, and continuously refactoring code can help programmers improve quality and think in a more deliberate, mindful way about their work. The overall message is that becoming a better programmer requires freeing one's mind and practicing programming as an art.
Similar to What do software engineers do (20)
Agile Development: Key to smart software development
Agile Development: Key to smart software development
Software Development Simplified - A Beginner's Guide.pdf
Software Development Simplified - A Beginner's Guide.pdf
Software Engineer Task and Responsibilities Lode Palle.pptx
Software Engineer Task and Responsibilities Lode Palle.pptx
Best 5 Swift IDEs and Code Editors for Your Next iOS Project.pdf
Best 5 Swift IDEs and Code Editors for Your Next iOS Project.pdf
2024.04 - AI in Code Generation - April User Group Meeting
2024.04 - AI in Code Generation - April User Group Meeting
Types Of Coding Languages: A Complete Guide To Master Programming
Types Of Coding Languages: A Complete Guide To Master Programming
More from Thamara Hessel
Liderar e ser liderado(a) - o que você precisa saber sobre liderança técnica
Existem muitos estilos e metodologias de liderança, além de técnicas de gestão e etc. Será que existe uma ideal para você como líder? Será que você como liderado(a) pode contribuir de alguma forma com a estratégia adotada?
Liderar tem tudo a ver com influenciar e impulsionar pessoas e ideias. Como podemos fazer isto na área da tecnologia quando os prazos são apertados e tudo está em constante mudança?
Nesta apresentação vamos abordar alguns pontos-chave dos desafios e limitações enfrentados no dia a dia como o nível de conhecimento técnico, análise de perfil técnico e comportamental de equipes, responsabilidades vs cultura da empresa, liderança técnica vs gestão de pessoas, autodesenvolvimento, engajamento e motivação e discutir alguns mitos e verdades.
Arquitetura e qualidade de codigo
https://log.pt/pt/blog/2018/07/14/change-log-domain-driven-design-2/
Custos indiretos no desenvolvimento de software – Arquitetura e qualidade de código - Jul/2018
Composer - tricks and tips
O documento descreve o Composer, uma ferramenta de gerenciamento de dependências para PHP. Ele explica como o Composer instala pacotes e gerencia suas dependências usando um arquivo composer.json e composer.lock para garantir que as versões corretas dos pacotes sejam usadas. Também resume os operadores que podem ser usados para especificar faixas de versão aceitáveis de pacotes, como til (~), caret (^), e asterisco (*).
Git style best practices - OLX
This document provides best practices for Git commit messages, rebasing, and merging. It recommends:
1. Structuring commit messages with a 50-character subject line separated from the body by a blank line, using imperative mood and capitalization for the subject.
2. Rebasing frequently to maintain a clean log and squashing commits into one before merging.
3. Using merge commits intentionally to mark releases rather than directly merging feature branches, and rebasing feature branches onto the target branch instead.
Code review Effective - kwan
The document discusses effective code reviews. It explains that code reviews are a formal assessment of code changes to check for issues. It outlines 5 stages reviewers may go through from being disillusioned to satisfied. Effective code reviews involve understanding why, when, and what is being reviewed. Reviewers should follow principles like egoless programming and accepting mistakes to provide constructive feedback and learn collaboratively.
Object calisthenics
The document discusses the concept of "Object Calisthenics", which are 9 rules for improving code readability and quality through practices like reducing indentation levels, using early returns, wrapping primitives in classes, and avoiding getters/setters. It provides examples of refactoring code according to these rules, such as extracting methods to reduce indentation, returning early from functions, and replacing getter/setter usage with method calls. References for further reading on Object Calisthenics are also included.
Git - Saia do Básico!
O documento fornece uma introdução sobre o sistema de controle de versão Git. Explica que Git permite controle de versão distribuído e possui diversas ferramentas. Também destaca os principais conceitos como descentralização, estados do código, fluxo de commits e comandos básicos.
Qualidade de código
O documento discute qualidade de código e como alcançá-la através de boas práticas de programação como uso de padrões, frameworks e código limpo, além de testes de unidade e integração. A qualidade também depende de aspectos técnicos como escolha da tecnologia adequada e custos associados a débitos técnicos. Embora a qualidade do software não esteja diretamente ligada à qualidade do código, boas práticas de programação auxiliam no desenvolvimento de software de qualidade.
Refactoring sem complicação!
O documento discute refatoração de código. Apresenta alguns pontos sobre o que não é considerado refatoração, como otimização e correção de bugs. Também aborda motivação para refatoração como código difícil de entender e backlog de bugs crescente. Por fim, exemplifica algumas ferramentas para análise e refatoração de código como PHPMD, PHPUnit e PHPCS.
More from Thamara Hessel (9)
Liderar e ser liderado(a) - o que você precisa saber sobre liderança técnica
Liderar e ser liderado(a) - o que você precisa saber sobre liderança técnica
Recently uploaded
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdf
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
A Comprehensive Guide to DeFi Development Services in 2024
DeFi represents a paradigm shift in the financial industry. Instead of relying on traditional, centralized institutions like banks, DeFi leverages blockchain technology to create a decentralized network of financial services. This means that financial transactions can occur directly between parties, without intermediaries, using smart contracts on platforms like Ethereum.
In 2024, we are witnessing an explosion of new DeFi projects and protocols, each pushing the boundaries of what’s possible in finance.
In summary, DeFi in 2024 is not just a trend; it’s a revolution that democratizes finance, enhances security and transparency, and fosters continuous innovation. As we proceed through this presentation, we'll explore the various components and services of DeFi in detail, shedding light on how they are transforming the financial landscape.
At Intelisync, we specialize in providing comprehensive DeFi development services tailored to meet the unique needs of our clients. From smart contract development to dApp creation and security audits, we ensure that your DeFi project is built with innovation, security, and scalability in mind. Trust Intelisync to guide you through the intricate landscape of decentralized finance and unlock the full potential of blockchain technology.
Ready to take your DeFi project to the next level? Partner with Intelisync for expert DeFi development services today!
HCL Notes and Domino License Cost Reduction in the World of DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on automated letter generation for Bonterra Impact Management using Google Workspace or Microsoft 365.
Interested in deploying letter generation automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Main news related to the CCS TSI 2023 (2023/1695)
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
Introduction of Cybersecurity with OSS at Code Europe 2024
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
Azure API Management to expose backend services securely
How to use Azure API Management to expose backend service securely
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...
Skybuffer AI, built on the robust SAP Business Technology Platform (SAP BTP), is the latest and most advanced version of our AI development, reaffirming our commitment to delivering top-tier AI solutions. Skybuffer AI harnesses all the innovative capabilities of the SAP BTP in the AI domain, from Conversational AI to cutting-edge Generative AI and Retrieval-Augmented Generation (RAG). It also helps SAP customers safeguard their investments into SAP Conversational AI and ensure a seamless, one-click transition to SAP Business AI.
With Skybuffer AI, various AI models can be integrated into a single communication channel such as Microsoft Teams. This integration empowers business users with insights drawn from SAP backend systems, enterprise documents, and the expansive knowledge of Generative AI. And the best part of it is that it is all managed through our intuitive no-code Action Server interface, requiring no extensive coding knowledge and making the advanced AI accessible to more users.
Fueling AI with Great Data with Airbyte Webinar
This talk will focus on how to collect data from a variety of sources, leveraging this data for RAG and other GenAI use cases, and finally charting your course to productionalization.
AWS Cloud Cost Optimization Presentation.pptx
This presentation provides valuable insights into effective cost-saving techniques on AWS. Learn how to optimize your AWS resources by rightsizing, increasing elasticity, picking the right storage class, and choosing the best pricing model. Additionally, discover essential governance mechanisms to ensure continuous cost efficiency. Whether you are new to AWS or an experienced user, this presentation provides clear and practical tips to help you reduce your cloud costs and get the most out of your budget.
Artificial Intelligence for XMLDevelopment
In the rapidly evolving landscape of technologies, XML continues to play a vital role in structuring, storing, and transporting data across diverse systems. The recent advancements in artificial intelligence (AI) present new methodologies for enhancing XML development workflows, introducing efficiency, automation, and intelligent capabilities. This presentation will outline the scope and perspective of utilizing AI in XML development. The potential benefits and the possible pitfalls will be highlighted, providing a balanced view of the subject.
We will explore the capabilities of AI in understanding XML markup languages and autonomously creating structured XML content. Additionally, we will examine the capacity of AI to enrich plain text with appropriate XML markup. Practical examples and methodological guidelines will be provided to elucidate how AI can be effectively prompted to interpret and generate accurate XML markup.
Further emphasis will be placed on the role of AI in developing XSLT, or schemas such as XSD and Schematron. We will address the techniques and strategies adopted to create prompts for generating code, explaining code, or refactoring the code, and the results achieved.
The discussion will extend to how AI can be used to transform XML content. In particular, the focus will be on the use of AI XPath extension functions in XSLT, Schematron, Schematron Quick Fixes, or for XML content refactoring.
The presentation aims to deliver a comprehensive overview of AI usage in XML development, providing attendees with the necessary knowledge to make informed decisions. Whether you’re at the early stages of adopting AI or considering integrating it in advanced XML development, this presentation will cover all levels of expertise.
By highlighting the potential advantages and challenges of integrating AI with XML development tools and languages, the presentation seeks to inspire thoughtful conversation around the future of XML development. We’ll not only delve into the technical aspects of AI-powered XML development but also discuss practical implications and possible future directions.
Trusted Execution Environment for Decentralized Process Mining
Presentation of the paper "Trusted Execution Environment for Decentralized Process Mining" given during the CAiSE 2024 Conference in Cyprus on June 7, 2024.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on integration of Salesforce with Bonterra Impact Management.
Interested in deploying an integration with Salesforce for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Programming Foundation Models with DSPy - Meetup Slides
Prompting language models is hard, while programming language models is easy. In this talk, I will discuss the state-of-the-art framework DSPy for programming foundation models with its powerful optimizers and runtime constraint system.
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
Recently uploaded (20)
Driving Business Innovation: Latest Generative AI Advancements & Success Story
Driving Business Innovation: Latest Generative AI Advancements & Success Story
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdf
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdf
Deep Dive: Getting Funded with Jason Jason Lemkin Founder & CEO @ SaaStr
Deep Dive: Getting Funded with Jason Jason Lemkin Founder & CEO @ SaaStr
A Comprehensive Guide to DeFi Development Services in 2024
A Comprehensive Guide to DeFi Development Services in 2024
HCL Notes and Domino License Cost Reduction in the World of DLAU
HCL Notes and Domino License Cost Reduction in the World of DLAU
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...
Introduction of Cybersecurity with OSS at Code Europe 2024
Introduction of Cybersecurity with OSS at Code Europe 2024
Azure API Management to expose backend services securely
Azure API Management to expose backend services securely
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Trusted Execution Environment for Decentralized Process Mining
Trusted Execution Environment for Decentralized Process Mining
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
Programming Foundation Models with DSPy - Meetup Slides
Programming Foundation Models with DSPy - Meetup Slides
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slack
What do software engineers do
- 1. THAMARA HESSEL I’m a coder I’m a coder
- 3. What do software engineers do? What do software engineers do? Will you hack me? ● Design software for the end user ● Develop applications for WEB, iOS, Android, Windows, Linux, and more ● Conduct requirements analysis ● Fix software and release updates regularly
- 4. Can a software engineer be a hacker? The answer is YES, but NOT everyone. Why not?
- 5. What are the different types of Software Engineer Roles? ● Front-End Engineer ● Back-End Engineer ● Full Stack Engineer ● Software Engineer in Test (QA Engineer) ● DevOps Engineer ● Security Engineer
- 6. What does a software engineer do all day? ● Read a lot ● Research by solution ● Write codes (programming) ● Talk with others
- 7. What does a code look like?