jph

85 ms·

871.
by jph 9y ago
If you want to help, here's the social network plan that has many comments thanks to HN folks: https://github.com/joelparkerhenderson/social_network_plan Comments welcome here or on GitHub or email me joel@joelpar
872.
Can Facebook be replaced? Let’s invest $100,000(calacanis.com)
51 points by jph 9y ago|51 comments
873.
by jph 9y ago
If you want to help with a social network plan for social good, please add your advice here: https://github.com/joelparkerhenderson/social_network_plan
874.
Facebook is a tyranny – and our government isn't built to stop it(theguardian.com)
4 points by jph 9y ago|1 comments
875.
by jph 9y ago
Thanks! I am adding these to the repo now.
876.
Social network plan – request for comments(github.com)
3 points by jph 9y ago|0 comments
877.
by jph 9y ago
> Are you trying to create yet another open social network like Mastodon? No because Mastodon is solely a decentralized network and is self-described as for microblogging. My research interest includes possibilities for centralized netwo
878.
by jph 9y ago
Many tech people want a better social network plan. I'm asking for opinions and advice here: https://github.com/joelparkerhenderson/social_network_plan The repo looks at issues of purpose, funding, audience, ident
879.
by jph 9y ago
Berkeley and the UC schools are making major strides in online education, including edX participation and on-campus projects. If you're interested in Berkeley and data science, there's an online masters program too. (Disclosure: B
880.
by jph 9y ago
Summary of GitHub special files and paths: README LICENSING CONTRIBUTING CODE_OF_CONDUCT etc. /.github /docs /ISSUE_TEMPLATE /PULL_REQUEST_TEMPLATE etc.
881.
Show HN: GitHub special files and paths (README, LICENSE, .github, /docs, etc.)(github.com)
6 points by jph 9y ago|2 comments
882.
by jph 9y ago
Seed deck notes that complement the YC info: https://github.com/joelparkerhenderson/pitch_deck
883.
by jph 9y ago
You're welcome. You're correct the 6-slide pitch deck doesn't have a "team" slide. It's deliberate. This is because it's higher priority to focus on the product and customer; the concept is still touched o
884.
by jph 9y ago
Pitch deck notes I use with clients: https://github.com/joelparkerhenderson/pitch_deck IMHO the Stripe notes and YC perspectives are especially useful when the pitch deck has a first draft. Founders and teams write the
885.
by jph 9y ago
This is amazing for shells. Thank you for writing it. Your reasoning and explanations are first rate, and the documentation is superb. Your emphasis on POSIX is a great approach for working on a very wide variety of shells, including olde
886.
by jph 9y ago
> If you ever had to make it faster, or make it work better on different hardware, you'd be starting from scratch again. Optimizations like these a great area for tests because the test files can keep all the various implementations
887.
by jph 9y ago
Fair points. A. When I encounter areas that need specialized workarounds (such as a mitigation for a security vuln) then I advocate using two methods: one of the normal condition and one for the specialized workaround. Same reasons as above
888.
by jph 9y ago
Turns out this is a great example of why tests are better than documentation. One way to implement this is by using two methods: one normal and one with the hardware mitigation code, with a dispatch that chooses between them. This separatio
889.
by jph 9y ago
My opinion is that test names, function names, variable names, constant names, high level languages, literate programming, and well written commit messages, all help code to be understandable; I'm fully in favor of all using all these
890.
by jph 9y ago
For example, here's one way to write a test that sufficiently explains "gets within a certain error margin of the correct answer yet is much much faster than the naive way". Using Ruby and its built-in minitest gem: 1. Write
891.
by jph 9y ago
> Some might claim unit tests will solve this Yes. Tests will solve this. Your point is perfect for tests. If another experienced coder cannot comprehend from the tests why something is wrong, then improve the tests. Use any mix of liter
892.
by jph 9y ago
If you can imagine each interview as a good way to learn about the people at the company, and also about the company's processes, then you can triage as you wish. As an example you could ask openly about the company's hiring proce
893.
by jph 9y ago
Coordinated disclosure information is here, and edits/suggestions/feedback are welcome: http://github.com/joelparkerhenderson/coordinated_disclosure
894.
by jph 9y ago
Congratulations and thank you. If you want to see concrete progress thanks to Dustin and Open Phil, read about Target Malaria, one of the research organizations. I am seeing firsthand the need in Southeast Asia: an emerging drug-resistant &
895.
by jph 9y ago
Test Driven Development (TDD) gets a huge improvement with the new coverage capabilities for methods and branches. Thanks Ruby team!
896.
by jph 9y ago
Coordinated Disclosure is a helpful way for users and security researchers to tell companies and software authors about potential security bugs. Today's example of Apple and the macOS High Sierra root security issue is a prime example.
897.
Coordinated Disclosure – how Apple can handle security bugs better(github.com)
1 points by jph 9y ago|1 comments
898.
by jph 9y ago
Coordinated Disclosure notes are here: https://github.com/joelparkerhenderson/coordinated_disclosur... (Note: Coordinated Disclosure is the newer term for what had been called Responsible Disclosure)
899.
by jph 9y ago
LISP. Recursive Functions of Symbolic Expressions Their Computation by Machine by John McCarthy at MIT. https://aiplaybook.a16z.com/reference-material/mccarthy-1960... "Introduction: A programming system called LI
900.
by jph 9y ago
I think you may be misunderstanding the core point. Linus describes two choices: 1) add warnings now to give developers a year to fix security issues, then add panic 2) skip warnings, add panic now, and start crashing everything for all use

More ›