Archie Mistry

Archie Mistry


What to do if you’ve lost passion for coding?

I recently stumbled upon a Reddit thread where someone said they had lost all interest in programming. By reading through the thread, one can quickly assume it’s the case of burnout.

You would be right to say so. Luckily, it turns out that’s quite common among us programmers, especially among JavaScript developers since the landscape is moving too fast underneath.

Programming is a difficult skill to master and requires great perseverance to get good at. The grind can be too much at times — remember, if something is hard, it’s worth doing, as nothing good comes easy.

The thread really inspired me as I’ve been in a similar situation a couple of times as well. I’ve been really burned out and bummed, and I want to share how I managed to cope with it and regain my passion for coding.

Work on Side Projects

Nothing beats having no boss and deadlines. You can work on any project without limitations and with the freedom of making your very own tech stack choices.

Want to use a framework that came out two weeks ago? No one is going to stop you. If you lack ideas on what to build, pick something from this list

However, in the situation you’re already working a 9 to 5 job as a coder, it’s understandable when there isn’t a single bone left that wants to sit down and write even more code that day.

For occasions like those, working on side-projects might make things even worse since you’re pushing yourself over the edge. Be honest with yourself and take some time to think where you stand on the spectrum.

There’s a huge gap between if you actually like coding, but just hate your day job and do you really just dislike coding and need a break.

In the case that you like coding, but hate coding during the day, here’s some advice on how to change that.

Jump Ship and Look for New Challenges

The above is a polite way to say that you might consider changing jobs. It’s totally normal to get bored and comfortable with your current job. Boredom happens when the things you’re working on aren’t challenging you enough anymore.

This is bound to happen if you worked at the same place for over five years. We, humans, are addicted to stimulation, we can’t stand to sit quietly in a room all by ourselves for even 30 minutes.

Of course, you might not have to completely change companies — start small by talking to your manager — ask to work on a new project.

If they deny you this opportunity, time to pack up your stuff and make the bold move of changing companies. You’ll thank yourself later and wonder what took you so long to make those changes.

If you do decide to change jobs, I’d recommend brushing up on your interview skills with the _Here Are 8 Questions You Should Ask Your Employer Before Taking the Jo_b article. It’s a quick read and points you in the right direction when it comes to picking a non-toxic company culture.

Take a Break From Coding and Pick Up New Hobbies

Mixing it up is always a noble idea. I’ve had to deal with my fair share of procrastination — I would get up in the morning and fantasize about all the things I want to accomplish, only to procrastinate half of the day.

Once you’ve lost half a day for nothing, panic is quick to hit. Coding isn’t something one can properly do under a lot of time pressure and panic.

Pick up running, cooking, archery, or Brazilian Jiu-Jitsu. If you have less time to procrastinate, you’ll be more productive. From my personal experience, I started to really appreciate and separate my work time once I picked up more than a handful of hobbies.

If you’re an experienced developer and just need a breath of fresh air — pick up a new programming language instead. It’s a dangerous game for sure, but I’ve seen it work plenty of times.

With a new programming language, everything looks new and shiny, thus it might reinvigorate the passion in you.

Exercise As Much as You Can

Programming is a truly stationary job — it’s terrible for the body. We’re not supposed to sit for eight to 12 hours per day. Our ancestors were hunters and gatherers, often nomads without a permanent residence.

If you’re young, you don’t feel it as much, but as you get older, you start to feel more grumpy and less healthy.

As a coder, It’s crucial to balance your life by exercising as much as you can. I can understand if you dislike running, but it’s not a reason not to exercise. It’s on you to explore and find something you truly like.

For example, I’m heavily addicted to Brazilian Jiu-Jitsu since it allows me to clear my mind. I might step on the mat with doubting thoughts and anxiety, and once I step off the mat, poof! All worries are gone. Has to do something with the wild endorphins.

If Nothing Helps — Take a Vacation

I love programming so much that I took my first vacation at the age of 23. I’m not bragging, or anything.

But of course, I went on a vacation to Ireland for a reason. I consider myself consistent and having a strong will to grind — I needed to escape it all and just forget about coding.

Everyone needs a vacation, be it spending more time with your family or visiting another country across the eternal ocean. Take care of yourself, you deserve it.


Thanks for reading, I hope you stick with programming. It’s a wild ride, but totally worth it. Feel free to talk to me privately if you’re having anxiety, worries, or a bad day.

#programming #development #code

What is GEEK

Buddha Community

What to do if you’ve lost passion for coding?
Tyrique  Littel

Tyrique Littel


Static Code Analysis: What It Is? How to Use It?

Static code analysis refers to the technique of approximating the runtime behavior of a program. In other words, it is the process of predicting the output of a program without actually executing it.

Lately, however, the term “Static Code Analysis” is more commonly used to refer to one of the applications of this technique rather than the technique itself — program comprehension — understanding the program and detecting issues in it (anything from syntax errors to type mismatches, performance hogs likely bugs, security loopholes, etc.). This is the usage we’d be referring to throughout this post.

“The refinement of techniques for the prompt discovery of error serves as well as any other as a hallmark of what we mean by science.”

  • J. Robert Oppenheimer


We cover a lot of ground in this post. The aim is to build an understanding of static code analysis and to equip you with the basic theory, and the right tools so that you can write analyzers on your own.

We start our journey with laying down the essential parts of the pipeline which a compiler follows to understand what a piece of code does. We learn where to tap points in this pipeline to plug in our analyzers and extract meaningful information. In the latter half, we get our feet wet, and write four such static analyzers, completely from scratch, in Python.

