HNHacker News
TopNewBestAskShowJobs

atmartins

146 karma · joined December 3, 2016

submissionscomments
atmartins··on [dead]
Are you saying that people are offended easily, and accredit too many things to "hate", so then everything called hate is just people taking offense, and is not actually hateful?

What if someone calls a young black girl the n word and nobody got offended. Is it not still hate? What's the intention of saying that? To demean or intimidate? That's hateful (abusive, mean, bullying, whatever you want to call it) and I wouldn't tolerate it if I witnessed it.

I hope you consider opening your heart up a little more when thinking about something like this. There are lots of nice people out there who get treated like crap and we can do better as apes on this rock.

atmartins··on Fitbit's 150B hours of heart data
I care because if companies can collect enough data to recognize patterns, and generalize those findings, it becomes everyone's problem. You don't think health insurance providers are dying to buy this data? Or drug manufacturers? You're being double sold and generalized.

For instance maybe insurance rates increase in a region showing a higher percentage of heart palpitations. I live there and now my rates increased even though I don't even own a bitfit.

atmartins··on Data Structures Reference
Have you ever worked with arrogant ones?
atmartins··on Inventor says Google is patenting work he put in the public domain
Can you elaborate on why this is advantageous to the situation in the article?
atmartins··on Cheap 3D-printed home is a start for the 1B who lack shelter
This is possibly a valid point but where are those numbers coming from? Citations please.
atmartins··on Collection of Useful CSS Snippets
Truncate text has a huge caveat in that it doesn't work fully for multi line text.
atmartins··on Let’s have no managers, instead of managers with no engineering experience
This is a valid point. In my mind, ideally, at least one or two trusted members on the team can help with this since they're even closer to the actual engineering taking place. It's helpful for management to understand the tradeoffs that are discussed, so I agree that some experience is very helpful, but hopefully the team has a few mature members as well.
atmartins··on JSON Schema
JSON schema can be the representation used to exchange information between two or more systems, languages, projects, etc. It's a form of lowest common denominator, something that can (somewhat) fully describe your interface but in a static, commonly available, easily parsed, easily generated way.
atmartins··on Npm operational incident, 6 Jan 2018
Not sure how that's relevant.
atmartins··on Ideal OS: Rebooting the Desktop Operating System
I'm surprised at all the negative, pessimistic views about looking forward with operating systems. I welcome conversations about what things could be like in the future. Obviously Google's pondering this with Fuchsia. Maybe it will take a more vertical approach, where only certain hardware could take advantage of some features for a while.
atmartins··on Angular 4.3 Now Available
But you don't have to import something if you don't intend on using it. They're baked in conceptually, so there's more coherence, but the deployment payload doesn't have to be unnecessarily large.
atmartins··on Apple’s culture of secrecy wore down Swift creator and Xcode lead Chris Lattner
How is speculating not equal to fake?
atmartins··on Ask HN: Does anyone here have an art degree?
This is like a clone of the comment I was about to write. I also had classes from that fellow, and share your sentiments almost exactly.
atmartins··on A one-side-project-per-month challenge
Man I'm glad you're not making business decisions for my company...
atmartins··on Things I learnt making a fast website
Yeah but if it takes 6 months longer, and is 30% harder to refactor, it doesn't matter. You're not selling anything when it's not running.
atmartins··on GraphQL is the King, R-I-P Rest
I appreciate the answer. It looks like I do want to create a rule for each property. Why? Why not create meaningful objects and not micro-manage individual properties? In case I want to update my front end query in the future? Shouldn't I just make my objects more granular, rather than this extreme of managing individual properties? I'm genuinely interested from an architectural standpoint what the real gain is here, it really seems like there are major portions of a useful api that are not discussed when I've looked in to GraphQL.
atmartins··on GraphQL is the King, R-I-P Rest
What about permissions? What if the logged in user is only allowed to see certain fields? Do I make a table that describes every possible field and which roles can access it? How do I know what's available to query, without reading docs? What about hypermedia? Do I have to gain knowledge about a large system's data structure to query it?
← PreviousPage 2 of 2