HNHacker News
TopNewBestAskShowJobs

goo

422 karma · joined February 17, 2011

submissionscomments
goo··on The software engineering notebook
I think that's a really valuable mental tool. Sometimes past baggage is a hindrance to current goals.

As part of treating my notes as a code project, I even keep them version controlled, which leaves me a little more free to just delete things or "refactor" stuff. A lot of the value I get is going back through things and synthesizing them into clearer and more useful notes. TODOs in particular are dangerous -- I try to treat files of that nature as extensions of my long term memory, rather than a curriculum which I feel obligated to follow.

That being said, there is an element of this project where I feel like a am building a piece of "my life's work". I've built a number of software projects, and part of building them over time and organizing them leaves them in a state where I am proud to have built them -- I can point out a piece of the system, and understand why it works that way, and remember the choices that led to its current state. At one point, I realized that I had no such project for my life, and it was a little weird that I had so clearly documented software systems that were hardly used, whereas my life and action and ideas and knowledge were, for the most part, just in my head. So in a way it's more than the practicality of having notes, although in the practice of it I have found it to be practical. It's a way of adding meaning to the course of my life -- now the ten minutes I spent reading an article can also become a gift to my future self due to the one choice quote I grab from it.

goo··on The software engineering notebook
Great question... some files are very read heavy (e.g traits.txt, which is a collection of about 25 traits phrased as imperatives that I aim to accomplish, such as: "

BUILD QUALITY RELATIONSHIPS - improve existing relationships, and seek out new good ones

MAINTAIN NEUTRALITY - approach things with a beginners mind

PRACTICE SELF-COMPASSION - admit pain, take kind and mindful action ")

Some files are just used a lot for both reading and writing. These include a todo.txt, event_planning.txt for planning logistics of whatever fun getaway or event I'm doing next, a shopping_queue.txt (reduce impulse buys by requiring I put things on that list for some amount of time).

I find that for taking notes on books or presentations, I will write them once, and then refer back to them infrequently -- maybe once a year. A bigger advantage is gained because it makes it easier to stop reading/watching things, because then I can always pick it up again and review the notes associated with it, so I can have a lot of educational threads going at the same time without fear of losing the context.

For journaling, I tend to review my journal and list of activities as a whole a couple of times a year, and typically will review the last week every week or so.

Much of this happens naturally due to the fact that the project is open -- it's often easier and more interesting to review my past work week or pick up where I left off on a book (stored as a pdf within the notes) than it is to jump onto facebook or whatever.

goo··on The software engineering notebook
Many notes are easily organized -- when I take notes on books I am reading, for example, there is pretty natural connection to where the not should live (e.g. /education/books/design_of_everyday_things.txt)

Otherwise, since these notes in the context of a project, I can treat it the same way I treat code. So a mix of multi-file search, and directories that correspond to the knowledge in them (e.g. "finances/investing.txt" or "journal/happiness_project.txt", the latter containing any work I do on http://diurnal.st/2013/05/27/training-your-brain-to-be-and-s... -- which I don't do everyday by any means, but that's an example of the kind of thing that exists in my notes)

goo··on The software engineering notebook
The commitment to taking good notes has been one of the best decisions of my life -- not just professionally. I use my standard text editor (Textmate 2), and have a "notes" project, with all manner of categories organized by folder. I take notes on articles I have read, take notes on any presentations I watch or educational courses I take, or books I read. Moreover, I now take much better in person notes -- I take them into "scratchpads" and then synthesize them later.

It's indispensable in meetings because I both take notes about the goals of meetings beforehand, take note of any important parts during them, and am able to succinctly review them afterwards as they relate to the original goals, and easily keep track of any action items.

I manage EVERYTHING this way now-- what I am currently working on, notes about what I've done in a day, notes about what I've done on the weekend, notes about books I want to read, movies I want to watch, have watched, fitness routines. It goes on.

At first it was a small but useful knowledge base, and a good plan for how to keep track of things better. Now it's a larger, and even more useful knowledge base, where due to review and organization the important concepts in it have mostly made its way into my long term memory. And the process of taking and using the notes has become a smooth and well-honed process. I keep the notes in dropbox so I have easy access to them on mobile also.

In short: I treat my personal knowledge base as if it were a coding project: using well organized text files. I am constantly adding to them and maintaining them. It is working very well for me.

goo··on Is it possible to host Facebook on AWS?
To be clear: reactjs uses the 3 Clause BSD license. https://github.com/facebook/react/blob/master/LICENSE

It's incredibly permissive (nearly the same as the MIT license), and does not allow for the concept of having it "revoked".

goo··on Drinking While Jurying
I know how excited we all are to board the moral outrage train, but there's an actual answer to that: http://www.vox.com/conversations/2017/1/19/14266230/empathy-...
goo··on Ask HN: How do you take notes (useful note-taking strategies)?
I experimented for a while until I found my favorite solution, which I'm really quite thrilled about.

I treat my notes as if they were a software project, which is to say, a collection of text files organized according to domain-specific methods. I use a code editor to write and edit notes (Textmate in my case) -- this has the bonus of not just using my familiarity with my code editor, but it actually adds to the value of improving my skills with the code editor, since that makes me better at notes and at code.

I keep two projects -- "life" notes and "work" notes. They are stored in Dropbox (and are additionally put in version control, although I commit changes rarely). Storing them in dropbox makes them all accessible on my mobile phone, which is nice.

In the root directory of my "life" notes, I have:

a few scratchpad_{identifier}.txt files (alpha, beta, etc.) -- so I always have an easy file to jump to to take notes on anything. I then synthesize these notes into a more useful location.

todo.txt -- a todo list schedule.txt -- notes on my schedule (typically to aid planning things a few weeks ahead, not a replacement for a calendar app) goals.txt -- keep my life goals front and center

and then directories, which included .txt files related to their title, or further subdirectories:

career culture (notes on articles) finances identification (keep track of useful info like VIN #) journal knowledge (non-career related learning) lifestyle (hobby-related notes, fun ideas) media_lists (books to read, books read, movies (watched/to watch), podcasts, etc.) projects (personal software project notes, ideas, before they deserve their own repo) travel self_improvement writing

Like a software project, I sometimes "refactor" the notes; the goal being to improve the ease of storing and the value of retrieval of the notes -- as a bonus, going through the notes refreshes valuable information for me.

My work notes are organized in a similar manner, but related to work things.

It's an awesome workflow -- almost everything I write starts in a scratchpad, and either gets migrated and synthesized elsewhere, or (like code) deleted if not worth maintaining.

After a lot of exploring solutions, returning to the core concept of files in folders and a text editor has been a perfect fit for me -- I never used to be big on notes, now I relish it.

goo··on [dead]
Looks to me like literally yes and HN mods should probably look into the voting ring that upvoted it to the front page.
goo··on [dead]
This is a great example of what Paul Graham calls a "submarine", (I think nowadays the common term is "content marketing"?).

Here's the 2005 essay: http://www.paulgraham.com/submarine.html

goo··on Ask HN: Lessons you wish you knew when you were Junior developer?
I'm not suggesting that C+P is magic, or a tool that should not be used. Understanding how and why C+P isn't really important. Being careful to only copy tokens or lines that don't introduce bugs (or making sure to modify those lines once you've copied them) IS really important. It's one of the more common ways to accidentally write bad code, and although of course I (like everyone) use C+P as a tool too, I think it is valuable to be aware of the increased risk. It's like driving. You're gonna drive, or someone on your team is, but it's one of the highest likelihood activities for accidental death.
goo··on Ask HN: Lessons you wish you knew when you were Junior developer?
Here is some insight that has helped me, some my own advice, some paraphrased from other sources, and I credit the source when I have it in my notes:

- There is no "silver bullet" for managing the complexity of user needs. Instead, (good) software is characterized by not a static state of "solving the problem", but a continuous refinement-- an existential struggle against incidental complexity.

- Have a very positive mindset, and inspire the same in your team.

- highly reliable websites for small companies: http://www.kalzumeus.com/2010/04/20/building-highly-reliable...

- Learn your debugging tools well: Get good at Chrome Debugging tools, pdb, visual studios debugger, or whatever the debugging environment is for your project.

- “… never consider your education complete or your opinion above questioning regardless of your title, your years of experience, your awards and accomplishments, or anything else that isn’t rational argumentation or evidence. Retaining a healthy degree of humility, constantly striving for improvement, and valuing objective metrics above subjective considerations will go a long way ..." (http://www.daedtech.com/how-software-groups-rot-legacy-of-th...)

- This is a marathon, not a sprint.

- Practical engineering advice: https://www.quora.com/What-are-the-best-kept-secrets-of-grea...

- Read books. I can especially recommend Refactoring by Martin Fowler and The Pragmatic Programmer as a more introductory text (affiliate links: http://amzn.to/2ekPnTL and http://amzn.to/2ekJQMK). Understanding why and how to do scrum effectively is really important too -- I waited too long to read a book that laid that out for me (http://amzn.to/2ekPxul)

- Good programming advice from Kent Beck: https://www.facebook.com/notes/kent-beck/mastering-programmi...

- Eventually, you will have to choose between engineering management and continuing to be close to technology. Trying to do both is a recipe for burnout. Some people might be able to do both simultaneously without trouble, but you're probably not one of them.

- Always be looking for ways to remove yourself as a bottleneck. This needs to be done both on a technical level and on an organizational level.

- Push back as necessary against demands of your time and energy that are not in harmony with your needs as a technologist.

- Good programming comes from good habits. (in that vein: copy-and-paste is the devil.)

- Seriously, read books. It's incredible how much good advice is out there.

goo··on Ask HN: What good open source projects written in React that I can learn from?
https://github.com/callemall/material-ui is a great collection of components -- there's perhaps some insight into how to make (and document!) reusable components, since the project is built to be a component library for others' use
goo··on Ask HN: Weekend wasted again
Side projects are hard to get around to sometimes -- I don't try to force it, because it's much worse to waste your time and build bad habits than it is to just admit that it's not happening today and make the most of your time.

I try to get outside and move every day that I can. I surf on weekends and it makes my life a lot better. Then the day is already in the "win" category, so if I feel like working on something, there's less pressure.

goo··on Ask HN: Who is hiring? (September 2016)
Zoomforth (https://zoomforth.com) | Full Stack Engineer | San Francisco or REMOTE | Full-time

Hey HN readers!

We're looking for a talented engineer to join us in building a communications product for salespeople, recruiters, and marketers. We have a stable and growing base of customers. We're unlocking some real opportunity with this, and we need help.

We make it possible for companies to build websites that serve as resources in their conversations with people -- "Squarespace for business teams".

For example, in our sales use case, the company may build a "pricing sheet" page. The salesperson can send that link out, and when their prospects arrive on the page, their activity is tracked, and we can send notifications back to the sender.

From an engineering perspective, examples of product challenges we wrestle with are as follows:

- improving the flexibility and intuitiveness of our page creation process - storing and serving multimedia assets on behalf of our customers (including video) - tracking and reporting on the behavior of our customers' page visitors - defining and addressing specific user personas and their permissions

The technology tools we use to build our site include AWS, Python (Pyramids, Celery), Backbone.js, React.js, LESS, and others.

For collaboration and workflow we use Vagrant, Gulp, CircleCI, Slack, Email, Asana, and other tools as needed.

You would be our 3rd engineer, so you would have a big effect on both the engineering culture and the product we make.

We are committed to making or company somewhere that supports remote employees -- if you've worked effectively as a remote employee (or perhaps run a small team of them), that's a plus. Right now, only our designer is remote, and we want to build on that.

If this sounds exciting to you, please apply at https://goo.gl/forms/GTyISOOjTJhSoUMj1

Thanks!

goo··on Revisited: Alan Watts, “This Is It”
I always laugh at myself a bit when I make purchases toward the goal of improving my consciousness and embracing my spirit. I see in myself the American consumer idea that if I buy the book, I will gain the knowledge.

Enlightenment! Now 50% off at Amazon.com!

Usually I don't regret the purchase, though...

goo··on Canada to introduce legislation to legalize recreational cannabis
I've never learned what contrapositive meant. Thank you for your casual use of it -- it inspired me to learn the concept. What a useful word!

The contrapositive in this case being: "Not being cool means you do not smoke pot", which as you explain seems like a reasonable assertion.

goo··on Ask HN: How did you learn about stocks and the market?
In the course of investing and reading about investing sometimes I stumble upon what I think of as particular well distilled pieces of insight. I keep a file of these in my notes. Here are a few of my favorite concepts, quoted from others:

“It all comes down to who is going to buy and who is going to sell and for what reasons,” -- Ray Dalio

Determine whether an investment opportunity is a Yes, No, or Too Hard: If you do not understand it after brief study…it’s Too Hard. If you do not love it shortly after that, it is a No. -- Warren Buffet, paraphrased

"The market is like a large movie theatre with a small door” - N. N. Taleb

goo··on Building Large Flask Apps in the Real World
It's a matter of conceptual load, not about the actual capabilities. By "putting the ball in your court" I mean to say that flask adds an insignificant amount of conceptual load, and the overall difficulty to read and understand your app will be based on what you decide to add beyond flask.

By saying "it's not a particularly opinionated framework", I mean to say that it allows you to add, easily, whatever you want to it. However, there is a fair amount of conceptual load in doing so. The difference between a flask app and a pyramid app with pyramid jinja2 built in is that one of them takes about 20 seconds to understand.

Don't get me wrong -- I think pyramid is fantastic. But it it is disingenuous to suggest that there are not differences in complexity between the two frameworks.

goo··on Building Large Flask Apps in the Real World
I've worked on one project with Pyramid extensively, and I've been relatively pleased. It gives you a lot of flexibility, which can be good and bad. There is useful code that helps you unit test your app, and it is not a particularly opinionated framework. That being said, the number of options that pyramids allows can be a little overwhelming -- it gets a grade 'C-" when held up to the zen of python's line: "There should be one-- and preferably only one --obvious way to do it." When held up to "Although practicality beats purity.", as well as most of the rest of the pythonic ideals, Pyramids gets a solid A.

Personally, I'm excited to explore flask more, since it seems to put the ball entirely in your court. I like the concept behind flask a lot -- for some projects I'm willing to sacrifice additional framework features in exchange for a more careful understanding of everything I am adding to my app.

goo··on Coding Interview Tips
I have observed a general frustration that good developers (who are in high demand) still need to do well in an interview setting. Frustrating as it may be, I think that embracing the reality is the best path forward.

A good developer would be smart to realize that this is a part of the project of finding a great new job, and would apply themselves fully to the subtask of preparing for and succeeding at an interview.

I think that, in the same way it is a necessary frustration to make sure the site performs well on IE8, a good developer recognizes the task as essential, and does what is necessary despite the perceived lack of significance.

Of course there is a limit to this lack of significance -- I am not advocating that people become professional interview-ees. But embracing the frustrations of a profession can give you a huge edge over those who don't.

If I were to be seeking employment right now, my first step would absolutely be to sign up for resources like this one, and dedicate a couple hours a day to honing my interview skills. It would be fun, and would develop a skill that opens a lot of doors.

goo··on The Cool Front-End Developer
This made me laugh hard enough to actually write it:

http://gurukhalsa.me/2015/the-mediocre-front-end-developer/

goo··on Ask HN: How much are full stack developers worth?
You could make more -- how much you make depends on what the market will bear, and the more sales savvy you have, the higher price you'll get for your product (you!).

The only way to know how much more you could make is to find out -- salary markets vary substantially between regions, so a developer making 140k in the bay area may struggle to find a job paying more than 80k in TN.

Salaries are a result of a negotiation with the organization at hand, and one of the key elements to a successful negotiation is to be both providing more value than you cost to that organization, and to have the ability to walk away from the table. Your best alternative, which gives you that power, is the most important element of a negotiation. Read up on BATNA: http://en.wikipedia.org/wiki/Best_alternative_to_a_negotiate...

Also keep _their_ BATNA in mind -- if they don't have anyone who can replace you, and it's making a bunch of money, then they have a poor position to negotiate from, and you can get more from them.

goo··on Thunderstrike – Apple EFI firmware vulnerability
I often come to the comment section looking for a summary of a dense article like this. Didn't find it, so here is my best shot at one:

Through the thunderbolt port, an attacker can put code that controls the firmware updates onto a mac. This cannot be removed by software, and could do all sorts of nasty stuff.

Anyone with physical access to the computer and a weaponized version of this exploit could do this. This includes intercepting hardware en-route to its recipients, spending a few minutes with a laptop while its owners are away, or while crossing international borders.

According to the author, this exploit works with every Mac with a thunderbolt port that they tested. Apple has a partial fix coming as a firmware update soon, but the author expresses concern that the proposed fix could still be bypassed.

goo··on How the 49ers Are Using Beacons to Help You Find Hot Dogs and Beer
Now if only they could use them to find the endzone...
goo··on The Intelligent Life of the City Raccoon
A raccoon recently snuck into my apartment in the middle of the Mission in SF, and rampaged around the place in the middle of the night, ripping through bread and leaving a huge mess. My roommate told me that he chased it back out the window with a broom.

I was totally shocked, and thought that it must have been a one in a million event. Of course, it happened again.

I would say it was a nice taste of the wild in the middle of the city, but sweeping up the mess and wiping down all the paw prints was a huge pain. Nature never ceases to impress.

goo··on Ask HN: Who is hiring? (July 2014)
Software Engineer at Zoomforth.com -- San Francisco, CA - Full Time, Local

We're building technology to make it easy for non-technical people to make multimedia-enhanced business messaging. There are lots of people whose impact is much greater with the ability to build messaging that includes photos and video, for sales, recruiting, or leadership, and we're striving to build the best product we can in that space.

We've got our foot in the door at several enterprise companies, and have closed a few larger deals. Our product is evolving -- there's a lot still to be imagined and built, in addition to the clear stepping stones to bigger sales with new enterprise clients.

We're looking to bring on our first engineering hire. We use Python+Pyramids as our framework, with a great deal of javascript including backbone.js and jQuery. Our persistence layer includes mysql and elastic search on top of AWS.

We're hiring experienced developers at either full-stack or front-end positions. We are passionate about making good software, and bringing an experience to our users that they love. If you think you can help us build that, apply via email at engineering+hn(at)zoomforth(dot)com Check us out at https://zoomforth.com/about.

What can we offer?

A competitive salary, full medical coverage, a flexible environment where we actually care about not burning people out, and a commitment from us to help you reach the top of your game, whatever that means for you.

goo··on Ask HN: Who is hiring? (June 2014)
Software Engineer at Zoomforth.com -- San Francisco, CA - Full Time, Remote OK

We're building technology to make it easy for non-technical people to make multimedia-enhanced business messaging. There are lots of people whose impact is much greater with the ability to build messaging that includes photos and video, for sales, recruiting, or leadership, and we're striving to build the best product we can in that space.

We've got our foot in the door at several enterprise companies, and have closed a few larger deals. Our product is evolving -- there's a lot still to be imagined and built, in addition to the clear stepping stones to bigger sales with new enterprise clients.

We're looking to bring on our first engineering hire. We use Python+Pyramids as our framework, with a great deal of javascript including backbone.js and jQuery. Our persistence layer includes mysql and elastic search on top of AWS.

We're hiring junior and senior developers at either full-stack or front-end positions. We are passionate about making good software, and bringing an experience to our users that they love. If you think you can help us build that, apply via email at info(at)zoomforth(dot)com

Check us out at https://zoomforth.com/about.

What can we offer?

A competitive salary, full medical coverage, a flexible environment where we actually care about not burning people out, and a commitment from us to help you reach the top of your game, whatever that means for you.

goo··on Ask HN: Who wants to be hired? (June 2014)
Hey Kevin, it looks like your locally app is giving me a 500 error when I try to sign up, I thought I'd let you know!
goo··on (Yet another) parody of 2048, where you try to lose as fast as possible
I may be mistaken, but I think you folks made it impossible to win -- new tiles that spawn always have a tile that they can merge into, so there can never be a lack of moves available.
goo··on Fred Wilson: By 2020 Apple Won’t Be A Top-3 Tech Company; Google, Facebook Will
I'll broadcast my opinions on your questions:

1) AAPL is arguably the most important company, full stop -- not just in tech. With the highest market cap in the USA, and a substantial share of mobile phones using both its hardware and software, it is the top dog.

2) I'll take the other side of that bet without hesitation. Google makes headlines because it does a bunch of cool shit, but it still makes its money on advertising. (Something like 65% of its revenue comes from google.com search: http://investor.google.com/financial/tables.html)

I think the fact that Facebook has been leveraging its expensive stock to aggressively counteract (i.e. buy) potential rivals makes me somewhat confident that it will be relevant in 6 years. The fact that they are investing in potential big future winners like Oculus VR increases my confidence. At the very least it's cool shit, and that puts them in the headlines :)

3) Who knows what future crazy tech breakthroughs will occur. There are unknown unknowns, and they will change the world and make the pioneers wealthy. Google embraces that possibility and continues to strive for more breakthroughs. If none of them succeed, at least they have their 50 Billion dollars of yearly revenue from advertising sales to fall back on...

← PreviousPage 2 of 5Next →