How do you deal with, avoid, or accept complexity — differently than you might have earlier in your career?
How do you deal with, avoid, or accept complexity — differently than you might have earlier in your career?
For further actions, you may consider blocking this person and/or reporting abuse
I rarely write in Python, but I follow Python zen:
Before that I felt inadequate for writing very simple code in comparison to sophisticated solutions I've seen around.
Turns out the simpler it is - the better🤦♀️
Thanks for sharing. 👍🏻
And this one got me thinking hard. 🤔
“ Complex is better than complicated.”
Think of it this way, you'd describe the relationship you have with your mother in law as complicated, and the reasons are subtle and different and they are all interrelated. And it really helps if you know all the back story.
However you'd describe the way in which aluminium is mined and purified as a complex process. But it can be broken down into steps, each step does not require knowledge of the step before it.
This metaphore is insanely accurate.
You cant avoid complexity as it is dictated by product requirements.
But as you gain knowledge and experience your start to get better in breaking complex scenarios into smaller chunks that you already either
and thus the problem as a wholeis easier to grasp.
(begin rant)
With web development, it's easy to spend so much time searching for the perfect tool that promises to relieve whatever complexity you might encounter with your project. However, that complexity has to exist somewhere, and any new tool you decide to pick up has the complement of additional mental overhead in learning that tool and relearning that tool when you return to it after a while, which isn't uncommon in large projects.
From being a CS major this past year, I've had to readjust my thinking to accommodate different language types. I had a class in assembly this past semester and it really showed the importance of knowing the extent of a system, but how to manage complexity efficiently in any environment, even at such low levels of the software stack.
The problem with modern Web Development and complexity (at this point I feel like I should make this an entire post lol) is that you have to deal with 3-4 different languages in harmony and modern web development encourages strong interop between them (e.g. css-in-js, TailwindCSS) while also preaching "separation of concerns". This leads to confused and convoluted environments, great disparity between codebases that are difficult to maintain and engineers are terrified to run
npm update, and tools that you find that you have to ask yourself why it even exists since it covers such a specific edge case.Every modern web development tool is trying to solve the same problem and no one is satisfied with settling on a solution to manage complexity. That's why we're now seeing so much of "just use vanilla HTML/JS/CSS, it works great", but then you ignore the reason that ReactJS/Vue/Angular were invented in the first place: to consolidate complexity. Web development is a delicate balancing act that requires sacrifice in actually solving some of your complexity instead of expecting a tool or library to.
I have found that developers often end up creating complicated solutions (complicated code) when the problem is actually not complex at all.
This results in having this complicated thing you have to deal with (technical debt) that is a layer over the top of what is actually a simple(r) problem.
This is why I try to think, "how can I reduce the amount of code and still design the correct solution &/or fix this problem?"
I've become incredibly paranoid about potential complexity.
Earlier I thought it was bad design/coding/development practices.
Now I've realized most complexity can be solved by determine what the problem actually is, rather than dealing with complexity in the solution. IE most problems aren't actually complex. Identifying them correctly can remove large vast quantities of complexity in any solution you create.
There are some issues that are just plain complex, but most aren't.
Seems you discovered the difference between doing the things right and doing the right things youtube.com/watch?v=OqEeIG8aPPk ;)
@lepinekong
Thank you for the gold nugget of a video ;)
There are two levels of complexity I've slowly come to terms with. The first is code complexity which you can handle by analysing cyclomatic, N-Path and CRAP scores.
The second is behavioural and project complexity. This is more difficult to handle as it's more theoretical and there is no definitive answer. To deal with it you need to be flexible, adaptable and humble. I'd also advise learning more about complexity theory.
A good place to start is Melanie Mitchell's book, Complexity: A Guided Tour. goodreads.com/book/show/5597902-co...
I used to think that I can do anything given time. That any complexity can be unravelled if I was just given enough time to sit it out in the corner and think/hack away at the problem. I used to get all excited about the solution and jump at it.
Now, my perspective is more nuanced than that. Some problems maybe beyond reach for my skill level (and experience) no matter how long I hack away at it. Sometimes its as much a "people problem" than a code problem. Overcoming complexity isn't as simple as hacking away at it. It requires us to really think it first and break apart the problem. Consider multiple solutions and what tradeoff it makes against the many facets of the problem.
I can say that I'm no longer as excited in jumping to the solution immediately.
When I was younger, I tended to avoid complexity, or always tried to go on it with some support (either colleague or internet).
But now with some more experience, I'll always deal it the same way with ~3steps :
I recommand having a look at "refactoring guru", the website with the badger mascot, as it explains a lot of it, with detailed examples both theoric and with code.
Some more advices :
Maybe the best advice I can give is that it will never be flawless the first time, and don't try to make 10+ classes for a start.
Most of the time I do a big old "index.php" or "script.js", code on the fly, and when things are finally starting running flawlessly, and your file is 500+ lines : it's a hint that it is time to split your code into multiple folders/files.
Got client stuff ? Create a "Client" classe.
Need to create a new client ? Create "Client->create( )" method
Client needs name and email ? Update your class : name & email properties. "Client->create(name, email)"
And so on.
Once you feel good and confortable about this, to get to the next level go check Unit Testing, and after that TDD > Test Driven Development.
It will help you thinking about your code as input/outputs and stuff, and can really improve code reliability, maintenance, avoid regression, and also make your code really faster.
Sorry for the big block and the approximate english.
Feel free to ask questions if you have some ;)
Have a nice day
I see complexity arise when people try to fit square pegs in round holes, use tools for purposes they were not intended for and for which they are mismatched. I think complexity can be reduced by 'going with the grain' of tools we use rather than against. Have written more thoughts here: dev.to/yawaramin/reducing-system-c...
I've learned to manage it. I do so by using abstractions and "Bounded Contexts" that closely represent the business domain. If a certain abstraction is too complex to maintain, "grok" or reason about, I "encapsulate it" and defer all its complexity to a consumable contract. This often applies to classes, modules, libraries as well as feature teams! I wish I'd had learned this "domain-focused" approach much earlier in my career. It would have made me more effective at maintaining codebases and designing larger systems.
I have personally become more complex as I age, my code less so.
Turning to have Code as documentation has allowed me to not only simplify it, but make methods and steps easier to understand with good naming.
My background was linear and procedural, which means I used to think of a problem as a set of steps that needed to be executed in order. Through the years, I found out that many approaches are better than a linear one.
In fact, one of the most basic ways to split a problem into smaller ones is called decomposition. If I'm solving a problem and getting stuck on some aspect, I can isolate that part and focus on it first.
With age and experience, I switched from a linear thinker to a systematic thinker, which triggers envisioning projects as a couple of interconnected elements that must be split first and then combined to fit an entire system.
I developed a process where I try to understand the problem first, isolate it as small as I can, think on a piece of paper on how to solve the problem outside the tool, then move into code.
I can summarize the process to:
1️⃣ Define the problem by isolating it as small as possible.
2️⃣ Think on paper of a simple solution (non-coding).
3️⃣ Code the solution.
4️⃣ Test the code.
5️⃣ Get feedback from peers and use it to improve the code.
6️⃣ Repeat steps 3-5 until satisfied with the result.
I've always strived for simplicity, as it is beautiful to look at and to work with. And it works.
I find that inexperienced developers often overcomplicate simple things. I've made peace with that as everyone needs to learn sometime. It is frustrating though to look at a project, codebase or architecture that is 10x times more bloated and convoluted than it should be.
Learning and work experience has helped a lot to cope with complexity in various different ways. I'd say though sometimes It's unavoidable but as a rule of thumb If it can be made simple, then simple it is. My latest recipe is something like:
On top of all of this with time I learned that no matter how complex it seems at first It always ends up being doable, managing that initial anxiety is very useful.
Actually it hasn't changed much it just reenforced the theory I had already because of my SystemsThinking background (I've been coached by a close friend of Deming the guy who helped Japan Industry become number I after WWII) youtube.com/watch?v=OqEeIG8aPPk ie Complexity is kind of fractal concept you could unify. In Science it is even quantifiable as degree of freedom which I refer below as "intrinseque complexity".
I've been always attracted to complex Systems originally I almost embrace a career of Astrophysicist but I had to go to Canada too cold for me :) Then I was half professional in Stockmarket (being analyst for pro traders in a big bank) in parallel to Software Enginer - which is kind of amazement because I had created a unique model that is based on a non linear equation which is extremely rare as the huge majority of models are stochastics so I'm one of the rare person who knows some truth about how it really works. And of course also Software which is rather simple compared to the other twos because the intrinseque complexity are augmented by artificial over complications which are partly social organisation, partly technical, partly accidental, partly commercial so it's kind of folkore, people who pretend to be "software architect" for example are almost laughed at compared to architect in traditional sense, Alan Kay himself think the field lacks rigor, but that's I find actually even more attractive as it creates opportunity to improve the field more than in another field. In the future this won't be possible anymore because probably it will be completely industrialised and commoditized by the Cloud Giants.
Complexity can always be increased, but reducing it is not always possible.
In most cases, you'll find ways to reduce complexity by understanding the issue to solve and the underlying system (APIs, formats, protocols, encodings) so you can reduce the complexity of the tasks required by the solution.
So... what do you mean by complexity? Dependencies, tactics vs strategy, technical debt all jump to mind.
In Science as I said there is the concept of degree of freedom. But that is about the object, whereas in Software what is really complex is the process which also involves social organisation like in a big corp which will over-complicate your job rather than facilitate it ;) Defining the right problem is often more complex than finding the solution once you have understood the first.
When I was brand new to programming I was kind of proud of complex systems in a way that is perturbing in hindsight. I am accepting of complexity, but certainly not proud of it.
Complexity is reserved for business logic. Complication is acceptable for technical concerns.
As long as the unit tests are readable, I give up caring about the code readability
Complexity is always accidental.
We need to avoid it all the time.
Forget about code complexity and software complexity. they are a myth
It's...
Complicated.
Now I'm fine with complexity - I try to understand it and try and do complex things,
Earlier I would have freaked out and stayed anything that was the slightest bit complex to me.
Will never forget this from one of the authors here at dev:
Code is simple, people are what's complicated.
Get the reason and workflow from the person takes the time and effort. Then the code is simple to implement.