Note that although the ideas here are discussed in light of Python, static code analyzers across all programming languages are carved out along similar lines. We chose Python because of the availability of an easy to use ast module, and wide adoption of the language itself.

How does it all work?

Before a computer can finally “understand” and execute a piece of code, it goes through a series of complicated transformations:

static analysis workflow

As you can see in the diagram (go ahead, zoom it!), the static analyzers feed on the output of these stages. To be able to better understand the static analysis techniques, let’s look at each of these steps in some more detail:


The first thing that a compiler does when trying to understand a piece of code is to break it down into smaller chunks, also known as tokens. Tokens are akin to what words are in a language.

A token might consist of either a single character, like (, or literals (like integers, strings, e.g., 7Bob, etc.), or reserved keywords of that language (e.g, def in Python). Characters which do not contribute towards the semantics of a program, like trailing whitespace, comments, etc. are often discarded by the scanner.

Python provides the tokenize module in its standard library to let you play around with tokens:



import io


import tokenize



code = b"color = input('Enter your favourite color: ')"



for token in tokenize.tokenize(io.BytesIO(code).readline):





TokenInfo(type=62 (ENCODING),  string='utf-8')


TokenInfo(type=1  (NAME),      string='color')


TokenInfo(type=54 (OP),        string='=')


TokenInfo(type=1  (NAME),      string='input')


TokenInfo(type=54 (OP),        string='(')


TokenInfo(type=3  (STRING),    string="'Enter your favourite color: '")


TokenInfo(type=54 (OP),        string=')')


TokenInfo(type=4  (NEWLINE),   string='')


TokenInfo(type=0  (ENDMARKER), string='')

(Note that for the sake of readability, I’ve omitted a few columns from the result above — metadata like starting index, ending index, a copy of the line on which a token occurs, etc.)

#code quality #code review #static analysis #static code analysis #code analysis #static analysis tools #code review tips #static code analyzer #static code analysis tool #static analyzer

Samanta  Moore

Samanta Moore


Guidelines for Java Code Reviews

Get a jump-start on your next code review session with this list.

Having another pair of eyes scan your code is always useful and helps you spot mistakes before you break production. You need not be an expert to review someone’s code. Some experience with the programming language and a review checklist should help you get started. We’ve put together a list of things you should keep in mind when you’re reviewing Java code. Read on!

1. Follow Java Code Conventions

2. Replace Imperative Code With Lambdas and Streams

3. Beware of the NullPointerException

4. Directly Assigning References From Client Code to a Field

5. Handle Exceptions With Care

#java #code quality #java tutorial #code analysis #code reviews #code review tips #code analysis tools #java tutorial for beginners #java code review

Houston  Sipes

Houston Sipes


How to Find the Stinky Parts of Your Code (Part II)

There are more code smells. Let’s keep changing the aromas. We see several symptoms and situations that make us doubt the quality of our development. Let’s look at some possible solutions.

Most of these smells are just hints of something that might be wrong. They are not rigid rules.

This is part II. Part I can be found here.

Code Smell 06 - Too Clever Programmer

The code is difficult to read, there are tricky with names without semantics. Sometimes using language’s accidental complexity.

_Image Source: NeONBRAND on _Unsplash


  • Readability
  • Maintainability
  • Code Quality
  • Premature Optimization


  1. Refactor the code
  2. Use better names


  • Optimized loops


  • Optimized code for low-level operations.

Sample Code


function primeFactors(n){
	  var f = [],  i = 0, d = 2;  

	  for (i = 0; n >= 2; ) {
	     if(n % d == 0){
	       n /= d;
	  return f;


function primeFactors(numberToFactor){
	  var factors = [], 
	      divisor = 2,
	      remainder = numberToFactor;

	    if(remainder % divisor === 0){
	       remainder = remainder/ divisor;
	  return factors;


Automatic detection is possible in some languages. Watch some warnings related to complexity, bad names, post increment variables, etc.

#pixel-face #code-smells #clean-code #stinky-code-parts #refactor-legacy-code #refactoring #stinky-code #common-code-smells

Fannie  Zemlak

Fannie Zemlak


Softagram - Making Code Reviews Humane

The story of Softagram is a long one and has many twists. Everything started in a small company long time ago, from the area of static analysis tools development. After many phases, Softagram is focusing on helping developers to get visual feedback on the code change: how is the software design evolving in the pull request under review.

Benefits of code change visualization and dependency checks

While it is trivial to write 20 KLOC apps without help of tooling, usually things start getting complicated when the system grows over 100 KLOC.

The risk of god class anti-pattern, and the risk of mixing up with the responsibilities are increasing exponentially while the software grows larger.

To help with that, software evolution can be tracked safely with explicit dependency change reports provided automatically to each pull request. Blocking bad PR becomes easy, and having visual reports also has a democratizing effect on code review.

Example visualization

Basic building blocks of Softagram

  • Architectural analysis of the code, identifying how delta is impacting to the code base. Language specific analyzers are able to extract the essential internal/external dependency structures from each of the mainstream programming languages.

  • Checking for rule violations or anomalies in the delta, e.g. finding out cyclical dependencies. Graph theory comes to big help when finding out unwanted or weird dependencies.

  • Building visualization for humans. Complex structures such as software is not easy to represent without help of graph visualization. Here comes the vital role of change graph visualization technology developed within the last few years.

#automated-code-review #code-review-automation #code-reviews #devsecops #software-development #code-review #coding #good-company

Vincent Lab

Vincent Lab


Let's Talk About Selling Your Code

In this video, I’ll be talking about when do I think code is ready to be sold.

#should you sell your code? #digital products #selling your code #sell your code #should you sell your code #should i sell my code