Implementing the application exactly like the client specified, because they won't listen.

assignment: use winAPI to create a "virus" that put itself in autorun and does nothing.

me, a curious student: does the assignment and adds a heap corruption code just as a joke.

after sending the assignment to the teacher I realized that I have sent the real virus.

result: teacher comes next lesson without a computer and stares at me silently and viciously.

we'll see what happens next
any idea on what's going on in his head?

The New Bug Fixing Architecture.

The evolution of software architecture

Dev: what do I call this file ?
Me: just name it something meaningful so other dev's know what it is

Two days pass

Me: time to do code review .. oh look a new file ..

Git comment : new file for sax parsing , architecture gave the ok.

File name : SomethingMeaningful.java

Life of Programmer

CTO: I heard about this great architecture of microservices. What is it exactly?
Me: it's building many servers with one responsbility each.
CTO: That sound good. But let keep it simple and build only one big microservice.
Me: 😲
(True story from a comapny a worked for)

Don't let it be tetris

Bad architecture causes more problems than bad code.

45 minutes into a technical presentation called "Architecture Meets Design", I realized the guy built houses.

Where I work, this is something that happens daily because manager (non-programming MBA) want everything now without proper design and architecture.

Me: Oh I see were using a non-standard architecture on this app. I like this bit but what is this doing? never seen it before.

Him: Ah we use that to abstract the navigation layer.

Me: oh ok, interesting idea, but that means we need an extra file per screen + 1 per module. We also can't use this inbuilt control, which I really like, and we've to write a tonne of code to avoid that.

Him: Yeah we wanted to take a new approach to fix X, this is what we came up with. Were not 100% happy with it. Do you have any ideas?

**
Queue really long, multi-day architecture discussion. Lots of interesting points, neither side being precious or childish in anyway. Was honestly fantastic.
**

Me: So after researching your last email a bit, I think I found a happy middle ground. If we turn X into a singleton, we can store the state its generating inside itself. We can go back to using the in-built navigation control and have the data being fetched like Y. If you want to keep your dependency injection stuff, we can copy the Angular services approach and inject the singletons instead of all of these things. That means we can delete the entire layer Z.

Even with the app only having 25% of the screens, we could delete like 30+ files, and still have the architecture, at a high level, identical and textbook MVVM.

Him: singleton? no I don't like those, best off keeping it the way it is.

... are you fucking kidding me? You've reinvented probably 3 wheels, doubled the code in the app and forced us to take ownership of something the system handles ... but a singleton is a bad idea? ... based off no concrete evidence or facts, but a personal opinion.

... your face is a bad idea

Two unit test suites. No integration testing.

I: "Do you have the right version for your architecture?"
He: "What"
I: "Did you download the 64 bit or the 32 bit version?"
He: "I'm not sure but I think it was sth. between 40 and 50!"

wrote shitload of clean architecture beautiful code and compiled successfully on the first try without crashes or errors

The process of piecing it all together in a nutshell.

To all the design pattern nazis..

Don't you ever tell me that something is impossible because it violates some design pattern! Those design principles are there to make your life easier, not something you have to obey by law.
Don't get me wrong, you should where ever possible respect those best practices, because it keeps your software maintainable.
But your software should foremost solve real world problems and real world problems can be far more complex than any design pattern could address. So there are cases where you can consciously decide to disregard a best practice in order to provide value to the world.

Thanks for reading if you got this far.

Business logic in the fricking database.

1000+ line SQL stored procedures.

What the actual fuck?! 👿

Pizza oriented architecture -> unikernels

A brilliant architecture without a product is nothing but a joke!

This codebase reminds me of a large, rotting, barely-alive dromedary. Parts of it function quite well, but large swaths of it are necrotic, foul-smelling, and even rotted away. Were it healthy, it would still exude a terrible stench, and its temperament would easily match: If you managed to get near enough, it would spit and try to bite you.

Swaths of code are commented out -- entire classes simply don't exist anymore, and the ghosts of several-year-old methods still linger. Despite this, large and deprecated (yet uncommented) sections of the application depend on those undefined classes/methods. Navigating the codebase is akin to walking through a minefield: if you reference the wrong method on the wrong object... fatal exception. And being very new to this project, I have no idea what's live and what isn't.

The naming scheme doesn't help, either: it's impossible to know what's still functional without asking because nothing's marked. Instead, I've been working backwards from multiple points to try to find code paths between objects/events. I'm rarely successful.

Not only can I not tell what's live code and what's interactive death, the code itself is messy and awful. Don't get me wrong: it's solid. There's virtually no way to break it. But trying to understand it ... I feel like I'm looking at a huge, sprawling MC Escher landscape through a microscope. (No exaggeration: a magnifying glass would show a larger view that included paradoxes / dubious structures, and these are not readily apparent to me.)

It's also rife with bad practices. Terrible naming choices consisting of arbitrarily-placed acronyms, bad word choices, and simply inconsistent naming (hash vs hsh vs hs vs h). The indentation is a mix of spaces and tabs. There's magic numbers galore, and variable re-use -- not just local scope, but public methods on objects as well. I've also seen countless assignments within conditionals, and these are apparently intentional! The reasoning: to ensure the code only runs with non-falsey values. While that would indeed work, an early return/next is much clearer, and reduces indentation. It's just. reading through this makes me cringe or literally throw my hands up in frustration and exasperation.

Honestly though, I know why the code is so terrible, and I understand:

The architect/sole dev was new to coding -- I have 5-7 times his current experience -- and the project scope expanded significantly and extremely quickly, and also broke all of its foundation rules. Non-developers also dictated architecture, creating further mess. It's the stuff of nightmares. Looking at what he was able to accomplish, though, I'm impressed. Horrified at the details, but impressed with the whole.

This project is the epitome of "I wrote it quickly and just made it work."

Fortunately, he and I both agree that a rewrite is in order. but at 76k lines (without styling or configuration), it's quite the undertaking.

------

Amusing: after running the codebase through `wc`, it apparently sums to half the word count of "War and Peace"

Haha keeping the tradition alive.

Legends -> I: Interviewer

I: what is mvc architecture

Me: model.. view.. controller... and blah blah

I: mvc is not an architecture.. its a design pattern.. architecture is blah blah

