HNHacker News
TopNewBestAskShowJobs

psahgal

270 karma · joined June 24, 2020

Senior software engineer for Blue Origin by day, game developer by night. Full stack engineer with experience in web, mobile, and backend systems. Based out of Chicago.

LinkedIn: https://www.linkedin.com/in/praneetsahgal/ Github: https://github.com/psahgal

More about Kin + Carta: https://www.kinandcarta.com/en-us/ More about Solar Command: https://solar-command.com/

submissionscomments
psahgal··on On Apple's Piss-Poor Documentation
I have been frustrated many times after stepping into a system function on iOS, only to be greeted with a mountain of assembly instructions. It was one of the first grievances I had with iOS development, coming from Android.

On the other hand, it's been a great opportunity to learn how ARM works!

psahgal··on On Apple's Piss-Poor Documentation
AWS's horrible documentation and user experience is the primary reason I prefer using Google Cloud Platform instead. :-)
psahgal··on On Apple's Piss-Poor Documentation
Even 5 years ago, I felt that Apple's documentation was way worse than Android's.

I wonder if there is a good way to measure documentation quality...I suspect such measures will require techniques borrowed from user experience research.

psahgal··on On Apple's Piss-Poor Documentation
I find this business decision fascinating because a good portion of their App Store revenue comes from developers. One would THINK developer relations would be a priority at Apple, but it's pretty clear that's not the case.

It was one of things that I found unbelievable when switching from Android to iOS development. The developer experience is just so much WORSE on iOS. Sometimes, it's as if Apple is actively trying to annoy developers.

psahgal··on On Apple's Piss-Poor Documentation
Based on the Android source code I've seen while working on Android projects, I think a good portion of the Android docs are generated by the inline documentation from the Android open-source project.

But on top of that, Google also produces high-quality long-form guides. Those are first-party guides, found at https://developer.android.com/. (Google maintains the Android developer site.)

psahgal··on On Apple's Piss-Poor Documentation
Has anyone else noticed that Apple has been slowly moving away from the long-form guides that were helpful at explaining core concepts? I remember once seeing a comprehensive guide on code signing, but over the years it appears to have been scrubbed from their documentation resources. In its place is a much less helpful (but prettier-looking) guide.

In comparison, I've noticed Android has FANTASTIC developer documentation. I've found full guides for everything. Even esoteric classes that are rarely used have at least a little bit of documentation.

psahgal··on Lobe.ai – A simple tool for training machine learning models
Thanks for the details! It's good to know this is an option for projects that require a custom image recognition solution. I have a feeling my company's clients will appreciate being able to train their data privately on their own computer.
psahgal··on Lobe.ai – A simple tool for training machine learning models
This looks really similar to Google AutoML! I wonder if there are any advantages to switching.

More info on AutoML: https://cloud.google.com/automl

psahgal··on Missing Covid-19 test data was caused by the ill-thought-out use of Excel
I would hope that any decent data engineer would know not to do this. Are there avenues for fully-employed engineers to help governments build these systems properly? I'd honestly be happy to just donate some of my free time to help these efforts.
psahgal··on Ask HN: Natural language processing to identify grammar in a text?
Have you taken a look at Google's Natural Language API? Try out the demo and switch to the "Syntax" tab to see the output. More info: https://cloud.google.com/natural-language
psahgal··on Ask HN: How to take notes?
I made it a point to take detailed notes for all of my lectures in college, and I did pretty well in my courses as a result! So here's some advice.

Consider taking notes by hand instead of using a computer. I found one study from some time ago that suggested handwritten notes are better: https://journals.sagepub.com/doi/abs/10.1177/095679761452458... I personally find taking notes by hand better for me. Since I can't find any studies replicating the result of the one I cited, I suggest trying it out and see if it helps!

When I was taking notes for class lectures, I would split sections of notes by date, titling subsections in a given day as appropriate. This sort of chunking will help you remember the notes better, rather than writing in one continuous stream. If you're taking online courses to learn some programming languages, I think this method will work! If not, I would suggest keeping a notebook per programming language and just organize your notes by day.

When taking notes, you do NOT want to copy what's on screen or what's being talked about verbatim. You want to capture just the highlights, so that they'll jog your memory later. I generally write tons of bullet points instead of complete sentences, and I end up with more of an outline at the end than paragraphs of information. If you need the finer details, it's better to go back and review the source material itself.

Once you have your notes, you can review them by going day-by-day. For your case, if you need to refer to previous sections quickly, consider bookmarking them with sticky notes. (Not sure how you would do this digitally.) You might be surprised to find that the act of writing down the notes was enough to keep them in your head, and you may not actually need to review your notes often.

Hope this helps!

psahgal··on Ask HN: How to avoid over-engineering software design for future use cases?
I totally understand the sentiment of writing elegant code that lasts forever, but I think developers need to manage their expectations a little better.

If you're writing foundational code for an operating system, then yeah, whatever you write is going to stick around for a while. (Which means you need to be a LOT more careful about what you write.)

If you're writing code for a mobile app or website, expect your code to get thrown out in a few months due to shifting requirements. I'm sure the Facebook app has been completely rewritten more than once, since they switched to React Native at one point.

If you're writing a JavaScript library, expect your code to be replaced next week. :D

psahgal··on Ask HN: How to avoid over-engineering software design for future use cases?
Test-driven development is a useful tool, but it doesn't remove the need for manual testing completely, especially on frontend projects.

I've worked on mobile apps before with a small team, and inevitably, we'll find bugs that show up in the user interface when the user rotates their phone. It's hard to unit test for rotation changes, and it's also hard to code a rotation change into an end-to-end test on mobile. Animations are also something that's difficult to test in an automated fashion, and all the testing in the world won't be as good as showing the animation in front of a designer. So some level of manual testing is needed on mobile.

I've worked on web frontends where there would be bugs with scrolling jumping back and forth. An end-to-end test using Selenium may not catch the issue, but for a user, it can be painfully obvious. Similarly, animations are also hard to unit test on the web. So some level of manual testing is needed on the web.

The only place where I could see manual testing NOT being needed is for backend development, since the input and output to a backend system is much more controlled. You could write an end-to-end test for any scenario a user could throw at your system.

In summary, don't underestimate the value of manual QA!

← PreviousPage 2 of 2