I often found myself with a lack of motivation when it comes to working on a project. But all that changed after I showed GoPlantUML to the great people at Reddit. This post is about how an open-source project can spark a new passion for work and how I am enjoying every minute of it.
GoPlantUML is open-source software that I wrote as a training exercise. I stumbled by accident with the ast library in Golang, and I discovered that I could quickly parse Golang code. Immediately, I realized I could use it to create a diagram of my projects using PlantUML, and thus GoPlantUML was born.
This project is progressing in a way I didn’t believe it would. I did it for myself and posted a link on Reddit, and then I received lots of excellent feedback. But what’s most interesting so far about open-source projects is something that happens that really makes them worthwhile. I find that it is easier to have people suggest new features than to come up with them myself. And as I continue to work on it, and receive more feedback, I see my child growing into something bigger.
All in all, I am quite glad this idea was found useful. And people can benefit from it. I guess that’s the joy of an open-source project, planting a seed and see it grow into maturity by the help and suggestions of others.
I can’t wait to see more people involved. It is nice to see others interested in PlantUML, since I often found myself isolated in that end. Moreover, bringing that tool to more people and at the same time having fun coding is more that I can ask for right now.
Happy coding, and come join us in the joy of open-source development.
Google used to publish Apps almost instantly, no quality review whatsoever, as result, the Google Play Store was full of garbage. Crappy Apps, malicious Apps and overall useless Apps were rampant. Several scandals and privacy breaches after, Google said, no more… “We will review the Apps and ensure some quality across the board”, (turns out that, although criticized, Apple was right, all the time).
Submissions for mobile apps for iOS are subject to approval by Apple’s App Review team, as outlined in the SDK agreement, for basic reliability testing and other analysis, before being published on the App Store.
Applications may still be distributed ad hoc if they are rejected, by the author manually submitting a request to Apple to license the application to individual iPhones, although Apple may withdraw the ability for authors to do this at a later date.
The terms Stack and Heap get thrown around a lot in the programming world. But what does it means? What is the difference between them and why should we care?
To start, I would like to make a clarification on a possible misconception. Heap is referred here as a memory allocation technique, not as a data structure. Furthermore, when we speak about Heap as opposed to Stack, we do not mean two types of memory, what we mean is two ways of allocating memory.
When your code compiles (or run if interpreted), the compiler needs to consider how to allocate your variable definitions in memory. To understand this process, let’s first examine the pros and cons of each type of allocation.
If you agree that nothing paints a better picture of your software project like a well maintained UML class diagram, then this post is for you.
I have been fascinated with Golang because of the versatility of the language. I wanted to take advantage of the Golang parser and a great software called PlantUML (http://plantuml.com/) to create a program that will translate my Golang code into a neat class diagram.
where Swift is overtaking Objective-C rapidly and the momentum is clear. In the
Android world, presently, the language option is not that clear.
Yes, Kotlin is
there, new, coming forward, garden-fresh, 21-century ready but it isn’t ultimately
taking off, not as expected.
Kotlin was first
introduced by JetBrains in 2011, which is the creator of IntelliJ IDEA,
PyCharm, and many other top IDEs. It got its name from ‘Kotlin Island’ in St.
Petersburg, Russia. Made to strike Java.
That said, the
dominance of Java is still immense, the number of libraries, APIs, code
generally speaking is humongous. Not to mention the readability of it, the many
algorithms and things done or thought already in Java, yeah… Simple as it
sounds, it’s hard to break a solid present for a “uncertain” bright future.