I: srry U r rejected.. god bless you

Me: 😥😢

after 1hr

Me: googled 'Is mvc a design pattern or architectural pattern'

Google: shows stack overflow link

Stackoverflow: mvc is architectural pattern blah blah... accepted answer

Me: hopeless about my future

GOD BLESS THE INTERNET and SOFTWARE DEVELOPERS

Lead: "We write SOLID code"
Me: *opens a controller file*
Controller: "I'm 8000 lines long and hell yeah I'll access the database and file system directly!"

This.
It didn't have to be a logical architecture!

Interviewer : So what frameworks and library you usually use?
Me : i use volley for networking, gson for parsing, livedata/architecture components for architecture and observability , room for database and java for app development

I : ok so make this sample app using retrofit for networking, moshi for parsing, mvrx for architecture , rx for observability , sqldelight for db, dagger2 and kotlin for app dev. You have 8 hours

Me :(wtf?) But i never used those libs or language!
I : we just want to check how easily you adapt to different surroundings.

Me : -_-

Honestly i don't know of it was a great experience or a bad one . I was stressed the whole time but was able to adapt to almost all of those libraries and frameworks.
At the end i got selected but decided not to go for those ppl. That was just a lucrative opening of a venus fly trap, they would have stressed the hell out of me

An application based on a single MySQL stored procedure that contained all the application business logic inside of it (plus a poor webapp that simply called it). The stored procedure had 97 (yes, NINETY SEVEN) parameters... and about half of them were boolean flag used for enabling/disabling another parameter. I think that Uncle Bob could follow you holding an AK-47 if he saw that. The saddest part is that the shit was written by a guy having a PhD in computer science, and he knew that was bad, but the boss asked him to do it in that way. The guy left the company before I joined it and I had to maintain that crap. Guys, the first time I saw it I thought that should be a joke. Code generated by decompilers was easier to read, maybe even Brainfuck. I tried complaining with the boss but she said that the system was wonderful and very efficient. This was one of the reasons I moved to another company after some months.

Confuzzled if I should go the low level way and learn more about software architecture and foundation or go the artificial intelligence machine learning way because I want to get out of this infinite loop of only developing apps!

Noob: Your pc? 32 bit or 64?
Me : x64
Noob: Haha, mine's x86 😎
Me: 😓

for me it's 70% design and architecture,
10% Googling, 10% stackoverflow, 10% college courses.

i'm seriously over mobile devs not understanding what backend architecture looks like.

the "we don't need a backend, we just need an API." statement drives me up the fucking walls. stop it, you should know better.

sincerely -
your friendly neighborhood web developer.

The newest *DD development trend: Panic Driven Development.

When your hexagonal domain driven serverless microservice architecture explodes in production and you don't know which one of the 50k components is failing.

I resigned today 😍
No more dealing with shit architecture and experimental beta technologies being used in production which went down constantly 😎
Back to good ol' product development! 🤩
One month notice period to go

Our Service Oriented Architecture team is writing very next-level things, such as JSON services that pass data like this:

<JSON>
<Data>
...
</Data>
</JSON>

Developing a Haskell project, indenting everything with 3 spaces. Develop to over a million lines of code. Use Darcs as a repository. Run the code on AIX powerpc architecture. Suffering from special snowflake syndrome.

normal architecture...

The IT head of my Client's company : You need to explain me what exactly you are doing in the backend and how the IOT devices are connected to the server. And the security protocol too.

Me : But it's already there in the design documents.

IT Head : I know, but I need more details as I need to give a presentation.

