Skip to main content

Mermaid for easy schemas

· 2 min read
Julian
DevOps and Quality Assurance Engineer

Schemas configured as code

As the saying goes, an image is worth a thousand words...
Whenever I tried to create schema before, I always had trouble keeping it up-to-date and had to drop it :(
But no longer thanks to Mermaid !

What is Mermaid ?

Mermaid is a language to create schmas.
No long are you stuck editing PNGs !

You can access the online tool here. And the project's GitHub here.

What's even better, mmd (mermaid markdown) is supported in GitHub Readme !

it's unfortunatly not supported by Docusaurus :(

Example

Mermaid example

And here is the associated code, that you can copy paste and easily edit!

---
config:
layout: elk
theme: mc
look: classic
---
classDiagram
direction LR
namespace HylozoaCompany2077 {
class Employee {
+int employeeId
+String position
+double salary
+work(hours: int) : void
+requestLeave(days: int) : bool
}

class Report {
+String title
+Date generatedOn
+String content
+export(format: String) : bool
}

class Rulian {
+String specialty
+customMethod() : void
}

class Person:::someclass {
lol name
+int age
+String address
+greet() : void
+updateAddress(newAddress: String) : void
}

}

Person --> Employee
Employee o.. "entrypoint" Report : draft
Person <-- Rulian

classDef someclass fill:#f9f,stroke:#333,stroke-width:4px;

Building and Engaging a Technical Community

· One min read
Julian
DevOps and Quality Assurance Engineer

We designed our project as an open and collaborative platform.


📜 License

Chosen license: [MIT / GPL / Apache]

Why:

  • ...
  • ...

📢 Contribution Calls

Actions taken:

  • Created issues
  • Posted on forums / Discord
  • Presented the project

🤝 Contributions Received

  • Pull requests: [...]
  • Feedback: [...]
  • Bug reports: [...]

Impact:

  • Code improvements
  • New ideas

📚 Contributor Documentation

Files:

  • README.md
  • CONTRIBUTING.md

Includes:

  • Setup instructions
  • Contribution guidelines
  • Coding standards

🏆 Recognition

  • Contributors list
  • Mentions
  • Acknowledgments

📦 Deliverables

  • Public repository
  • Issues / PR history
  • Community interactions

❌ What is not enough

  • Public repo without docs
  • No interaction
  • Ignoring feedback

🧠 Conclusion

Community involvement makes the project stronger and more sustainable.

Measuring and Optimizing Technical Performance

· One min read
Julian
DevOps and Quality Assurance Engineer

We track:

  • Response time
  • CPU / memory usage
  • Latency

🧪 Testing

Types:

  • Stress testing
  • Load testing
  • Resilience testing

Tools:

  • [k6 / JMeter / custom scripts]

📊 Results

VersionResponse TimeCPUMemory
Before.........
After.........

🔍 Analysis

Identified issues:

  • Bottlenecks
  • Slow queries
  • Memory inefficiencies

⚙️ Optimizations

  • Added caching
  • Optimized queries
  • Refactored code

⚖️ Trade-offs

  • Performance vs complexity
  • Cost vs benefit

📈 Impact

  • % improvement
  • Stability gains
  • Scalability improvements

📦 Deliverables

  • Logs
  • Graphs
  • Test scripts
  • Monitoring dashboards

❌ What is not enough

  • No metrics
  • Guess-based optimization
  • No documentation

🧠 Conclusion

Measure → analyze → optimize = controlled performance.

Structuring and Securing the Technical Architecture

· One min read
Julian
DevOps and Quality Assurance Engineer

Our architecture consists of:

  • Frontend: [...]
  • Backend: [...]
  • Database: [...]
  • Deployment: [...]

📊 Diagram


🧠 Technical Choices

Why we chose:

  • Framework: [...]
  • Database: [...]
  • Code structure: [...]

👉 Every choice is justified.


📚 Documentation

README includes:

  • Installation
  • Commands
  • Environment variables
  • Project structure

Advanced docs:

  • Architecture diagrams
  • Use cases
  • Technical roadmap

🛡️ Quality & Security

  • Linting: ESLint / Pylint

  • Tests:

    • Unit tests
    • Validation tests
  • Security:

    • Authentication
    • Logging
    • Error handling

⚙️ Reliability

  • CI/CD: [...]
  • Monitoring: [...]
  • Error handling strategy

📦 Deliverables

  • Complete README
  • Diagrams
  • Test results
  • Deployment scripts

❌ What is not enough

  • Missing README
  • Monolithic code
  • No tests
  • Unjustified choices

🧠 Conclusion

A clear architecture makes the project scalable, maintainable, and professional.

Evaluating and Integrating New Technologies

· One min read
Julian
DevOps and Quality Assurance Engineer

In this post, we describe our technology watch process and how we evaluated and integrated new solutions into our project.


🧠 Active Technology Watch

  • Sources:

    • Technical blogs
    • Official documentation
    • GitHub / newsletters / forums
  • Technologies explored:

    • [Tech 1]
    • [Tech 2]
    • [Tech 3]

👉 Goal: identify relevant solutions, not just trending ones.


⚖️ Analysis & Comparison

TechnologyProsConsDecision
X.........
Y.........

📊 Benchmarks:

  • Performance
  • Scalability
  • Maintainability

🧪 Experiments (POC)

  • POC 1: [description + repo]
  • POC 2: [description]

Results:

  • ✔️ What worked
  • ❌ Limitations

🔧 Integration

  • Selected technology: [name]

  • Why:

    • ...
    • ...
  • Impact:

    • Performance
    • Developer experience
    • Maintainability

🌍 Community & Sharing

  • Discussions: [Discord / forums]
  • Contributions: [issues, PRs]

📦 Deliverables

  • Research notes
  • Benchmarks
  • POCs
  • Updated documentation

❌ What is not enough

  • Following trends blindly
  • No testing
  • No documentation

🧠 Conclusion

This process led to an informed technical decision and measurable improvements.

Blog Template

· One min read

Here is a template to follow

What this is about

Lorum ipseum, ...

What impacts does it have ?

Lorum ipseum, ...

TLDR

Copy paste that template and focus on teaching your stuff

Image

Docusaurus Plushie