Tags: Coding

screen_shot_2018-07-01_at_1.24.35_pm.jpg

Big O notation is a mathematical representation of how an algorithm scales with an increasing number of inputs. Using Big O notation, developers and engineers can construct the best algorithm that fits within their constraints.

Big O Notation? More like Big O-M-G

There are a lot of ways to write algorithms for a specific task. Since there are so many variations, how does someone know which algorithm to use in which situation? One way to look at the problem is to ask yourself: what limitations are present and how can I check if the algorithm fits within...
Read 0 Comments

Squinting at ASCII on Linux

ASCII plays a much more important role on our systems than generating techno-art. Let's explore the commands that allow you to see how it works. ASCII came about to circumvent the problem that different types of electronic systems were storing text in different ways. They all used some form of ones...
Read 0 Comments

How to Implement Dijkstra’s Algorithm in JavaScript

I’ve been reading Grokking Algorithms, which I recommend to anyone new to algorithms. It’s basically the introduction I wish I had a few months ago! The examples in the book are written in Python, so I’d like to share a JavaScript version of Dijkstra’s algorithm. This algorithm uses a directed,...
Read 0 Comments

Practical Functional Programming

The following is reformatted from a presentation I gave at LinkedIn last year. The presentation attempted to explain functional programming without using concepts like “monads” or “immutability” or “side effects”. Instead it focuses on how thinking about composition can make you a better programmer...
Read 0 Comments

Why Senior Devs Write Dumb Code and How to Spot a Junior From A Mile Away

One of my all time favorite quotes is from Brian Goetz, a smart dude in the Java world who is one of the authors of Java Concurrency in Practice, among other things. The quote appears in an interview that Oracle published under the title, “Write Dumb Code”. Goetz was asked how to write code that...
Read 0 Comments

Tracing Memory Leaks in the NFC Digital Protocol Stack

By Thierry Escande, Senior Software Engineer at Collabora. Kmemleak (Kernel Memory Leak Detector) allows you to track possible memory leaks inside the Linux kernel. Basically, it tracks dynamically allocated memory blocks in the kernel and reports those without any reference left and that are...
Read 0 Comments

Starting Out In Development - Subversion

This is and entry in a series about Starting Out In Development. The goal of this series is to provide brief introductions to critical tools, concepts, and skills you'll need as a developer. By now you should be familiar with what version control is. If you're unsure, check out my article ...
Read 0 Comments

Secrets of Writing Good Documentation

Taylor Barnett, a Community Engineer at Keen IO, says practice and constant iteration are key to writing good documentation.  At the upcoming API Strategy & Practice Conference 2017, Oct. 31 -Nov. 2 in Portland, OR, Barnett will explain the different types of docs and describe some best...
Read 0 Comments

Review by Many Eyes Does Not Always Prevent Buggy Code

Writing code is hard. Writing secure code is harder—much harder. And before you get there, you need to think about design and architecture. When you're writing code to implement security functionality, it's often based on architectures and designs that have been pored over and examined in detail....
Read 0 Comments

Secure Coding in Java: Bad Online Advice and Confusing APIs

For programmers and software developers, the Internet forums provide a great place to exchange knowledge and seek answers to concrete coding conundrums. Alas, they are not always the source of accurate information. A group of Virginia Tech researchers has analyzed hundreds of posts on Stack...
Read 0 Comments

Pages

Click Here!