Me : (That's the point! You want me to be your teacher!) Okay. I will try.

IT Head : You have to.

Me : (Fuck you) Well, there are four separate servers - cache, db, socket and web. Each of the servers can be configured in a distributed way. You can put some load balancers and connect multiple servers of the same type to a particular load balancer. The database and cache servers need to replicated. The socket and http servers will subscribe to the cache server's updates. The IOT devices will be connected to the socket server via SSL and will publish the updates to a particular topic. The socket server will update the cache server and the http servers which are subscribed to that channel will receive the update notification. Then http server will forward the data to the web portals via web socket. The websockets will also work on SSL to provide security. The cache server also updates the database after a fixed interval.

This is how it works.

IT Head : Can you please give the presentation?

Me : (Fuck you asshole! Now die thinking about this architecture) Nope. I am really busy.

Working code is not a clean code

So, I was gonna rant about how it can be difficult to design event-based Microservices.

I was gonna say some shit about gateways APIs and some other stuff about data aggregation and keeping things idempotent.

I was going to do all this but then as I was stretching out the old ranting fingers I decided to draw a diagram to maybe go along with the rant.

Now I’m not here to really rant about all that Jazz...

I’m here to give you all a first class opportunity to tear apart my architecture!

A few things to note:

Using a gateway API (Kong) to separate the mobile from the desktop.

This traffic is directed through to an in intermediate API. This way the same microservices can provide different data, and even functionality for each device.

Most Microservices currently built in golang.

All services are event based, and all data is built on-the-fly by events generated and handled by each Microservices.

RabbitMQ used as a message broker.

And finally, it is hosted in Google Cloud Platform.

The currently hosted form is built with Microservices but this will be the update version of things.

So, feel free to rip it apart or add anything you think should change.

Also, feel free to tell me to fuck right off if that’s your cup of tea as well.

Peace ✌🏼

Uncle Bob and Martin Fowler. Their books (“Clean code”, “Clean architecture”, “Refactoring”) and Twitter posts have changed the way I look at software development.

➡️You Are Not A Software Developer⬅️

When I became a developer, I thought that my job is to write software. When my customer had a problem, I was ready to write software that solves that problem. I was taught to write software.

But what customers need is not software. They need a solution to their problem. Your job is to find the most cost-effective solution, what software often is not.

According to the universal law of software development, more code leads to more bugs:

e = mc²

Or

errors = (more code)²

The number of bugs grows with the amount of code. You have to prioritize, reproduce and fix bugs.

The more code you write, the more your team and the team after it has to maintain. Even if you split the system into micro services, the complexity remains.

Writing well-tested, clean code takes a lot of time. When you’re writing code, other important work is idle. The work that prevents your company from becoming rich.

A for-profit company wants to make money and reduce expenses. Then the company hires you to solve problems that prevent it from becoming rich. Confused by your job title, you take their money and turn it into expensive software.

But business has nothing to do about software. Even software business is not about software. Business is about making money.

Your job is to understand how the company is making money, help make more money and reduce expenses. Once you know that, you will become the most valuable asset in the company.

Stop viewing yourself as a software developer. You are a money maker.

Think about how to save and make money for your customers.

Find the most annoying problem and fix it:

▶️Is adding a new feature too costly? Solve the problem manually.
▶️Is testing slow? Become a tester.
▶️Is hiring not going well? Speak at a meetup and advertise your company.
▶️Is your team not productive enough? Bring them coffee.

Your job title doesn’t matter. Ego doesn’t matter either.

Titles and roles are distracting us from what matters to our customers – money.💸

You are a money maker. Thinking as a money maker can help choose the next skill for development. For example:

Serverless: pay only for resources you consume, spend less time on capacity planning = 💰

Machine Learning: get rid of manual decision-making = 💰

TDD: shorter feedback cycle, fewer bugs = 💰

Soft Skills: inspire teammates, so they are more productive and happy = 💰

If you don’t know what to learn next — answer a simple question:

What skills can help my company make more money and reduce expenses?

Very unlikely it’s another web framework written in JavaScript.

Article by Eduards Sizovs
Sizovs.net

RISC-V is the future !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Fuck x86 or ARM.
RISC-V is the real real architecture.

DATA COMMUNICATION BETWEEN SERVER AND AN APP..

1. Write all data into files,
2. Make the files as zip,
3. Send the zip to server,
4. Server will unzip the zip file,
5. Read all the data line by line from the files and update the data.

** TRUST ME, THIS IS A PRODUCTION APP I HAVE SEEN FROM A CLIENT **

!rant
TIL: The IKEA effect is a cognitive bias, that lets you think, stuff build by yourself is more worth then stuff build by others

Does that sound familiar to anyone?

It always gives me a smile when my boss (ceo, no technician) calls me and says "let's do some software architecture together!". He has no idea what this means, but he likes the term. Sometimes, this call just means "let's have a beer together"

Now blame the architecture!

Bob Martin. His books Clean Code and the Clean Coder, and all his talks on architecture, SOLID and TDD. I could listen to him talk for days, and he taught me everything i know about writing clean code.

As a Java developer I didn't write a line of code at work for about 2 months. Been so busy with meetings, doc, governance, architecture decisions, running after people for approvals,... I really miss coding.

So, they've decided that they "don't need architecture."

To all the developers fighting for a good architecture, and the designers fighting for good UX. You guys are the real heroes fighting the eternal fight.
Here's to you!

“No it’s better this way, it’s an enterprise grade architecture design” - someone who was no idea how to build an app

When your boss tells you that you are going to develop and maintain an old legacy architecture

I have my Computer System Architecture exam in 10 hours.

I'll fail. For sure.

I had a meeting today with some high level technical executives from IBM and I showed them our architecture and they were impressed and said it was rare that they saw start-ups with such great architecture. As a dev with no formal education and one year experience this makes me so proud and also very proud of my team

Titled my presentation "High Availability Setup", after a moment of thought, I changed it to "High Availability Architecture".

There, I will sound a bit more intelligent when I read it out loud on Monday. 😎😂

I didn't really find the usefulness of Docker until I used Docker Compose. Deploying our architecture with a simple 'docker-compose up' FeelsGoodMan.jpg

My fucking campus building.
Really. Built a new one in 2017, we started to study there since Oct 2017 til now and lemme tell something: it's shit. My classroom's paint cracked 2 months in. My classroom lacks a projector which is standard for every classroom to have one back in the old campus building. But nooope. No projector for 1.25 years, at least by now compensated by a 50" TV which whoever the fuck installed the thing took the *only* stock HDMI cable. Shitty floor tiling (think r/mildlyinfuriating but worse), shitty toilet that would break down every 2 weeks and "over the top" gymnasium with air ventilation so bad it feels like Hitler's fucking oven every time we got in.

Being a grown-up dev is replacing "that’s the stupidest idea I’ve ever heard" with "Ok boss, I’ll consider those architecture suggestions".

architecture...

They laugh at me when I'm still using windows batch scripts.

I ask them how to check the cpu architecture within a batch, to check whether administrator rights are present and if not, enabling the default windows admin and create another admin over the default admin. I ask them how they'd set a registry key within a batch...

They don't have any idea...

After designing the new server architecture for our software and the security to go with it, the boss decides we should ask our provider’s solutions architects to see if it is okay, they came back and said it all looks good apart from one part which my manager did and I always said was bad practice.

How to get investors wet:

“My latest project utilizes the microservices architecture and is a mobile first, artificially intelligent blockchain making use of quantum computing, serverless architecture and uses coding and algorithms with big data. also devOps, continuous integration, IoT, Cybersecurity and Virtual Reality”

Doesn’t even need to make sense

When my clients expect me to finish the software architecture ASAP and accuse me of procrastinating : Do i really need to explain how thinking works? 😤

Running code in a JVM ... which is a virtual machine...
Inside a VM that runs Linux...
Inside a host OS that runs on native...which runs on a CISC processor... that internally runs a RISC architecture... so that makes the CISC a VM...
The RISC architecture I am pretty sure runs on Elf Magic... I am fairly certain Turing was an Elf working for Santa...
So I am really running my code on VM Elf Magic

Quote of the day
"Writing code without thinking of its architecture is useless in the same way as dreaming about your desires without a plan of achieving them."

That literally hit me hard

I can’t respect an architect that does not code or never has. Keep making pretty pictures...

The worst part of being a dev is when you realize you have a major design flaw in your architecture at 4:50 PM on a Friday. Goodbye weekend, hello intense thought.

Microservices.
(by @kelseyhightower on Twitter)

Installing my company's microsystems architecture to run locally is a pita because it is 60 GB of docker containers. With my 256 GB Macbook, that's a scaling problem for the years to come.

"The C programming language was specifically designed to abuse the von-Neumann architecture"
- Some guy on StackOverflow

The worst architecture I've seen is WordPress.
How can you be so drunk to design such a filthy mess?
In some way PHP might be to blame. Its API is a fucking mess as well and may have stirred WP developers in this puke around so they couldn't come up with a better CMS architecture.
Don't get me wrong. I do love PHP. But only in it's OO form with namespaces and type hints and composer dependencies.

I've seen enough of PHP functional programming and it still haunts me.

The design process.

Call me old fashioned - but clean-code/clean-architecture/SOLID is not as important as simplicity and coherence.

I JUST NEED FUNCTION THAT DOES STUFF! But noooooo better overly design EVERYTHING!

Very few general embedded systems books exist, most are specific to chip, or architecture. Very few cover overall ideas, and concepts that are common across ALL embedded systems regardless of architecture and things you must keep in mind while designing software for them.

I think this a a good book. As a primer for deep diving into embedded systems design philosophy

"The Fire Department has traditionally considered architecture a priority only when it’s burning down. " - Justin Davidson

When your PM is drawing all over your nice architecture diagram..

“3mb JavaScript over dialup” - Before I knew how to write proper JavaScript I once wrote a calendar scheduling app in php that generated all of the functions for all of the buttons for all of the times for all of the days currently being displayed... the result was a 3mb JavaScript file... in the days of dial up modems...

When your product owner tells you to forget about architecture and unit testing, "just push it out"...

Reviewing code for applications after not working on it for six months.

Client: so what is the first step to adding our new feature.

Me: I really think we need to redo the entire architecture from the ground up. It won't work any differently than it does now, but the code will be cleaner.

Client:😓

Me:😅

Boss: so let's get AWS in to ask their advise on the new architecture, but let's not bother involving the systems architect who actually knows what is going on.

Overheard: "I'll need to get in touch with my Infrastructure Architecture Innovation Team"

😂🤣😅😂🤣😅

Why not just call them team buzzwords. Omg.

Bricked my android device the other day. Took a whole day to get it working again.

Why do phones have to make it all so complicated. It should be like PCs, being able to install anything as long as it matches the CPU architecture.

What books do you guys recommend?
So far I read:
1. The Clean Architecture
2. Microservices Architecture (50% done, should be done in a week or two max)

I'm thinking of reading next:
Domain Driven Development

What do you think?

That new devlead that just joined and is bad mouthing everything we did and introducing his own state management library he hacked together without understanding our architecture (Clean Architecture) nor what layers are supposed to do and what the sense behind layers is. Also we learned from him that apparently Android deprecated ProGuard, LiveData is deprecated and Lifecycles in Android are broken.

Just a random shout out to @Lyniven for helping me with modular application architecture at past few days

- "what architecture is your project ?"
- "haystack architecture .."

You realize that the ERP software you use at your company is shit when:
- there is no service-side ERP backend handling requests
- the whole permission system is client-side (!)
- every client directly connects to the MSSQL database with a supervisor user (stored in plain text in a local config file)
- the MSSQL database contains tables with:
- typos
- names like "contract" but then also "contracts"
- mixed german and english words
- the multiple-business-unit implementation uses 4 columns named "Layer 1, Layer 2, Layer 3, Layer 4" in EACH table
- you find out that the ERP software is created with a fucking "software creation tool"
- there is no API, so you have to program one yourself to use for services

Yet, they charge us shit ton of money for their broken ass software.

software archi evolution

Ahhhh.. the great feeling of starting a new project at work after the stresses and health deterioration of maintaining old code bases.

I'm curious..

When does programming suck for you, and when is it fun?

Like I hate programming, when I run into an obscure use case that opens up some serious errors with my some, or gasp, all, of my architecture and forces me to rethink everything - especially DB design, ugh.

I love programming when my architecture and DB design create naturally readable code and everything falls into place and I feel like a genius.

I guess, in short.... plan before you code?

And then, plan again.

But don't plan too much.

The love/hate of my programming life summed up right there I think.

How about you?

Went to the O’Reilly conference on architecture last week. Will say there were some good points made (really liked the elephant in architecture and tech debt talks). But wow developers love to circlejerk. If you don’t deploy microservices on the cloud with serverless actions for everything then they’ll talk down to you like what you do isn’t important. Like so many talks memed monoliths were annoying. Like I get we love the new and shiny things but it’s kinda ridiculous.

I want to create something crazy with this architecture, what do you think?

Just got rejected for an internship because of my architecture pattern. Learnt an entirely new framework and deployed an API in a week. Sigh

Edit:
Was at a college level. Not completed my bachelor's yet.

Fuck you, previous lead architect dictator! I spent a year arguing against your rigid nonsense custom built bullshit, and a year and a half after the client finally caught on and got rid of you I just got bitten yet again from one of your retarded over-complicated "solutions" to problems that never existed in the first place.

I wish I could send you an email and tell you about how I have thrown out all the useless shit you created and that we are all clearly better off now, but instead I will just share my frustration on DevRant and hope you read it and know exactly who you are.

I feel sorry for your current client.

When scope creep actually becomes a complete rewrite for a different architecture.

Development time : 1 month
Architecture: 5 days
Writing code: 5 days
Testing: 5 days
Deciding variable/service/entity names: 15 days

So, I have a bit of a question for you guys..

I'm a self taught coder, but I think I lack some elements regarding the architecture side of software development.

Does anyone have some valuable sources to learn about it?

Thanks in advance :)

