71–80 of 175 posts
Some interesting salary stats here, was surprised to see Seattle stand out with an average salary adjusted to the cost of living.
Every Programmer Should Know LISP
I hope this list stays brief. Every list so far I observed was eventually bloated to hundreds of items (useful or not) by helpful pull requests.
There are loads of people who don't actually know how to efficiently cut the loin from a pig, tack against the wind, or ensure proper close air support while bringing even a few thousand soldiers into territory held by an enemy force... But who still post that Heinline monologue about how specialization is for insects.
I might not know how to butcher a pig, but I know multiple programming languages, multiple human languages, I ski, I climb, I skate, I ride bikes. I can cook foods from cuisines from all over the world. I read books on things I haven't formally studied.
Life is just more interesting if you're not a one trick insect.
Earlier quoted context omitted.
>I still struggle to always get this right. I really like the FHIR Human Name data type[0]. It requires none of the fields... so it can represent someone without a name. It also has all the necessary fields for representing someone's name and their name in various forms and pretty much as many edge cases as possible. The only problem is turning it into a UI that makes sense. [0]: https://www.hl7.org/fhir/datatypes.ht…
May I ask where you work that you work with FHIR?
I don't do anything "real" with FHIR at my company, I just borrow concepts because FHIR does a pretty good job at encapsulating the healthcare domain.
http://jimkeener.com/pdfs/aptb-book-toc-44e1b61.pdf is the current table of contents. It feels a little disheveled in places. I'm still working out some of the structure, but I'd say 95% of the final sections are there, and maybe 85% are in the correct relative positions (at least in part 1). I'm also going to be trying the following parts mirror part 1 in structure as much as possible.
Right now it's a GFDL license, but it's not yet public. I'm still debating if there is a better libre license, but one that would allow it to be physically published as well.
This is what every programmer should know: 1. Life is too short, so get a life. 2. Know that you don't know everything, so get don't arrogant. 3. Don't get caught up in the various programming "religious" wars, there's more to life than a specific point of view. 4. Laugh and enjoy the the wonderful beauty in the world around us. 5. You're as much the idiot as the person you consider an idiot. 6. Sometimes the "import…
I find that saying the phrase "get a life" to people that enjoy what they are doing is extremely condescending. If I enjoy programming all day, or having huge flame wars, or maintaining a huge collection of antique watering cans sorted by volume, then who are you to judge me for that?
I'm a free software hacker and activist. I'm also a professional programmer. My life outside of work is how I described myself in the first sentence of this paragraph, and I'm unhappy with how _little_ time I have to devote to it. These are things that are fundamental to my identity, so saying "get a life" when talking about what makes me me is telling me that the life I chose isn't one worthy of choosing.
Again, I'm not confident that this was the oldandtired's intent with those comments, but I think there's an important perspective to consider. The username is also suggestive. :)
This is what every programmer should know: 1. Life is too short, so get a life. 2. Know that you don't know everything, so get don't arrogant. 3. Don't get caught up in the various programming "religious" wars, there's more to life than a specific point of view. 4. Laugh and enjoy the the wonderful beauty in the world around us. 5. You're as much the idiot as the person you consider an idiot. 6. Sometimes the "import…
Earlier quoted context omitted.
I find that learning how to work with list is like having a crescent wrench in your tool box. Not every tool box have one but I sure think they should. If you don't know list you won't know when that is the right solution. I have seen many people just use a SQLite DB for something as simple as a 20 item list.
Yep, I guess you really didnt read that article :D The List in the title is not the datatype ...
Earlier quoted context omitted.
If this is how it was meant, perhaps a different phrase would have conveyed OPs opinion better. For me, "get a life" is strongly associated with "douchey jock" behaviour, bullying, nerd-shaming (is that word a thing? it is now) and phrases like "you like math? what a nerd, get a girlfriend bro", things I'm sure many people on HN have had to deal with.
When I'm reading HN I assume the commenters are at least somewhat similar to myself until I have evidence to think otherwise. The culture here is neither anti-intellectual nor anti-math. Given that we're on HN I'd say it's safe to assume no one is telling you to quit coding or stop caring about math. On this forum issues around workaholism and burn out come up all the time, "getting a life" is a step toward not burni…
I'm not saying that is the intended reading here. Nor, that such a reading is charitable.
One of the things I assume when I writing on HN is that I can go back an edit what I wrote to make it better. "Don't forget to live life," might better express the idea. Finishing with "Get a life" after showing the overall intent might better express the sentiment.
Leading with "Get a life" means the reader reads with only their existing context and can reasonably apply standard connotation. It is normally a bullying phrase, and an author ought to expect it to be taken as such without doing a lot of additional work. It is no surprise that it puts people off.
Suppose the author's response to people being put off by the advice "get a life," is something like "well, that's their problem." That's exactly the connotation of dehumanization "get a life" has in US culture and a charitable reading is unwarranted.