<h1>What's that ?</h1>
Based on the Georgios Ntais' Paper <a href="https://people.dsv.su.se/~hercules/papers/Ntais_greek_stemmer_thesis_final.pdf">Development of a Stemmer for the Greek Language</a>, I developed an opensource implementation of a Greek stemmer library written in Go. Inspiration for this project came from this GitHub repo: <a href="https://github.com/skroutz/greek_stemmer/">skroutz/greek_stemmer</a>. 
The Greek stemmer is developed as a computational linguistics tool that applies a set of rules and algorithms to transform inflected Greek words into their base or root form. 
This process, known as stemming, allows for improved analysis and comparison of Greek texts by reducing words to their essential forms. 
Possible application include Natural language processing tasks (text analysis, information retrieval, and machine translation), Search Engine optimizations (e.g. a search for "running" could also return results for "run.") etc.
<hr>
<h1>Example usage:</h1>
<div><pre><code>package main 

import (
 "fmt"
 "github.com/petersid2022/greek_stemmer"
)

func main(){
 x := greek_stemmer.GreekStemmer("ΑΠΑΓΩΓΗ")
 fmt.Println(x)
}
</code></pre></div>
<blockquote>
<a href="https://github.com/petersid2022/greek_stemmer">GitHub repo</a>
</blockquote>

Greek Stemmer library written in Go

<h1>Give me Good Enough, not Perfect.</h1>
Often, we're told that the best solution to a problem is usually the easiest one, or at least the one that first comes to mind when we're grappling with an issue. 
Knowing this, it's astonishing to me, how many times I've pushed myself to find the most elegant and beautiful solution, whether it's a technical challenge or something else entirely, since for almost all of the problems that I had to face, that was my primary objective. 
My primary objective was never to find a solution but better yet to find The Solution™ —the one that would be so elegant, so simple and yet so brilliant, that it could easily clinch the First Prize for the Annual Best Solution award™.
You might know it as the First Prize for the Annual Most Time-Wasting Technique To Convince Yourself That You're Actually Being Productive (better known as A.M.T.W.T.T.C.Y.T.Y.A.B.P™).
I myself know it all too well.
Fortunately for me, I'm not alone in this constant pursuit of the perfect solution. In fact, it's a mindset deeply ingrained in the fabric of our culture and society.
<blockquote>
We've all been unwittingly shaped by a world that often prioritizes the appearance of perfection over practicality.
</blockquote>
From the sleek designs of our gadgets to the flawless presentations we witness daily, we've been conditioned to admire and seek out excellence in all its forms. We've been indoctrinated to believe that the best solution should resemble a masterpiece, an ingenious creation worthy of accolades. 
And so, we relentlessly chase that elusive "Eureka" moment, convinced that it will bring us closer to our ideal of perfection. 
In our relentless pursuit of perfection, we've embarked on a journey shared by many in the engineering world. It's a journey driven by the desire to create elegant, brilliant solutions, ones that could stand proudly on the podium of the "Annual Best Solution" awards. 
In this shared pursuit of perfection, we often encounter a paradox. While the drive for elegance fuels innovation and elevates our skills, it can also lead to unforeseen consequences. We face the looming specter of project delays, the risk of over-engineering, and the ever-present pressure of deadlines.
<blockquote>
Recognizing that this pursuit is a collective endeavor in the software development world is the first step toward finding a balanced approach. It's acknowledging that the allure of perfection can sometimes blind us to the practical realities of software development.
</blockquote>
This is when "Good Enough" is more than desirable. It's Perfect.