Fresh on the heals of our TS Party comes this curated list of tools for getting the most out of static code analysis. This list is gloriously polyglot, so there’s probably something in there for everyone.
Not in to static analysis (or just a huge fan of lists)? Check out the sister project, Awesome Dynamic Analysis.
“GUIs are bloatware” — Terminal rules…a guide to the terminal…
In this post, I’ll walk you through everything you need to start making your terminal a complete development environment: how to edit text efficiently, configure its appearance, run and combine a myriad of programs, and dynamically create, resize and close tabs and windows.
Earlier this year Retool ran a survey of developers and builders on internal tools to learn how people build and maintain their internal tooling. The survey had 310 respondents, mostly in SaaS, Finance, and Retail, and mostly from mid sized (2-500 employees) companies. This report outlines the results and insights they learned.
The tldr is internal tooling is really important, but rarely gets the time and focus they need.
Programming around time is the bane of pretty much every programmer’s existence. UTC works most of the time, but still has its flaws.
Zach Holman writes on his blog:
Programming time, dates, timezones, recurring events, leap seconds… everything is pretty terrible. The common refrain in the industry is Just use UTC! Just use UTC! And that’s correct…sort of. But if you’re stuck building software that deals with time, there’s so much more to consider. It’s time…to talk about time.
Zach includes a lot of time-related puns and whole lot of wisdom about programming time.
As we gear up for the launch of Practical AI and more AI/ML/DS related news coverage, I wanted to bring to your attention to this 6-month apprenticeship (compensated) in AI research at OpenAI.
We’re now accepting applications for the next cohort of OpenAI Fellows, a program which offers a compensated 6-month apprenticeship in AI research at OpenAI. We designed this program for people who want to be an AI researcher, but do not have a formal background in the field. Applications for Fellows starting in September are open now and will close on July 8th at 12AM PST.
I love this with my whole heart. 🤤
In total the project took a year and a half to upgrade from Rails 3.2 to Rails 5.2. Along the way we took time to clean up technical debt and improve the overall codebase while doing the upgrade. Below we’ll talk about how we upgraded Rails, lessons we learned and whether we’d do it again.
Congrats to Eileen and the team on this massive effort! Click through to read how they did it and the lessons the learned along the way.
This list is a lot longer than I expected! Alongside each app is an icon indicating whether it’s written in Swift or Objective-C, which is nice for those of us looking for reading material. 💪
From Heroku’s Code[ish] podcast, Rick Newman (Director of Engineering at Heroku) talks with Mikolaj Pawlikowski, author of “Chaos Engineering.”
Chaos engineering is a way of testing your software predicated on the fact that something in your system, at some point, will break. By intentionally causing disruptions–for example, dropping network connections–and observing how your system responds, you’ll better prepare yourself for when the unexpected happens.
If you need a JS runtime that supports TypeScript out of the box and has security as a top-most priority, star this repo and come back when it’s no longer “Segfaulty”.
Feature bullets! 👇
- No package.json, no npm. Not backwards compatible with Node
- Single executable
- Defaults to read-only file system access
- Always dies on uncaught errors
- Supports top-level await
EDIT: it’s worth noting that this project is by Ryan Dahl, inventor of Node.js.
Inspired by Vim’s modal editing, but built to be as simple as possible. This is no fly-by-night proof of concept. It’s 3 years in the making and looks extremely polished.
I’m definitely going to give Amp a test-drive. 👌
Amjith shares a simple git alias he uses to resume work from where he left off. Perhaps you’ll find it useful, too.
mostly’s purpose is to serve as a lightweight, easy-to-comprehend starting point, with a focus on providing a great developer experience while helping you get high quality and maintainable web applications deployed rapidly.
It uses Express for the server and React for the client. Worth a look if you’re starting up a new web project. I dig this point about it:
Nothing is hidden, nothing is magical, and all of the “plumbing” is accessible and simple.
Olivier Lacan on why we should all stop using
cd and start using
j (a.k.a. autojump). I’ve been wasting soooo many keystrokes over the years! 😱
A fun little side project by Mislav Cimperšak where you plug in a few values and it generates a shareable replica of XKCD’s famous Compiling comic. Here it is in action with a piece of modern art I call, “Low Hanging Fruit”. 😁
Mint is super cool, but handing over your precious financial information to a 3rd-party is always a bit nerve-racking. Evan You’s new Node app builds a bridge between Plaid (for bank access) and Google Sheets (for data storage) so you can roll your own system.
Now you only have to trust your precious financial information to two 3rd-parties 😉. But! This is open source so at least you don’t have to trust the application code.
Vuido makes it possible to create lightweight, native desktop applications using Vue.js. Application using Vuido can run on Windows, OS X and Linux, using native GUI components, and don’t require Electron.
Emphasis added. Vuido uses libui under the hood to drive its cross-platform GUI components.
Stripe Atlas has a wide array of guides to running an internet business that are totally open and free for everyone. This guide is on “scaling engineering organizations” and covers everything from recruiting and hiring, training and on-boarding, to retention.
If you haven’t checked this out yet, it’s a 15 minutes or less read.
Hackable and configurable to the core, signale can be used for logging purposes, status reporting, as well as for handling the output rendering process of other node modules and applications.
Dimitri Fontaine shares 3 classic data-modeling anti-patterns. The UUID section lacks strong argumentation, but the real gem in this article is his advice at the end. A snippet:
My advice is to always normalize your database model first, and then only fix the problems you have with that when you actually have them. Well except in those 3% of cases where really, really, it should be done in the design phase of the project. It’s quite hard to recognize those 3% though, and that ability is hard gained with experience.
Experience is the ultimate teacher.
What are you most excited about for this upcoming release of Go?