HNHacker News
TopNewBestAskShowJobs

hrishi

374 karma · joined July 21, 2019

https://southbridge.ai https://olickel.com
submissionscomments
hrishi··on SparkFun Hooks a Patent Troll
Agreed about size when it comes to suing for patent rights. However, the problem with patent trolls is the same as copyright trolls: they send out unimaginable amounts of spurious notifications in the hope that some will pay. The spam really is the problem here.

I have no problem with a company - any company - making a serious allegation against someone else using IP they hold. They deserve to be heard. Being able to send out 1000 of these in a day without consequence is a big problem.

How about something like an exponential ratchet or cool down period for losing patent lawsuits? Maybe the cost to file (or damages if you lose) doubles after every 10th lawsuit you lose against 10 different entities, for a year.

hrishi··on Link shorteners: the long and short of why you shouldn’t use them
Feels like a bad idea. Shortened links often don't need the level of longevity blockchains provide, nor will they be able to afford the cost if decentralized storage with high availability.
hrishi··on A Project of One’s Own
Good point, and it makes me wonder if it's just a personality thing. Some of the best people I know are never obsessed with anything, and try to maintain things in moderation, while I (and many others) find it easier to be obsessed and driven in a few things, often to the exclusion of other things.
hrishi··on A Project of One’s Own
I hate the obsession with grades as much as anyone, but most parents are often mirroring the importance we place on them as a society. Disagree with a number of the sub-comments here, grades matter. Not eventually and not on their own, but they provide optionality the same way race and wealth and other factors do: you can succeed without them, but it definitely helps your chances.
hrishi··on Command Palette Interfaces
A command palette is what we're basing our UX rebuild over at https://grey-wing.com, so I can point out some additional benefits, drawbacks and fixes:

A command palette when implemented correctly, can also strike a balance between older users and power users. It doesn't hold power users back, but the verbose nature of the instructions and command (no more undecipherable icons and strange UI interactions) can also be easier for older, less techy users - IF implemented well with a lot of testing.

There is still a lack of discoverability with a command palette. Our solution has been to include commonly used commands, and most popular commands alongside, as well as introducing some new ones intermittently.

One more problem is context. More complicated commands may be harder to grok or conversely very long for users to remember. The UNIX solution is switches, which is short but hard to remember (https://xkcd.com/1168/), and the alternative is long sentences which is hard to parse, perhaps too long, and has too much variation to be reliable.

Finally, they're also a great way to discover what paths your users would like to go down but can't. It's hard to understand what button they couldn't find or what label they didn't understand from a traditional UI, even with extensive user interviews and analytics. With an omnibox, each failed search is a point of information to you.

hrishi··on Employees are quitting instead of giving up working from home
I really don't see that happening except in the very upper echelons of work.

When there's more competition, the guy willing to work longer will always win, especially if the work is such that he can work longer without a decrease in quality.

We're automating more things, there's more of us around, and we're connecting job markets better every day. There's more competition.

hrishi··on A virtual machine for microcontrollers
I see how the title might mislead one into thinking that the author was about to outline his problems fitting V8 into a uC, but I don't understand the upset that he was successful.

If successful, the streaming service with lack of relocation should be a useful tool in the toolkit for working with microcontrollers. I don't see much use for it for me at the moment, but then I haven't used uLisp much either.

hrishi··on Stripe isn’t a platform, it’s a mouse
Agreed, with perhaps the exception of Apple. They've remained a platform, with a healthy amount of apps they own and operate outright, and sweeping control of their ecosystem elsewhere.

Maybe not forever it looks like though.

hrishi··on The Expanse UI Design
I imagine some futuristic version of git where... basically git but they've got better merge algorithms after they've solve NP and P.

You can sync to the trees of ships near you and catch up, and once in a while one of them gets to a station and updates to the tip of wherever development is at.

hrishi··on Floor, Ceiling, Bracket
Echoing a lot of the sentiment here, I wish math would simply use english (or natural language). It clearly seems too much to ask for a programming language, especially when it comes to pure math.

At an undergrad math course, we were allowed to state our proofs in english without any notation. This was the only course that did this. I found it easier to write and reason about my proofs, it was incredibly easy to read my peers', and the professor had no issues with my work while he did have some trouble with some of the notation.

When I first started, the question I had was if there existed an encyclopedia or an OED for mathematical notation. I was told there wasn't. I then enquired how I would go about deciphering something I didn't understand, and was told that I should ask my professors and peers. I brought one of the papers I had found online to him, and he asked me to write to the author because he couldn't understand it either.

Meanwhile I can download any old piece of code, and given enough time with the compiler and myself, I can understand what it means to express. I shudder to think 9f the sheer body of work that relies on a vague understanding of the notations in the underlying proofs.

For a science that believes in precision of logic, I ask: how is this still a thing?

hrishi··on Is It Pokemon or Big Data?
I'm sad I only have one upvote to give. Please have it.
hrishi··on Launch HN: Greywing (YC W21) – Automated ship operations focused on crew
Nick's right here - as we operate shoreside (we're beginning to work on helping operations onboard vessels), connectivity is less of an issue.

