From Cooking to Coding

It’s difficult to think of two careers more contrasting than chef and web developer. I would venture to put myself into a fairly unique category of people who have done both. Factor in my gender, with females making up an average of 39% of web developers and 20% of chefs, and that makes me rather unique indeed.

Just how big are the differences between these two career paths? Looking at some studies of overall job satisfaction, the answer is…pretty big.

The 100 Best Jobs of 2015**
#11 - Web Developer
The 200 Worst Jobs of 2015**
#3 - Cook
So, I basically went from having one of the absolute lowest rated jobs of all time to having one of the highest. If you’re wondering how much of an impact this change had on my life, know that it was massive.

I don’t have to read any of those articles to know what makes working in a kitchen awful, and what makes designing and developing websites so great. I’ve lived it. And I’d like to share some of my experiences with you.

A Little Backstory
In 1998, my older brother Nick had discovered the internet. He was always learning new things and honing new talents at that time - drawing, writing, music - and he loved to share what he learned with me. I will never forget him drawing a diagram explaining the meaning of a href and img src as I watched in uncomprehending fascination.

Nick never viewed a page source again, but I was already hooked. Designing websites became one of my main hobbies and means of self-expression, along with art and music.

Over the next decade, I witnessed first hand the evolution of design and code: the birth of CSS; layouts of frames to tables to floats; fixed and fluid width arguments.

Throughout my adolescence, I never read a tutorial or book about web design. I simply wasn’t interested in “being a great developer” or really understanding how the code works. I just wanted to make something, and make it look a certain way, so I played around with it until it did.

I never thought about college, and I never considered the web as a possible career field. Rather, I took every art class that was available and spent most of my time drawing. Art school seemed like the logical choice for me, so no one was more surprised than myself when I ended up going to culinary school.

For the next 8 years, web design was forgotten. Life was all knives and flames, scars and stress. I had always been determined and unafraid of hard work - mandatory traits in the restaurant industry - and I quickly excelled from cook to chef-manager by 22.

As the years wore on, the novelty of my new career faded, the urge to prove myself became pointless, and it became increasingly hard to understand or justify the choices I had made. At some point, I realized 8 years of culinary experience on my resume could only lead to 8 more years of culinary experience.

I knew cooking wasn’t my passion, or even a job I wanted to tolerate anymore. I wanted to find out what color my parachute was. I set off on a journey of self-discovery. I quit my job and went solo camping.

I read a host of autobiographies, filled out tests and diagrams, and wrote journals. It always came back to the same main point.

What fascinates you so deeply that life, the world and time all cease to exist?
What can you work on for hours and feel like minutes have passed? What has endless possibilities for learning and improvement? What pulls you in and makes you forget everything else?

For me, it was and has always been making websites.

You might think that figuring that out was the easy part, and the journey from inexperienced chef with no portfolio to web developer was the hard part, but it was very much the opposite. Self-actualization is not easy; taking the time to be honest with yourself and reflect, learn, and improve is a process. Deciding to leave your stable job for the unknown is terrifying. As they say, nothing worth doing is easy.

“Nothing in the world is worth having or worth doing unless it means effort, pain, difficulty.”

Theodore Roosevelt

#notes #career #visual studio code #visual studio #code

What is GEEK

Buddha Community

From Cooking to 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