Architect: I've been using this architecture for 20 years now and this works nice since pascal, that's why we are using it in this J2EE app.

This was the justification that I received after hearing that I shouldn't use exceptions, just make the function return a false and add the error message to a embedded message list and make the caller capture it.

Me: *suggests an architectural input to something that would have taken care of a lot of shit in our project*

Lead Dev: *doesn't completely try to understand what I suggested* I don't know if this would work, it seems a "bit weird"(really?). I think we need to rethink our current architecture. *Moves on to redesign everything from the base up and asks us to adopt so we go on and delete a lot of the existing code and basically rewrite everything*

- 10 days later
Lead Dev: *sees the same old issues with using the new architecture and suggests the same approach that I had suggested earlier, only this time he came up with it and it's a brand new idea*
Me: WTF! *Screams into oblivion*

When you go to an architecture meeting and people's statements are so abstract that they could apply to any product on the face of the earth.

Teammate turned my neat minimal service architecture into dog's breakfast.
Now I don't know which one I hate more. Him or ROS.

At what point do you stop optimizing queries and realize it's a database architecture, scaling problem?

We've been having production issues this week because a lot more users with more demands, and I'm going we need more servers... We can't just have one db, we need to parallelize like Hadoop...

Everyone else is going, how do we optimize queries, indexes, reduce the load...

