First Post!

Author: codegax

content/about.es.md

@@ -5,4 +5,22 @@ date: "2024-04-09"
 aliases: ["about-us"]
 ---
 
-Hola
+[Anubis2](https://github.com/Junyi-99/hugo-theme-anubis2) is another simple minimalist theme for Hugo blog engine.
+
+Written in Go, Hugo is an open source static site generator available under the [Apache License 2.0.](https://github.com/gohugoio/hugo/blob/master/LICENSE) Hugo supports TOML, YAML and JSON data file types, Markdown and HTML content files and uses shortcodes to add rich content. Other notable features are taxonomies, multilingual mode, image processing, custom output formats, HTML/CSS/JS minification and support for Sass SCSS workflows.
+
+Hugo makes use of a variety of open source projects including:
+
+- <https://github.com/yuin/goldmark>
+- <https://github.com/alecthomas/chroma>
+- <https://github.com/muesli/smartcrop>
+- <https://github.com/spf13/cobra>
+- <https://github.com/spf13/viper>
+
+Hugo is ideal for blogs, corporate websites, creative portfolios, online magazines, single page applications or even a website with thousands of pages.
+
+Hugo is for people who want to hand code their own website without worrying about setting up complicated runtimes, dependencies and databases.
+
+Websites built with Hugo are extremely fast, secure and can be deployed anywhere including, AWS, GitHub Pages, Heroku, Netlify and any other hosting provider.
+
+Learn more and contribute on [GitHub](https://github.com/gohugoio).

content/posts/inner-source.md

@@ -0,0 +1,67 @@
+---
+title: "Inner Source is NOT a lie!"
+description: "Inner source needs to be implemented correctly to be successful."
+date: "2024-10-02"
+draft: true
+hidden: false
+tags: [inner-source, collaboration, enterprise]
+---
+
+## A lie?
+
+Regardless of what you might have heard on the internet (_possibly from a tech influencer with a mustache who dislikes ReactJS_), inner source is real and it's a fantastic way to foster collaboration and innovation within your organization, much like open source does in the wider community.
+
+## Why the Skepticism?
+
+While "hate" might be too strong a word, there are certainly many who are skeptical about the benefits of inner source. The main issue is that many people use it as a justification for their choice of tech stack. Critics argue that inner source is not worth the effort because they believe no one will contribute to their projects. In an organization, everyone has their own tasks and priorities, and they may be reluctant to spend time on something that doesn't directly benefit their immediate goals.
+
+## The Real Benefits of Inner Source
+
+But here’s the thing: the reality is often quite different. Inner source can bring about some amazing benefits—if you know where to apply it. Have you ever considered which areas in your organization could truly benefit from this approach?
+
+While it's true that everyone has their own tasks and priorities, inner source can help align these with the organization's overall goals.
+
+This is particularly evident in companies with development teams divided into different departments, especially when the main product is not software.
+
+In these cases, inner source can help align the various departments, allowing the development team to operate as a single unit instead of each department creating its own solution to the same problem.
+
+### Hypothetical Scenario
+
+Imagine you have a company with multiple locations around the world, not only each with its own development team but with teams separated by departments. All locations have to predict shortages on their products and they all have to create a solution to predict these shortages:
+
+- Location A: More developers; creates 3 solutions in Angular + C#.
+- Location B: Decent team; develops a solution in React + Python while focused on other projects.
+- Location C: One developer; builds a solution in Vue + NodeJS.
+- Location D: No developers; creates a solution in Excel.
+
+Corporate already had an outdated solution that wasn’t working as expected. Now, whenever someone wants to improve the prediction of shortages, they must choose between five existing solutions and discuss with other locations to determine if a new solution is better.
+
+User resistance is high because they have to learn a new system each time a new solution is created, while their local solution is tailored to their specific needs.
+
+This scenario is common in companies that lack a strong software development culture. You might think such situations are unrealistic, or perhaps you feel like I’m describing your own workplace.
+
+Having a closed perspective that assumes all companies are the same can lead to generalized opinions. In this case, inner source can help align different departments, enabling the development team to work as a single unit rather than having each department create its own solution to the same problem.
+
+### Hypothetical Solution
+
+Corporate comes to the conclusion that all plants should use the same solution. They create a repository with the base solution, something that has at least all the current features already have and the different locations can contribute to the solution. The solution is created in a language that all locations are familiar with and the solution is created in a way that can be extended by the different locations. The code source is open and anyone can detect if something is wrong or understand how the solution works.
+
+This not only helps to align the different locations but also helps to create a culture of collaboration between the different locations. The different locations can now share their knowledge and create a solution that is better than the one they had before. Now it also creates a standard on language and quality of code that is expected in the company.
+
+## Implementing Inner Source
+
+The first thing is to identify the areas that need inner source the most. This could be a project that is struggling to meet its goals, a team that is having trouble collaborating, or a department that is not aligned with the organization's overall goals.
+
+Then you need to foster a culture of collaboration. Get rid of the ego thinking your solution is better than any other team solution. You need to create a culture where everyone feels comfortable sharing their ideas and working together to achieve a common goal.
+
+Create a structure that allows everyone to contribute. This could be a centralized repository where everyone can submit their code, or a system that allows for code reviews and feedback.
+
+Finally, recognize and reward contributions. This could be as simple as giving credit to the person who contributed the most, or as complex as creating a system of rewards and incentives for those who contribute the most.
+
+## Conclusion
+
+Inner source isn’t just a buzzword; it’s a transformative approach that can align teams and enhance collaboration.
+
+So, the next time you hear someone dismissing inner source, remember that with the right implementation and circumstances, it can be a game-changer for your organization.
+
+Take a moment to evaluate your organization’s collaboration practices. What steps can you take today to start leveraging the power of inner source?

content/posts/reinventing-the-wheel.md

@@ -3,5 +3,5 @@ title: "Why do we reinvent the wheel?"
 date: "2024-10-02"
 draft: true
 hidden: false
-tags: [learning]
+tags: []
 ---

content/posts/unhealthy-competition.md

@@ -0,0 +1,7 @@
+---
+title: "Unhealthy Competition"
+date: "2024-10-06"
+draft: true
+hidden: false
+tags: []
+---

hugo.toml

@@ -22,7 +22,7 @@ readNextPosts = 2
 copyCodeButton = true
 rssAsSocialIcon = true
 locale = "en-us"
-toc = true
+toc = false
 
 
 social = [