That said, maintaining realtime information for decision making does have to deal with spotty data (AIS for example, may drop out), so all of our sources have fallback and catch safeties that will (depending on the source and the action context) fall back to a best value, or prevent the action entirely if there is not enough confidence.

hrishi··on Launch HN: Greywing (YC W21) – Automated ship operations focused on crew
Definitely appreciated, thanks!
hrishi··on Launch HN: Greywing (YC W21) – Automated ship operations focused on crew
Exactly right - it's a legacy feature we keep not to break some user flows, we're looking to rebuild that pretty soon.
hrishi··on Launch HN: Greywing (YC W21) – Automated ship operations focused on crew
Some parts are actually in C, but they've all been.. containerized.

I'll see myself out.

hrishi··on Vessel Finder
We're focused on routing (shoreside) and not navigation at the moment, so we've been able to build a custom in-house map focused on the needs of crew managers and operators.

Unfortunately you're right about the rest - it's a problem that's pervasive throughout maritime. We've had to build our own routing engine, port database, and much more that we initially expected to buy/use.

hrishi··on Launch HN: Greywing (YC W21) – Automated ship operations focused on crew
It's a mix really: all of them care about the cost savings, but the UI and the opportunity to digitize and connect different parts of the business have also been strong drivers.

First-generation software has been around just long enough in maritime that a lot of organisations are feeling the pain from having multiple solutions that don't connect and are starting to show their age.

hrishi··on Launch HN: Greywing (YC W21) – Automated ship operations focused on crew
Could be! Sometimes things get stuck up there and over time weather down to something I can no longer Google or remember attribution for :)
hrishi··on Vessel Finder
this is awesome, will definitely be checking it out.

ADS-B is definitely more popular than AIS, and I've always wondered why. Perhaps it's that airplanes evoke more wonder, and is more accessible over land than poor old ships?

Do DM me if you're looking for a position, or if you'd just like to chat about vessels, AIS and anything maritime.

We're building maritime intelligence at Greywing (https://grey-wing.com), and I'd love your input. In fact we have a Launch HN post up right now, so if you have any thoughts do drop them in!

hrishi··on Launch HN: Greywing (YC W21) – Automated ship operations focused on crew
We've been using PostGIS' internal storage mechanism for routes and tiles so far. We've attempted to build our own indexing (through quadtrees indexed similar to OSM's), but it's never crossed the performance we get by default from PostGIS.

It's not a bottleneck yet, but I'm sure we'll be revisiting this soon. Thanks for the link! I hadn't found this one yet - super helpful.

hrishi··on Launch HN: Greywing (YC W21) – Automated ship operations focused on crew
We've been using a mutated blend of our own patterns with the ones you mentioned, but you're 100% spot on.

The reason we have a product today with 100% uptime and reasonable tech debt is that we front-loaded the cost of data by making sure we normalize (which is non-trivial in maritime), along with cleaning and consolidation with other sources. We also have our own internal consensus algos that pull multiple sources where possible and pick the most likely.

And hopefully this is an anecdotal data point for anyone, but we've been running a pretty performant system that services 200,000 ports, 50,000 airports, 50,000 crew, 5000 vessels and millions of miles of GeoJSON routes in real-time with Postgres alone. In my experience a well organised relational db can outrun most document stores, in most applications.