Finding fragile balance between “we need to create a programming language to solve this task elegantly and efficiently” and “yo dawg here’s some php, go get that shit together”

I just learned the concept of this thing called REST API and now here's GraphQL showing up on me face. Mother fucking web development hell. BRB. KMS

Immediately start coding every feature all at once as fast as possible. After about a week I realize the architecture is so bad I can't continue so I stop, and design the architecture properly so it will scale. Then I delete everything I had and start from scratch. Finally after about another week I lose interest and let it rot in the side project graveyard.

Rinse and repeat.

Has devRant had to scale anything since it got launched or is it still stable enough?

For the love of GOD, if you're an architect or someone in the position where you can make drastic changes to the overarching design of a software system, if you're so keen on enforcing something "cool" just because you've read about it in a blog post/seen it on a youtube video, READ ABOUT IT THOROUGHLY, as in, pick up a fucking book or do actual research. An architect overseas just informed us that a whole legacy PHP application (a fucking monolith with a dysfunctional database, yes, I think someone demented designed it) should be rewritten to a microservice architecture (without a messaging broker, just plain API interaction through HTTP) AND WE'RE KEEPING THE DATABASE WHICH BEGS TO BE PUT DOWN FOR GOOD. So now we're gonna have a clusterfuck of tons of PHP microservices (Q_Q) which interact through plain HTTP APIs (swagger's gonna be put to a test) and all have a single broken database in the center. Talk about a microlithic design. Jesus Christ.

Develop my first mobile app with a restful backend for consumer usage

Learn more about cloud architecture/computing

Finish learning calculus

Learn linear algebra, discrete math, statistics and probability

Maybe start ML this year depending on math progress and time

If there is anything I learned from Robert Martins in The Clean Architecture book is that: Marketing geniuses are fucking useless

I don't understand the code that I wrote yesterday everyday.

Rant to discuss Domain Driven Design (DDD) architecture.

Did anyone implemented on production?
How scalable and easy to use?
Do you recommend it? if yes in which environment? in which business types?

So... Yesterday I ordered a meal and it had whole jalapenos in it. I didn't order jalapeños. I love the taste but I hate toilet visits after. Hence, was putting them aside. But then I got into that new code, jumping around this new project I'll be working on. We were getting intimate. I liked the architecture, I liked it a lot - it was using event sourcing and respected CQRS. Suddenly I realised I ate everything. Including jalapeños. And the only reason I noticed is because I was eating with my hands. And my eye got watery. And I wiped it.

So, yeah. Yesterday for the first time in my life I was pouring milk into my eyes. Does this count as a proper dev rant? I don't know. Fuck the protein interface that can't process simple food orders, though.

All day long meeting with business consultant about company future, software architecture, technical debt, refactoring, resources, projects.

Conclusion from top consultant, ex country manager of a weeeell known tech company:
Who cares about "code" anyway? (disgusted smile)

An application requiring lots of servers to handle the workload is not the problem.

The problem is an application that cannot handle workload no matter how many servers you throw at it.

You told the design team this won't work on a large scale
Design team: Well we designed it, so, fuck you !
You: Does the implementation...
End Product: * Doesn't work *

Design Team: Why isn't it working, suggest a workaround

* Facepalm *
* Dead Inside *
* Give me Death Note plox *

exactly two years back I joined my current company, it is spanish company and I speak only english. each document that was there in the welcome kit was in spanish, including design and architecture documents. also coding guidelines. it was a night mare as comments in the code were also in spanish. it took me three days to come to terms with reality.

I can write pretty much no algorithm
but bubblesort without googling.

I write articles where I teach other developers how to design architecture.

