The “Boring Software” manifesto

As software developers we are tired of the false claims made by evangelists of the latest and greatest technology. We will no longer confront them with their lack of understanding of computer science fundamentals, nor will we defend our lack of knowledge of their hyped and volatile technologies. The state of industry is forcing us to value:

  • Not only working software,
    • but also well-crafted software,
    • built exclusively with popular and proven tools.
  • Not only responding to change,
    • but also steadily adding value,
    • while reducing the dependencies and complexity.
  • Not only individuals and interactions,
    • but also a community of professionals,
    • that share best practices with verifiable claims.
  • Not only customer collaboration,
    • but also productive partnerships,
    • to reduce the scope of the software we build.

That is, in pursuit of “agility and craftsmanship” we have found “boring software” to be indispensable. Continue reading “The “Boring Software” manifesto”

Goodbye DMCA and Github

Microsoft and Apple collaborators are still making premiums through the warehouse. For this reason they have turned off warehouses that do not comply with some DMCA policies. Guys, even when we try to delete the stores, it’s failing. We can not do anything.

It is clear from DMCA that this is a ridiculous policy. It was frustrating for us to let such things happen in Github. That’s why I carry all my stores.

Fucking goodbye to the DC and other policies. 🙂

O Language: Web Site Update

The website of that language has been renewed. We converted the site to a documentation site in order to use it more efficiently. So we will create the documentation directly by hovering over the site. You can search by direct documentation.

For example, if you use the term “file” directly on the site, you can make automatic assignments like “Files”. We made searches and corrections in the post. We have adapted our documentation to the most recent version.


These types of optimizations will be effective both in terms of google and site. While doing such optimizations, we have updated the site design. You can visit to see the updates.


O Language: Exception Management

Exception management is an array that allows you to check whether an error has occurred depending on an object. The content is checked to see if there is an error, or to the end if no error has occurred.

Begin is used to control an object.

begin object{

“Expect” and “recover” are used to debug and print out errors. Automatic “error” identification is done. In this way, we can use this definition as an internal variable.

begin object{
   if (test == "hello"){
     except test "Hello is not usefull. Please use Hi on project."

   recover test{

If no errors are received, “final” is used. If there is no error in this way, the values in “final” are automatically executed.

def test = "hello"
begin object{
   if (test == "hello"){
     except test "Hello is not usefull. Please use Hi on project."

   recover object{

   final object{
      println("Hello is not used. Yay!")

This is how we debug it. Exception detection can be used in this way.

Web site:


O Language: Snap Store Version Released

It has been compiled in all distributions with SnapStore support or “o language” specifically for platforms that support the snap run environment. You can use the snap command to unpack the desired packages via the SnapStore, where you can easily install and install packages. And without depending on platforms and package managers.

Now I will talk a little bit about how to set up a package with snap. First, to take the package over the SnapStore;

sudo snap install "package name"

The package is set up directly. O Language is officially offered as a stable version of the store. For the installation;

sudo snap install olang

You can effortlessly install your system. You can check snap store for package details.