The only caveat I'd say (if there is one) is normalization as a hard rule. We denormalize some fields when we need to squeeze performance out of a commonly accessed metric (caching essentially, but through the db which I think makes it denormalization), and it's been quite helpful. Of course you need stronger checks and balances in code to make sure things don't desync, but it can be helpful to speed up large, common queries.

I'll link some of the technical write-ups of how we use Postgres and PostGIS below in [1] and [2], if anyone's interested.

[1] - https://hrishioa.github.io/large-geospatial-queries-and-opti... [2] - https://hrishioa.github.io/subqueries-and-ctes-an-example-of...

hrishi··on Launch HN: Greywing (YC W21) – Automated ship operations focused on crew
The most challenging aspect for us has been getting integrations with client software done and out of the way. Unlike other industries, the existing software around crew, reporting and planning are often in-house and in some disrepair, from a first-wave of digitization. This has pleasantly not been the case sometimes, but often we need to build the pipes ourselves - sometimes on both sides!

Our integrations range from SOAP, REST, FDW as well as push, pull, batch, and almost all combinations of these. Getting them done can also mean cleaning and consolidating the data we receive, so the users have a seamless experience.

Integrations can make a big difference in the UX as it stands, and our work the past few weeks have been focused on building graceful circuit breakers for our modules so that the the experience works as well as it can even without automated data.

Another one is definitely customization, but it's been rewarding for us. We've definitely had to customize the product to better suit the workflows of our customers. Maritime is a pretty heterogeneous place when it comes to details, but I think we're now at a point where most of the requests we get are already built into the product - customization is becoming just a matter of config.

The most rewarding aspect technically has been to watch new solutions emerge as a result of having a clean graph of data with well built relationships. There are a number of zero-to-one problems in maritime tech (routing, ports, events, etc) that I believe prevent new entrants into the space - much like ride-sharing would not be as easy without a good map element, GPS and cellular data.

Once those are solved, it's been rewarding to take unrelated requests from clients (around withholding or corporate tax, for example) and realize that you've got 99% of the tech needed to deliver a good solution.

From a business perspective, it's been a harder journey than we expected to get parts of the industry to open up about data or collaboration. It's significantly easier once you've built momentum, so it's also been rewarding to collaborate across stakeholders - from port agents and crewing unions to marine travel companies - as of late.