One of our 'Microservices' solutions has > 40 projects in it :(

Last year, we had computers architecture class where we study about the architecture of processors like RISC, CISC, SIMD... The teacher was a nice person but didn't have much knowledge on the field. I read some of Patterson&Hennessey book (computer organisation and design iirc) and learned how to use openmp and mpi, and then in the last lab we were required to optimize matrix multiplication using 4 threads in openmp, the best students optimiseed for 4 times at best, meanwhile I made 16 times optimisation and showed the teacher how fast it was. She was really impressed lol

Designing a framework: design the framework. Have a bunch of drinks. Try use the framework. Sober up and examine how you’ve butchered it.

Adjust the framework.

Trying to re-arrange my web api to fit this "Clean Architecture" form of rather unprescribed structure.

Its the kind of architecture where if you were to ask a guru "ok so where do services live in this layout", you would get in response "Let me ask, does this service mingle with your infrastructure level devices, does it fulfill key functionality on your domain models? If so, place in some directory within infrastructure that will be arbitrarily named and its interface in some interface directory in core".

No absolute right or wrong answers, never black and white, always 5 other questions to answer your one because everything is so damn contextual.

For anyone working with Clean arch let me ask this. With micro services splitting the boundary line shorter and shorter between functionality, is the robust nature of clean arch even needed anymore ?

It makes sense for splitting large repos into logical pieces that can be plugged in and replaced easily but thats also one of the major take aways with micro-serviced architecture.

My reaction when I meet peopel that still don't use any Architecture/Design Pattern to code.

What is yours?

Why do product managers think their roadmaps/decisions are completely unrelated to our technical decisions? Information/transparency are key themes in the architecture process. In order to accept the risks, you must first understand them.

I coded a simple Java programme when I was a beginner, today I reviewing it. I facepalm myself and thinking "I wish I know about 3 tier Architecture software development earlier" . Now I am looking at a one tier Architecture programme.

Which means UI components, Logic Components and Database components are all in ONE class and one method. Omg. Silly past self...

Q. What did the fat Software Engineer call his stomach?
A. 3-Tier Architecture

Who is using serverless architecture and recommends it?

No seriously, tell me more about how leveraging React-Native for sections of the app and creating these custom architecture patterns is going to revolutionise mobile development. I'm all ears.

Today I was orders to check out one of our applications. Accounting said that the Twilio bill was constantly increasing even if we do not get any new clients. In 10 min I found out what is the problem. All calls are recorded and stored in Twilio, which charges handsomely for such service.
Developers instead of downloading those recording to our data lake, use Twilio as storage, because no coding was involved.
Company lost around 30k dollars this year and around 10k-20k in previous ones, because someone was lazy to spend few days to download mp3 from url.

Writing tokenizer for a new language.

Me: Ok, we'll implement that message tech. But since the clients are servers in that architecture and can't speak IPv6 we've to use a dedicated VPN so the endpoint is able to connect to the servers (clients). Since we have limited network resources we should use VPN cert-encryption and send the actual data plain to save at least some overhead.

Boss: Ok! Let's do it!

Next day.

Boss: Hey! I talked to a guy from that message tech. Their encryption is certified. We should use that instead and get rid of the VPN to save the overhead!

Me: *unable to say a word*

What in "VPN in that architecture is mandatory" is unclear?

Well, I assume we'll kill the architecture then... Fun Time!

When do you know something is being overdesigned or overengineered?

The applications that the other programmer started building are killing me. He's using Clean Architecture and it has like a million different classes and shit. It's not messy or anything, but fuck it's overwhelming.

Just to figure out wtf was happening when getting the currently signed in user's email, I had to go through like 30 folder and files. Maybe more. All files were fairly simple on their own, but the entire flow was mindfucking me. Use cases, schemas, gateways, repositories, entities, models, etc etc

And that's the client facing application, I haven't checked the API yet, though it seems like that one is simpler.

The worrying aspect here is, any time anyone else has to mess with this, they'll also have to deal with this shit. This needs some really good documentation.

I work as a "software architect" in a company where architecture is just a footnote on stuff we have to build on top of a legacy codebase. The most frustrating thing about my job is having to deal with senior developers whose skills consist of things they last updated in 2010. I'm supposed to call these people my peers when they can't even grasp the concept of asynchronous messaging across three services as it gets way too complex. My job as an "architect" is 90% just being a developer and then expected to solve problems related to architecture and development standards with the remaining 10% of my time.

I started at a what is now called a brogrammer shop. While the three owners were probably 50 and older, there was little design outside of the owner's dreams. We busted out programs in the new language C# in three tier architecture with an Access backend. It was fun but when the economy went south I got laid off after about a year.

Has any of you worked with someone claiming he's a "Senior Software Engineer" but he does not know what he's doing? I'm not saying I'm a very good developer myself but I know how to differentiate a good code from a garbage code and architecture. It's really becoming a pain in the ass...

Just use proper variable name and class architecture and header file and viola you don't need documentation.
In the worst case to understand class heirchy use the graphviz of doxygen and you are done.

So this web company i joined had a page load time in minutes. The free text search (inverted index search, based on elasticsearch) queries would return results in 10-45 seconds (should be milliseconds always). The indexes had no schema. And they would crawl data and feed into mssql db, which had a 2 gb/db limit on the free version. So everytime the db hit the limit, a new db was created and the name was incremented by one.

Had a very tough time cleaning up that mess. Plus the architect who had made this architecture was on his way out and unhelpful to the core.

What was worse was that most of the changes i did were very simple changes that should have been done long back. Basic sanity changes.

I need some opinions on Rx and MVVM. Its being done in iOS, but I think its fairly general programming question.

The small team I joined is using Rx (I've never used it before) and I'm trying to learn and catch up to them. Looking at the code, I think there are thousands of lines of over-engineered code that could be done so much simpler. From a non Rx point of view, I think we are following some bad practises, from an Rx point of view the guys are saying this is what Rx needs to be. I'm trying to discuss this with them, but they are shooting me down saying I just don't know enough about Rx. Maybe thats true, maybe I just don't get it, but they aren't exactly explaining it, just telling me i'm wrong and they are right. I need another set of eyes on this to see if it is just me.

One of the main points is that there are many places where network errors shouldn't complete the observable (i.e. can't call onError), I understand this concept. I read a response from the RxSwift maintainers that said the way to handle this was to wrap your response type in a class with a generic type (e.g. Result<T>) that contained a property to denote a success or error and maybe an error message. This way errors (such as incorrect password) won't cause it to complete, everything goes through onNext and users can retry / go again, makes sense.

The guys are saying that this breaks Rx principals and MVVM. Instead we need separate observables for every type of response. So we have viewModels that contain:

- isSuccessObservable
- isErrorObservable
- isLoadingObservable
- isRefreshingObservable
- etc. (some have close to 10 different observables)

To me this is overkill to have so many streams all frequently only ever delivering 1 or none messages. I would have aimed for 1 observable, that returns an object holding properties for each of these things, and sending several messages. Is that not what streams are suppose to do? Then the local code can use filters as part of the subscriptions. The major benefit of having 1 is that it becomes easier to make it generic and abstract away, which brings us to point 2.

Currently, due to each viewModel having different numbers of observables and methods of different names (but effectively doing the same thing) the guys create a new custom protocol (equivalent of a java interface) for each viewModel with its N observables. The viewModel creates local variables of PublishSubject, BehavorSubject, Driver etc. Then it implements the procotol / interface and casts all the local's back as observables. e.g.

protocol CarViewModelType {
isSuccessObservable: Observable<Car>
isErrorObservable: Observable<String>
isLoadingObservable: Observable<Void>
}

class CarViewModel {
isSuccessSubject: PublishSubject<Car>
isErrorSubject: PublishSubject<String>
isLoadingSubject: PublishSubject<Void>

// other stuff
}

extension CarViewModel: CarViewModelType {
isSuccessObservable {
return isSuccessSubject.asObservable()
}
isErrorObservable {
return isSuccessSubject.asObservable()
}
isLoadingObservable {
return isSuccessSubject.asObservable()
}
}

This has to be created by hand, for every viewModel, of which there is one for every screen and there is 40+ screens. This same structure is copy / pasted into every viewModel. As mentioned above I would like to make this all generic. Have a generic protocol for all viewModels to define 1 Observable, 1 local variable of generic type and handle the cast back automatically. The method to trigger all the business logic could also have its name standardised ("load", "fetch", "processData" etc.). Maybe we could also figure out a few other bits too. This would remove a lot of code, as well as making the code more readable (less messy), and make unit testing much easier. While it could never do everything automatically we could test the basic responses of each viewModel and have at least some testing done by default and not have everything be very boilerplate-y and copy / paste nature.

The guys think that subscribing to isSuccess and / or isError is perfect Rx + MVVM. But for some reason subscribing to status.filter(success) or status.filter(!success) is a sin of unimaginable proportions. Also the idea of multiple buttons and events all "reacting" to the same method named e.g. "load", is bad Rx (why if they all need to do the same thing?)

My thoughts on this are:

- To me its indentical in meaning and architecture, one way is just significantly less code.
- Lets say I agree its not textbook, is it not worth bending the rules to reduce code.
- We are already breaking the rules of MVVM to introduce coordinators (which I hate, as they are adding even more unnecessary code), so why is breaking it to reduce code such a no no.

Any thoughts on the above? Am I way off the mark or is this classic Rx?

I remember when I was going, I tried to delete system32 folder in windows because I was sure my pc has 64bit architecture...xD

I have my computer architecture midterm in about 3 hours and I understand almost half of the material. Wish me luck, I'll need it!

Started my first private App project using all the goodies of 2017 android development like TDD, Android architecture components (hence MVVM), kotlin (which I yet have to learn), RxJava2 (if I need it additionally to AAC) and maybe try to set up a CI environment.

Wish me luck guys and girls 😁

How to tackle game AI?

I learned about behaviour trees, listened why they are bad, state machines, why those are bad too, hybrid systems, guidelines, that systems should be modular, that AI needs clearer building blocks...

I think it will all come down to "go to player and shoot" -.-

So I was talking microservices architecture with some lead techs.
And I started asking how did they combine/connect their microservices.

And despite having a lot, they use HTTP as the main transporter.
So the put some API-Gateway, all inside traffic has to go through it, to connect to the final client.

And I said that I do meshing microservices, and we use Nats as man transporter, so our messages go through UDP and not TCP.

And they freaked out. Saying UDP is too low level and not useful...

My question: if you do microservices oriented architecture, and not SOA, do you use HTTP? Did you use it simply because "it works"?

I don't understand the point of giving a 'new' mobile build, 'everyday' to clients

"Today I did minor bug fixes and minor architecture level changes"

Now what, are you going to laser scan the build to see my changes? :|

Day 1 of migrating the entire companies infrastructure to GCE...

Thought It wouldn't be too difficult migrating the db until I found out the 480 triggers and 42 stored procedures are a no go.

I mean I know they right and the db layer should be about storage only - I even remember thinking "This is a bad idea" when I wrote most of them but fuuuck it's going to take weeks to refactor this. :'(

Has anyone else struggled with CS classes that teach very low-level stuff like in Computer Organization and Architecture? I'm in that boat right now.

Hey fellow devRanters,

I'm sure some of you have read about the newest vulnerabilities in Intels Management Engine (ME). I feel like ME and similar "features" are unacceptable backdoors into our systems. Unfortunately Intel and AMD do not offer their customers the option to acquire CPUs that lack these backdoors and make disabling them rather impossible 😒

Thus my question: Do you guys know of any 64-bit "open-source" CPU on the market that is production-ready and suitable for high-traffic web applications? Please note that I don't consider FPGAs to be viable options, since I don't trust Xilinx and Altera either.

Trying to review the architecture of an internal boilerplate... After having explained Atomic design principles, and the "component approach" to my colleague, he still managed to come back to me with:

- plugin/
- module/
- components/ ....

in his architecture... I don't know what to do. I'm depressed. FML. I'm quitting.

Guys help... I need a new chromebook and can't decide on a chromebook pro or chromebook plus... Is having x86 architecture worth the extra $120? :-/

Teach students the importance of clean code/architecture and testing. Even if they dont yet understand the more complex topics such as architecture, they should understand why quality is important and that software is a craft more than a science. You cant just apply principle X and insert design pattern Y and profit++. You actually have to think and constantly improve. AND TEST.
Think I would probably also cover things like build automation and continuous delivery. These are now important things for junior devs to know about going into companies.

Learned ARM assembly in just a day. I guess I proved myself wrong when I thought it's gonna be hard to jump to another architecture.

PS. Originally worked with 16 Bit Windows Assembly. 😂

My universities computers. They have really high end hardware but are bottlenecked by the shoddy network architecture and software being used by the IT admins. 🙄

May be the worst developer decision I have ever made... but I think I want to consider switching the architecture in my video chat app to serverless (like now.sh)

cheaper for me as well.

My colleague sucks in all programming languages known to mankind, and he's one the best programmer I know.
Stop thinking "programming = programming language", languages are nothing ! Programming is about logic, architecture, paradigms, and that's about it.

Programming languages are the front-end of programming.

I had perfect code until the exception handling was on my Todo list... Fuck my beautiful architecture I guess

Oooooohh this shiny new android app architecture seems cool 😍. There goes my sleep again.

So I've a little freelance project, is basically a blog. I've decided to use microservices with angular in the front end and python in the backend.

I've been about 2 weeks copy pasting code in my api because all the modules are pretty simple CRUDs that do the same thing, there is not heavy business logic or anything, just database handling.

I was really tired of copy pasting modules and his test, only changing function names and parameters, today I've this "epifany" about the inheritance and thinked about using it in my service, creating a base class and making all the other classes children of him.

Before the change my project has 220 tests (100% coverage) now I have only 40 tests (the same 100% coverage)

So, the lesson is: don't start throwing code like an idiot and start your project with some good planning

Worst architecture I've seen is Intel's x86 and AMD's x86_64.

Change my mind.

Tired of chasing an elusive architecture and finding good community that helps promote it. Basically:

- Not CRUD
- Not MVC
- More like CQRS; commands and queries represent use cases
- Event Sourced; event log is source of truth, everything else is a cached projection
- Functional Domain Design; not DDD; focus on immutability and simplicity
- Functional in general; less OO
- More focus on domain concepts rather than tech concepts
- Domain can be used through CLI, API, or SDK
- UI is just another client to the API
- Authorization is ABAC, graph-based access control

I'm looking for a fucking unicorn.

"When we think of design, we usually imagine things that are chosen because they are designed. Vases or comic books or architecture…" - Seth Godin

I just bought "Code Complete", "Design Patterns", and "The Pragmatic Programmer". Any advice on reading them?

WHY WOULD YOU PACKAGE BY LAYER NOT BY FEATURE

What do i do?

I worry about problems that don't exists yet. Look for breaches that are not made. And am pissed off at things that are slow but I've never used them.

!rant

I need advice. I want to build new pc and i can get i7-4770k for 100 €, but one thing that turns me down about that is older socket. Should i go for it ? Or should i get something with new architecture ?

Having a meeting to decide, when to have other meetings...
Scrum, scrum of scrums, workstream, planning, pm ,design review, architecture review, Sprint review on and on....on and on on...why can't i simply code:(

Like serverless architecture, in future there would be devless architecture.

The MVP vs MVVM debate is making me have an object oriented crisis.

In software architecture definitely my own architecture in a programming project for uni
In building architecture the recently "modernised" Park Inn hotel in Bratislava 😅

I'm cross-compiling software I create for many years. Ignoring languages targeting some kind of VM, some additional efforts were always needed.

Go (as far as I can see, since 1.5) is doing this right and quite straightforward - select target and architecture, issue build command and you get native executable file. I'm happy ... B)

When your team is at war with the other site's team because their archi approach is "screw architecture and quality"

I'm envious of Backend developers who can just 'see' the problem domain and start creating an architecture. I can't see shit - I just stare blankly at the project and I think: hm, what models do I write?

I know I'm a structured person, but I lack the knowledge and practice. One day I'll be able to do this, but for now I have to keep doing things ad hoc.

I really don't belong in the Backend but unfortunately that's how my career is turning out for now. All I know is I have to get better at this.

If you think good architecture is expensive, try bad architecture. (Brian Foote and Joseph Yoder)

When Windows 10 revives a memory error from running 32 bit apps on 64 bit architecture first logged and patched on Windows Server 2003. It was 13 years ago!

(Sr. Dev) Oh right, you can't do that in the controller.
(Me) I can't do what?
(Sr. Dev) That thing.
(Me) Call another controller from the controller?
(Sr. Dev) Yep.
(Me) Where is supposed to be called?
(Sr. Dev) From the view.
(Me) But what is supposed the controller to be used for?
(Me) What is supposed to do the controller?
(Sr. Dev) The controller pass data to the inner classes. (Controller > Manager > Domain Object > DAO)

I ended calling 3 controllers methods from the view in 4 different views everytime...

Ever have one of those days where you work really hard on something only to be completely defeated by the architecture you're working in. I seriously want to rearchitect this entire damn project. Spaghetti code doesn't even begin to touch it.

From my last rant, I'm now looking for Jobs.

I heard that a few people from here work in startups. Just wondering what your xp with these kind of companies are.

Also looking for some good critical questions that I may be able to ask.

I'm currently all about architecture, frontend and UI/UX

Arcolor is an architecture site to match building to their colors.
This giving the architect a view of the common colors in his favorite buildings

Waiting 3 days for your graphics card to get trough all training data to see if you wasted your life with bad architecture.

So today I got to see one of the most stupid architectural choices I have ever seen.

They have a service-oriented architecture. Mainly Python and Elixir.
A lot of computation goes in the Python services.

And the Elixir services as used to expose RestApi. Basic ones, basically DB proxies.

Not a lot of async, or communication... Just plain CRUD.

Why the fuck do you use Elixir for that?? And now they can't recruit someone... And the CTO doesn't get why it was a stupid choice!!!

And in python, they use async functions with sync DB APIs...

I'm in our biweekly architecture meeting. I feel like Denny Crane in Boston Legal: everything is fuzzy and I have no idea what's going on.

Axing features in your project that you’ve been working on for months just because the architecture was setup wrong really hurts.

Question to all those who have worked with software architecture: What is your approach when implementing architecture and design into actual software?

I find it very hard to translate UML diagrams and architectural requirements into working code and I feel like there is quite a big "gap" between the two. How to you breach that gap and manage to maintain a clean and comprehensive architecture in your project folders?

My manager put "Architecture Diagram" onto my list of tasks. "Do you have a diagram"? came up in our last call.

No, I don't have a diagram like your useless block diagram that shows nothing of what we've done. Instead I have a ton of wiki pages, real documentation, READMEs in each git repo that are detailed and complete, unless you're repos of empty directories, `.keep` files, empty READMEs and blank "TODO" wiki pages!

Can somebody explain to me why developers (especially web) have to micromanage every single thing into it's own f*ing component.

Story time: I have an input form with some tabs. I discovered that the UI Library (Devextreme) has a nice little component that handles forms, (including tabs, groups, etc.). So I make a page, configure tabs, inputs and whatnot.

Now, I already knew that my coworkers can't handle html that is bigger than a page. So instead of putting the configs in the frontend, I made nice files where I store those, to keep them nicely clean and seperated.

Me feeling very good, went off to have a nice lunch break.

I come back read the message from my coworker, asking me to make every tab it's own component and form and load them into a separate Tab-Component, instead of using the built in configuration

......

WHAT?

Like seriously. I have a f*ing library that handles that, why the f*ck do I need to reinvent the wheel here!?

Supposedly it's to make it more maintainable, easier to find bugs, flatten the hierarchy.

Here's a little wake up call you morons: Nesting hundreds of components into each other does *not* help you with that.
It just creates a rabbit-hole of confusing containers that you have to navigate and dissect every time you try to find something.

"Can I fix the bug in the detail Page? Sure I'll tell you tomorrow when I find out which fucking component the bug results from".

Components are there to be *reused*. It's using inheritance for reusing code all over again, but worse.

But maybe I'm just old fashioned, and conservative. Maybe I'm just a really bad software engineer, because nowadays everything seems to result in architectures spreading hundreds of folders, thousands of files with nothing but arbitrary cut-offs with no real benefit, that I don't see the value in.