# Vladimir Jovanović Vladimir's personal website This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Firebase Predictions: User Segmentation and Monetization Strategies DevFeed: [Firebase Predictions: User Segmentation and Monetization Strategies]() Original publisher: [Read original article]() Author: Vladimir Jovanović Published: 2020-05-22T09:44:00Z Content type: tutorial Language: en Sources: [Vladimir Jovanović]() Topics: [Firebase](), [Machine learning](), [Users]() Tags: [android](), [firebase](), [firebase-predictions](), [machine-learning](), [programming](), [push-notifications](), [remote-config]() ### AI overview This introduction explains how Firebase Predictions applies machine learning to Firebase Analytics data to segment users by their likelihood of taking specific actions within the next 7 days. It presents retention and monetization strategies using Remote Config, ads, push notifications, and in-app messages. ### Source excerpt Firebase provides a wide variety of tools, something for every developer and something for every problem. But did you know that it has a tool that enables you to see into the future?! ## Mark intentionally empty methods with comments DevFeed: [Mark intentionally empty methods with comments]() Original publisher: [Read original article]() Author: Vladimir Jovanović Published: 2019-03-20T09:44:00Z Content type: opinion Language: en Sources: [Vladimir Jovanović]() Topics: [Code](), [coding]() Tags: [clean-code](), [code](), [programming]() ### AI overview The article argues that empty method implementations can be mistaken for errors. It recommends adding comments to clearly indicate when a method is intentionally empty or unfinished. ### Source excerpt Doing copy/paste of the sample data from one project to another is not an option. ## Sharing Android sample data between projects with Gradle DevFeed: [Sharing Android sample data between projects with Gradle]() Original publisher: [Read original article]() Author: Vladimir Jovanović Published: 2018-03-10T09:44:00Z Content type: tutorial Language: en Sources: [Vladimir Jovanović]() Topics: [Android](), [Gradle](), [Script](), [layout]() Tags: [android](), [android-development](), [android-layout](), [code](), [design](), [gradle](), [layout]() ### AI overview This tutorial explains how to share custom Android sample data across projects by hosting the files and using Gradle scripts to download them into a project folder. ### Source excerpt Doing copy/paste of the sample data from one project to another is not an option. ## Improving Android Layout Previews with Sample Resources and Preview Attributes DevFeed: [Improving Android Layout Previews with Sample Resources and Preview Attributes]() Original publisher: [Read original article]() Author: Vladimir Jovanović Published: 2018-02-18T09:44:00Z Content type: tutorial Language: en Sources: [Vladimir Jovanović]() Topics: [Android](), [layout](), [ui](), [XML](), [coding]() Tags: [android](), [android-development](), [android-layout](), [coding](), [design](), [layout](), [ui](), [xml]() ### AI overview This tutorial explains how Android developers can improve XML layout previews using sample resources and preview attributes. It covers showing representative text and images, previewing repeated items, configuring horizontal orientation, and displaying menu items without adding runtime view state. ### Source excerpt As every Android developer, I also started building my layouts by hard-coding values into them. Later on, I have realised that I should... ## How to Make an Open-Source Project Useful to Developers DevFeed: [How to Make an Open-Source Project Useful to Developers]() Original publisher: [Read original article]() Author: Vladimir Jovanović Published: 2017-11-11T09:44:00Z Content type: opinion Language: en Sources: [Vladimir Jovanović]() Topics: [Open Source](), [Code](), [GitHub](), [Repositories](), [App]() Tags: [code](), [github](), [open-source](), [product](), [programming](), [repositories](), [software-development]() ### AI overview This opinion article argues that publishing code openly is not enough to attract users or contributors. Open-source projects should provide clear value, use readable and maintainable code, present polished documentation and packaging, promote the project, and improve it continuously. ### Source excerpt About two years ago, I started putting pieces of code on my GitHub page. And soon I have noticed that nobody was looking at it. My profile was dead. ## Learning Prolog: A Beginner's Introduction to Logic and Relational Programming DevFeed: [Learning Prolog: A Beginner's Introduction to Logic and Relational Programming]() Original publisher: [Read original article]() Author: Vladimir Jovanović Published: 2017-10-24T09:44:00Z Content type: tutorial Language: en Sources: [Vladimir Jovanović]() Topics: [Programming](), [Programming language](), [Development](), [Mathematics](), [Software]() Tags: [computer-science](), [language](), [math](), [programming](), [programming-language](), [prolog](), [software-development]() ### AI overview A developer revisits Prolog after encountering it at university, explaining its facts, rules, relations, queries, and use in calculating factorial. The article concludes that Prolog is a niche but worthwhile way to explore a different approach to software development. ### Source excerpt During my university days, while I was studying Mathematics and CS, software development was refreshment of applied science in a sea of theoretical math. But then at my 4th semester I got the Prolog. ## Why Descriptive Variable Names Improve Code Readability DevFeed: [Why Descriptive Variable Names Improve Code Readability]() Original publisher: [Read original article]() Author: Vladimir Jovanović Published: 2017-10-17T09:44:00Z Content type: tutorial Language: en Sources: [Vladimir Jovanović]() Topics: [Variable](), [Code](), [Programming](), [Computer science]() Tags: [clean-code](), [code](), [computer-science](), [developer](), [programming](), [understand](), [variable](), [writing]() ### AI overview This article explains why descriptive variable names make code easier for humans to read and maintain. It contrasts short, cryptic names with clearer names and notes that naming requires judgment rather than automatically improving code. ### Source excerpt While you are writing your code, the most important thing to have in mind is that you are writing your code first and foremost for humans to understand, and secondly for a machine to interpret. ## Handling configuration changes using static references DevFeed: [Handling configuration changes using static references]() Original publisher: [Read original article]() Author: Vladimir Jovanović Published: 2017-10-09T10:44:00Z Content type: tutorial Language: en Sources: [Vladimir Jovanović]() Topics: [configuration](), [Memory Leaks](), [Android](), [App]() Tags: [android](), [android-app-development](), [application](), [configuration](), [crash](), [leakcanary](), [memory](), [memory-leak](), [memory-management](), [os](), [rotation]() ### AI overview This Android article explains why using static references to preserve data across Activity configuration changes is unsafe. Such references can prevent the operating system from reclaiming memory, eventually causing the application to be killed and crash. ### Source excerpt What if you hold a static reference to the data in my Activity to preserve them on screen rotation? Why is that bad? ## Why Short Methods Improve Code Readability and Testability DevFeed: [Why Short Methods Improve Code Readability and Testability]() Original publisher: [Read original article]() Author: Vladimir Jovanović Published: 2017-10-02T22:44:00Z Content type: opinion Language: en Sources: [Vladimir Jovanović]() Topics: [functions](), [Code](), [Refactoring](), [context](), [test]() Tags: [clean-code](), [code](), [context](), [design-patterns](), [functions](), [programming](), [refactoring](), [software-architecture](), [software-development](), [test]() ### AI overview The author argues that methods should generally be short--often around 10 lines, with 25 lines as an upper limit--because they are easier to read, understand, test, and maintain. The article also explains how developers' implicit context can make long methods seem clearer to their authors than to future maintainers. ### Source excerpt My boss came to me and said: "Every method that you write should be less than 25 lines long" and I laughed, I laughed hard, right in his face. I was such a plonker!