Programming

> Bpesquet

General aspects between Elm and JS. 2017-05-08 by Franzé Jr.

This is Part 1 in a series about Elm for JavaScript Developers. I've been programming in JavaScript for a while, and hearing people speak so highly about Elm inspired me to give it a try! Studying Elm has raised several questions about this language. The idea of this text is to introduce Elm to JavaScript developers like myself. If you're reading this, you're probably aware of what Elm is, but let's go overt it. In this blog series, we will compare Elm with JavaScript.
A dive into spatial search algorithms – Vladimir Agafonkin – Medium.

I’m obsessed with software performance.

One of my main responsibilities at Mapbox is discovering ways to make our mapping platform faster. And when it comes to processing and displaying spatial data at scale, there’s no concept more useful and important than a spatial index. Spatial indices are a family of algorithms that arrange geometric data for efficient search. For example, doing queries like “return all buildings in this area”, “find 1000 closest gas stations to this point”, and returning results within milliseconds even when searching millions of objects.

Spatial indices form the foundation of databases like PostGIS, which is at the core of our platform. In the last 4 years, I’ve built a bunch of ultra-fast JavaScript libraries for spatial search: rbush, rbush-knn, kdbush, geokdbush (with a few more to come). Spatial search problems Spatial data has two fundamental query types: nearest neighbors and range queries. K nearest neighbors. VanRoyChapter. Your first GraphQL component – Abhi Aiyer – Medium. If you follow my musings surely you must know how enamored I am with GraphQL.

Frequently asked questions I get aren’t really about how it works anymore, but rather: How do I get started and build something? Today I want to get you your first win. Today, let’s build a little UI Component who’s data is backed by a GraphQL API. Since this is more of a front-end tutorial, we will be picking from a list of public GraphQL APIs. There were many options for a public API here: and what we go over here can apply to any of these! I’m going to try to go step-by-step here, so try and follow along!

Prolog

Exercism.io. So You Want to be a Functional Programmer (Part 1) – Medium. Taking that first step to understanding Functional Programming concepts is the most important and sometimes the most difficult step.

But it doesn’t have to be. Not with the right perspective.
Playbook for software design and development. We are thoughtbot.

We have worked with hundreds of product teams all over the world, from individual founders who are self-funded, to large multi-national organizations. We have also created our own products and dozens of open source libraries. This is our playbook. It details how we make successful web and mobile products, and also how we run our company. It's filled with things we've learned based on our own experience and study of others' experiences. It is a living document that everyone at thoughtbot can edit in a private GitHub repo. We've made the playbook free and licensed it as Creative Commons Attribution-NonCommercial so you may learn from, or use, our tactics in your own company.

Product Design Sprint All our projects are design-led, starting with post-its and sketching, ending with design implemented as code in the app.
The Practical Guide to Becoming a Professional Web Developer — Free Code Camp. This article is meant to serve as a practical guide to becoming a professional web developer.

I’ve spent over 20 years writing code for the web. I work with and help developers daily. In this article, I will tell you what you should learn, when you should learn it, and where you can learn it from (usually for free).
Being A Developer After 40. Being A Developer After 40 (This is the talk I have given at App Builders Switzerland on April 25th, 2016.

.NET

Phoenix Framework. Elixir. REST. Architecture. Git. What To Know Before Debating Type Systems. Recently, it was brought up on Proggit that Chris Smith's "What to Know Before Debating Type Systems" was no longer online.

This is a really great article, and in an effort to make sure it survives, I've grabbed the archive.org cache and am 'reprinting' it here. If you're into programming languages, read this and level up! EDIT: Chris has placed it back online. You can find it here. Without further ado, "What to Know Before Debating Type Systems": What To Know Before Debating Type Systems I would be willing to place a bet that most computer programmers have, on multiple occasions, expressed an opinion about the desirability of certain kinds of type systems in programming languages.

There are a few common misconceptions, though, that confuse these discussions. Classifying Type Systems Type systems are commonly classified by several words, of which the most common are "static," "dynamic," "strong," and "weak.
"

He will be speaking at our CloudBeat conference later this month. In the wild kingdom of cloud computing, there are still a few mountains to summit. Development in the cloud is a big one. Software is truly eating the world, and today code and the teams writing it are the crown jewel of almost any business. Today, everything a modern software development team needs is available as a pay-as-you-go service, spun up in minutes and blended together better than a Wendy’s Blizzard.

There’s no perfect guide to a setup, and mileage will vary by team, but the basics include: Learning to code: If you’re new to the dark arts, start with an online tutorial or two to get a flavor of what it’s all about. Workflow of champions The real magic happens when these services are fluidly connected together, creating a whole easily greater than the sum of its parts.