Ship faster with one tool for your engineering team. Track issues, plan sprints, and write documents. Connect AI agents via MCP to automate your workflow.
Ahoy! Thanks to whoever posted a link to Airframes here on HN. I'm the founder of the project.
It's been a bit of a crazy 24 hours, and I haven't had enough time to fully surface and understand the impact that the ADSB Exchange sale has on everyone, the community, and Airframes.
Most of the Airframes effort has been fairly heads down, built in a tiny corner of the community and was not prepared for the events of the last day. Until now, most people weren't even familiar with technologies such as ACARS or VDL, limited to a mostly a small cross section of the community.
It has been a careful and deliberate effort to grow feeders & ingests slowly due to the nature of the data and infrastructure/storage needed, from both discovery (figuring out the data structures) and process (how to make use of it) perspectives. Requiring much of the efforts on the backend that the currently simple web app does not exactly reveal.
A new web app in development (there are some obvious and glaring issues/quirks with it now), and several other components, such as a desktop app, a mobile app, and a multi-architecture radio-focused OS to easily setup feeders (to Airframes, and the other aggregators) that will expand to other radio interests in time. There has been a lot of preliminary work on each of these.
The plan is to open source much of this over time.
If there is interest, I'm happy to elaborate more. I have been very transparent about the development process and implementations on the Discord in realtime. You are welcome to explore the dev channels there to get more background in the meantime.
Note that due to current events, I am taking on higher traffic than usual, unexpectedly, and everyone is still trying to understand what the impact of the recent events are.
Hey, I'm Kevin (founder of Airframes), and I'd like to give some background here.
While the world has been obsessing about ADS-B, which is primarily focused on positional data, I've been building a platform that is heavily focused on ACARS (often referred to as Plain Old ACARS), VDL (the successor to ACARS), HFDL (HF-based, also containing ACARS payloads), and SATCOM (such as AoA - ACARS over Insmarsat, and AoI - ACARS over Iridium).
The information in ACARS is quite interesting, and reveals significantly more about flights than ADS-B alone. The goal of the project has always been to provide a fuller picture of what is flying, including OOOI, routing, equipment status, fuel details, and more.
Some very early feeders and enthusiasts have been feeding data and supporting the effort, and as many/most HN folks know, this is all very time consuming.
Let me respond to your points too:
1. I'm a strong supporter of open source, and conceptually even open data. Your assessment that most of the stuff is still private is true. This is a strategic decision I have made. Having watched the aggregator space for many years now, my concern was that since we're still getting things built out (and I'm the only developer), a heavily budgeted competitor (such as FlightAware) could come along and enter the ACARS space long before we were ready and make the effort pointless.
I do plan to continue to open source and open data, and as it makes sense to, at my own expense, I will do so. Especially as more people become involved and build interest in ACARS.
2. The roadmap on the trello has not been updated, because, there were very few people interested in the effort and did not really engage in using it. But there is most definitely a roadmap -- some of the things are related to API, desktop/mobile app, a radio-focused OS (initially aimed at making it easy to feed to Airframes and other aggregators, but with the goal of wider radio interests) similar to OctoPi for OctoPrint.
3. Documentation has been in the works. But, seeing as that I have a lot of priorities (and it's mostly just me at the moment), it's not complete. I was hoping to release it when more digestible/ready. https://docs.airframes.io
4. I would hope that folks do consider supporting the effort, and there are a lot of big plans for it in the ACARS space.
Also, to put it bluntly, we were not yet ready for the events that unfolded. So there are some growing pains to deal with there.
I have been making a living building Rails apps for over a decade. It’s never too late, and while Rails is no longer the cool kid on the block, it is worth learning because:
1. There’s still a market for it. It shines at early stage, and plenty of companies like it, and the community is still decent (even though the energy of the early days is gone).
2. Many other newer frameworks and languages have borrowed many concepts from Rails and Ruby. Your learnings will translate!
3. It’s not all about money. Yes, you can make great money working with Ruby and Rails, but it’s a fun language and framework that cares about developer happiness (though, yes, there’s unhappy areas). So pick a language and framework that makes you enjoy your day. That’s why I have worked with Ruby so long.
4. Diversify. It’s not just about one language and framework. Learn other things too. Don’t put all your eggs in one basket (as it sounds like you kind of have with PHP). I particularly love learning Go, Dart, TypeScript, Vuejs, Nestjs, Swift, etc. Those are just a few. The point here is you learn the fundamentals in ways you will carry to whatever your future in programming will bring by taking some learnings from each one.
5. If you don’t actually enjoy learning new languages maybe consider another career? Not saying you should drop out of programming, but do what you love. We have one life to live. As cliche as that sounds, it’s true!
This is dangerous, in most cases, because clients are not looking out for you -- by definition they look out for themselves. It is not in your best interest to offer a fixed bid because undoubtedly problems out of your control will arise, and you are on the hook for it.
Furthermore, since the client is not always benevolent, you may be expected to implement changes outside of the scope of the contract, and this can often sour the relationship when you explain that it can't be done in the fixed bid you supplied. If you were upfront about a time and materials (T&M) beyond the agreement of the fixed bid, then you can protect yourself from this situation.
Unfortunately what most engineers tend to misunderstand about the role of their manager is that there are responsibilities outside of the team itself that the manager must perform.
Most managers are in simply supervisory roles, to watch over the team and ensure it's functioning, surviving, and thriving. That is what a supervisor or lead is for. While managers are certainly responsible for nurturing and growing their teams efficiently, they're also highly concerned with managerial duties to the company, which can often be unseen or misunderstood by their direct reports.
Managers often have responsibilities to the management team, the executive team, and other departments entirely. Take an IT department for example. All of the other departments in the company, including operations (where IT often sits to avoid conflict with engineering, and because largely it's an operational focus), are its internal clients, and the management in IT must work with the management of all other departments.
Meanwhile, IT engineers (sysadmins, devops, etc) often under recognize that this intricate dance is going on. The executive team will put pressures on the department, and the manager must delicately balance their needs with what the needs of the team are as well.
Thus, the engineer often looks for a manager that focuses solely on the team. But long term, the manager ends up having to account for the needs of the company. Any manager will need to do this.
It's ultimately important that the staff understands that their manager is superior to them simply because the position requires this of them (not necessarily because of any inherent skill advances). To look for an equal out of your manager is and will continue to be an exercise in futility.
The simple fact that if your startup has minimal capital (if any at all) and no revenue should indicate that spending a small fortune (potentially $2,500-10,000) to travel to a week long party (that's what SXSW is anyway) will only put you further into the debt hole that you need to make up for later. Who cares if you make $5,000 later on, because you're effectively still negative.
Some of these ego-whores are at every meetup, conference, mixer, breakfast, etc. Imagine how much of the startup's capital they are effectively wasting. All in the favor of "networking" --- 90% of which never pans out because most people at these events are all talk.
Sure, the events are fun, but they're not as productive as hunkering down and writing some code, reaching out to a potential customer, showing off a demo, or reviewing some feedback.
Hell yes! Well said. This makes me feel much less jealous of all the conference hoes running around acting like you need to be at a conference to get great things done.
Good idea, I need to sync the About page with the front page. The copy should be consistent and clear! Yes, the primary purpose of the site is to collaboratively learn topics, but there's no reason you need to do it with other people if you want to stay siloed.
I considered having the Add button below resources, but after you have 5 or 6 lists, the button disappears down the page. Haven't figured out a good solution for that yet. I looked into the button not working, and the bug is that it works on the list's page, but not on the manage page. Thanks!
I looked on other sites, and it seems pretty common to separate your profile settings (how people see your profile, etc) from your account settings (username, password, email). Any thoughts on how to make it more clear?
You're reading my mind. I already have a "next resource in list" feature, but have disabled it in the UI until it's complete. Also, there will be a way to do this on the dashboard across multiple lists, but I haven't come up with a good algorithm that users can control to determine what resources from which lists to do next. That might be overkill.
Unlike some of my colleagues, I am polite to recruiters. I never know when they might put me in touch with an early stage hire, even if it's out of scope from what they're doing now. Also, you never know when you're looking to scale and having some relationships in place can be helpful.
Don't forget, that even though they can be annoying and a bit out of touch with what position reqs actually are, they're human too, and a little short but polite response about your situation can go a long way.
I'm a long time HN lurker, and wanted to show a side project that I recently started working on that I think has some merit.
If you're an avid learner who is working on lots of different topics at any given time, as I know most HN folks are, you know that keeping track of what you are learning, the resources (books, tutorials, articles, courses, etc), and your progress along the way is difficult to do. LearnTribe solves this problem by providing a social way to organize and track your learning efforts.
I'd especially appreciate some honest, but constructive criticism about the concept and implementation. Note that the site is lacking a real design treatment (mood, colors, logo, etc) and needs a look at UX. I'm hunting for a design partner to take the project to the next level.
And my point about annoying other people was that I certainly could not beg my friends to help a different person every single day. It's not sustainable. I know for certain that every one of my friends would block my emails, social network updates, and phone calls.
I could ask them once, twice, maybe even ten times over the course of a year. But beyond that, it begins to mirror harassment. It's just not sustainable for one person to broadcast that many repetitive messages.
Though, I sure wish I could make the same efforts to tell people about each individual of the thousand other people in need, as I have about Amit.