hrishi··on Launch HN: Greywing (YC W21) – Automated ship operations focused on crew
Thanks! Nick can chime in here once he's up - I'm the night owl (we're on SGT) and he's up in a few hours.

But the way I see it, most of the problems around piracy are systemic. I'll skip going into too much detail, but when economies are set up to benefit from a rise in pirate activity in their borders, you've created a loop that removes incentives to find a long-term solution.

The solutions have been exactly what you've suggested. One option for highly trafficked routes (like the Gulf of Aden) is to control a narrow part of the route well, so ships can use it. The IRTC[1] is a good example.

The other option is security. However, security may not always be possible. One reason is price (when we started Greywing, the per day cost of a security vessel sometimes exceed that of the tanker it was guarding!). The other is that security is still a volatile market, especially since suppliers always have to be located in the countries you're closest to. Security companies can pop in and out of existence, and the service is often a far cry from what you pay for.

There has been some work in the technology on the vessels - better training for the crew, better citadels, nonlethal deterrents, etc. However, these can only go so far when you're comparing the resolve of a pirate vessel to that of the crew on a tanker to survive.

From a software standpoint, routing makes a difference, but not as much as you might think. If a vessel needs to call at a port, there are often unavoidable routes that need to be taken. However, some of the early work we were doing focused on making sure that the captains and crew had a good idea of high and low alert days, as well as an idea of the mitigation measures to undertake to prepare for them.

Some of the products that were serving the security market when we started have since gone out of service, and I'm not personally aware of any yet that focus on operators, rather than nation-states and intelligence agencies. There's still open demand for services that focus on establishing trust and reputation around suppliers, aggregating good services, and enforcing due diligence.

This took me down a rabbit hole of our videos, but [2] is an example of what CRY4 looked like in the early days, when it was just piracy!

[1] - https://en.wikipedia.org/wiki/International_Recommended_Tran... [2] - https://vimeo.com/393361342

hrishi··on Launch HN: Greywing (YC W21) – Automated ship operations focused on crew
I meant we're not as good at simplifying the narrative, as we hope Greywing is at simplifying the task of vessel operations :)

We don't currently use any AI - we're yet to exhaust deterministic knowledge-based algorithms, but it might be something we look at in the future.

hrishi··on Launch HN: Greywing (YC W21) – Automated ship operations focused on crew
Completely agreed - and it's something we've had to work very hard at.

A rule of thumb that's worked for us is that the more information you show, the more tolerant your users are. However, that's also directly in opposition to the fact that the more information you show, the less user-friendly your product becomes.

Our approach has been to pyramid up the information we have. When we integrate a new source of data, we initially run customer engagement and have internal sanity checking algorithms to make sure we have a decent confidence about the data that we present. At this stage however, we give the user more information than less - so a full cost breakdown of a port call, instead of indicative total estimate, for example.

User engagement and testing will then help us understand which pieces are being used the most, and how we can best condense the data down in a way that best helps the user. This also gives us more time to refine our backend so that we have a higher degree of confidence about our methodology and results.

This often results in big changes - a twenty paragraph statement of restrictions may be condensed into a traffic light on whether a certain nationality is accepted into a port, or a fuel table may be condensed into a single estimate of cost based on estimated weight of the ship. This approach has worked well for us, and it might help in similar fields.

hrishi··on Launch HN: Greywing (YC W21) – Automated ship operations focused on crew
Thanks! It's a mixture of all of these things, to be honest. We had visibility into and in the industry due to our work with maritime security, as well as the benefit of being in an uncontested space (vessel operations intelligence) which was in crisis.

However, our first customers were inbound, from the demos we uploaded explaining how CRY4 could help with security and operations. So it's likely all of these things combined - we've worked to understand what drove initial adoption, but as we become more established we're seeing that these drivers shift into different things. What's driving leads today, I think may not be these things exactly.

hrishi··on Launch HN: Greywing (YC W21) – Automated ship operations focused on crew
None directly, but we believe improving crew well-being and providing more assistance to ensure vessels operate smoothly will have a long-term impact.

Ships can only function as well as the people on-board, but it's an often overlooked part of the industry.

hrishi··on Launch HN: Greywing (YC W21) – Automated ship operations focused on crew
Thanks! Our process has been client-driven from day one: we've got a good amount of technical and maritime expertise on our side, but it pales in comparison to the mountain of operational knowledge that our users have.

What this means is that all of our clients came on for the solution we were offering at the time, but each has had a strong impact on what the tools became, and what modules we've offered since then.

As an example, our first customer came on board for Covid-19 risk reporting (to improve communications with port authorities), fleet tracking and our routing tool. Under their direction, we released our port scanning tools and geofencing-related modules. Our second customer bought this product, and with their help we've been able to release (to name a few) a communications tool for port agents and flight tracking and heuristics.

This has been a good model for us: the benefit to us is an increasing price point for new customers as well as the ability to learn from parts of this process that wouldn't have known about otherwise, and the existing customers aren't charged for new modules and improvements.

hrishi··on Launch HN: Greywing (YC W21) – Automated ship operations focused on crew
We take all the information you (a ship manager) have about a vessel (route, plans, crew composition), with all the information externally available (piracy, flights, fuel costs), and tell you where to route your vessel and what the best choices are for the crew, and the purchases you're making.

Does that help? Happy to try again, it's a pretty complex piece of software that simplifies a complex job: unfortunately we're not as good as our software at simplifying the explanation.

hrishi··on Launch HN: Greywing (YC W21) – Automated ship operations focused on crew
I didn't know that either until I joined maritime! They are still very much a thing, and Nick could tell you stories forever - in some cases it's a well oiled machine, where the pirates know the insurance negotiators and vice versa.

It's also an unfortunate result of conditions today. If you look at some of our risk maps [1] you'll see that the hotspots are pretty consistent and predictable. Somalia, Nigeria, Malacca Strait, etc.

1 - https://grey-wing.com/intelligence-reporting

← PreviousPage 2 of 4Next →