Topics /

Software Engineering

The most popular blog posts about software engineering on Hacker News. 21,834 posts.

Any year
12456

What is a Full Stack developer? (2012)

Is it reasonable to expect mere mortals to have mastery over every facet of the development stack? Probably not, but Facebook can ask for it. I was told at OSCON by a Facebook employee that they only hire 'Full Stack' developers. Well, what does that mean? To me, a Full Stack Developer is someone with

12462

.NET Core RC2 – Improvements, Schedule, and Roadmap

Updated (2017): See .NET Core Releases to learn about newer releases. This post was written by Scott Hunter. You all want .NET Core 1.0 RC2, you want a schedule, and you want to go live. Today we’ve got a schedule to share plus some changes that will improve things for everyone in the .NET Community going forward. The…

12464

Transcending Posix: The End of an Era?

In this article, we provide a holistic view of the Portable Operating System Interface (POSIX) abstractions by a systematic review of their historical evolution. We discuss some of the key factors that drove the evolution and identify the pitfalls that make them infeasible when building modern applications.

12470

How Does One Create A Gtk+ Application?

How does one go about creating a gtk+ working application? Is it even possible? Seriously. TL;DR: The Gtk+ ABI is broken so often that distribution-supplied binaries rarely work. * * * Imagine it is the time when Gtk+ 3.0 was released. You have a beautiful application with no bugs. For the sake of argument…

12477

Emacs: The macOS Bug

The Context I have been recently roaming. Doing some Zig, doing some Go, some Janet. Some C integration. Should have focused on my project but life threw more at me than I could handle, so I sought… happy distractions. My experience with those technologies taught me new tricks and one day, when I needed some more…

12479

On undoing, fixing, or removing commits in git

This document is an attempt to be a fairly comprehensive guide to recovering from what you did not mean to do when using git. It isn't that git is so complicated that you need a large document to take care of your particular problem, it is more that the set of things that you might have done is so large that different…