Software Architecture #softwareengineering
Almir Mustafic’s Post
More Relevant Posts
-
Fresh Graduate Computer Science | B.CompSC | D.CyberSecurity | Cyber Security Specialist | SOC Analyst | SqlMap | Semi Understanding
Software Architecture #Software_Architecture
To view or add a comment, sign in
-
-
Founder of REVSYS | Expert in building, scaling and maintaining complex web applications | Python/Django/React/PostgreSQL on Kubernetes
I usually describe it just like a house/building architect. While building architects get super detailed a software architect is not usually giving out to the millimeter "follow these directions at all costs" designs, but more detailed than a napkin sketch. They aren't measuring and cutting boards, nor nailing them together. They aren't constructing the thing, they're designing it. It's quite possible that after construction has started, mid-stream changes have to be made "turns out the city code says this pipe has to be 8 inches away from the electrical, not the 6 inches on the drawing", but in general, the bathroom is over here, and the fireplace goes on that wall.
How would you describe "software architecture" to a person with 0 experience coding?
To view or add a comment, sign in
-
Software Architecture Basics and Architecture Patterns in Software Engineering (Software Engineering 101)
To view or add a comment, sign in
-
Improve your security and compliance - Helping you to build secure software companies - Contract | Freelance
I came across a post titled "Are Software Engineers Becoming Dumber?" This made me think about how software engineering has evolved over the years. While the use of abstractions, libraries, frameworks, and tools has made development more efficient, it has also made the landscape more complex and difficult to understand. Additionally, the use of generated code and Stack Overflow code without proper vetting can pose security risks. It's important for engineers to be integrated into the company's business, security, and other aspects to orchestrate the development of new products and software.
To view or add a comment, sign in
-
Design patterns are a fundamental part of software engineering, and they can help you write better, more maintainable code.
To view or add a comment, sign in
-
-
Co-Founder of Neat Roots. Mobile app development trainer, Android developer skilled in Kotlin Multiplatform, Java, XML, and Jetpack Compose. YouTuber. Successfully achieved 1M+ downloads on Play Store.
Q- Clean Code Architecture? . . . . 🔹The concept of Clean Code Architecture is inspired by the SOLID principles, Domain-Driven Design (DDD) and other best practices in software development. 🔹Clean Code Architecture is a set of principles and practices that aimed at creating modular, maintainable and scalable Software Systems. 🔹 It emphasizes separating the concerns and organizing code in a way that makes it very easy to understanding, testing and extending. Key Principles: 🌟Separation of concerns: Organizes code into distinct layers with specific responsibilities like promoting maintainability, testability and adaptability. 🌟Dependency rule: Code can be only depend on the inner layers and isolating business logic from external factors and reducing coupling. 🌟Abstraction: Interacts with outer layers interfaces, abstract classes through abstractions and shielding the core business logic from implementation details. for more on this topic please read the document:) #androiddevelopment #androiddev #android #androiddeveloper #androidstudio #androidapp #cleanarchitecture #softwareengineering #softwaredeveloper #mobileappdevelopment
To view or add a comment, sign in
-
In many companies, software architects are often decoupled from classical software engineering tasks. This perspective couldn't be more wrong, as architecture is not solely about designing structures. Here's an idea I truly appreciate, with significant emphasis on the last sentence, that to do their jobs properly, architects must experience the problems they are creating. 💻🏗️ "First of all, a software architect is a programmer; and continues to be a programmer. Never fall for the lie that suggests that software architects pull back from code to focus on higher-level issues. They do not! Software architects are the best programmers, and they continue to take programming tasks, while they also guide the rest of the team toward a design that maximizes productivity. Software architects may not write as much code as other programmers do, but they continue to engage in programming tasks. They do this because they cannot do their jobs properly if they are not experiencing the problems that they are creating for the rest of the programmers." from Clean Architecture, by Robert C. Martin #SoftwareArchitecture #Programming #CleanArchitecture
To view or add a comment, sign in
-
Ever wondered what separates a junior developer from a senior one? It's more than just experience. In this post, we dive deep into the world of software architecture, the secret weapon that elevates devs from code-slingers to strategic thinkers. ️ #softwarearchitecture #developer #careerdevelopment #seniordeveloper #juniordeveloper
Software Architecture, the gap that differentiates between a Junior Dev and a Senior Dev - ZeFer
zefer.blog
To view or add a comment, sign in