drum

Even though you may not feel good at LeetCode type questions, study algorithms and data structures anyways!

Try watching YouTube videos, reading 'Cracking the Coding Interview' and get familiar with the programing language you are most competent with already or are trying to get a job with.

The best way to make up for a gap in resume or short stints at other companies is to prove you have the technical knowledge anyways.

The demo videos in the 'Installable' section should be up in your hero with the benefits listed alongside as subtitles. It took me a while to fully understand what your service does.

Coloft (closed), ROC (closed), and now Spaces - which is owned by Regus.

I have nothing but positive things to say about coworking spaces after having worked at them for the last 3 years. I've met great friends, business partners and clients. I think they'll continue to be important as the freelance and remote working economies grow.

Cool dialogue between PG and Jeff Atwood (StackOverflow cofounder) on the tweet thread - From Jeff: “You can always borrow concepts and ideas from other startups, too. It's good to look, and understand the competitive landscape in detail, but not to obsess over.“

Doh! Thanks for asking. Voltron is a white labeled version of Jira (which I did not realize when writing my post). Edited.

After using Jira for the last 2 years, Atlassian has struck me as the 800 pound gorilla that's resting on its laurels.

On my dashboard, I'm consistently annoyed by being shown the option of creating a new user account and having to decipher the UI to choose wether my ticket is a bug or feature during mission critical moments. Just give me one big button that says 'Create Ticket', we'll figure out the rest later. Secondly, why aren't tickets shown on the dashboard by default? When I log in, I'd expect to see what's going on, not have them tucked away in the nav menu.

Recently during a mission critical ticket, email responses to Jira threads were not creating new messages in Jira, creating massive delays in communication with the team until we figured out messages weren't posting. Diagnosing the issue later, it seemed to be due to file attachments in the email responses.

The problem I have with statements like this are that they apply to every large framework, not just Rails. ASP, Django, Zend, Cocoa etc. A combination of libraries are bound to be hard to update two major versions later when methods and variables are deprecated.

It seems like the core of the argument is Javascript has wider adoption than Ruby, in enterprise and startups.

I was expecting a more technical comparisons to Rails and Node. The point made about Ruby not being adopted by well established companies seems half true considering adoption of Rails - AirBnB, Twitter, Coinbase, Github, etc

The brewing trade war can't make running the company easy for Ma, considering Alibaba does more volume than eBay and Amazon combined as a portal to Chinese manufacturers. Taking into account that the company's listed on a US stock exchange yet still has to answer to government regulation back in China, I can't imagine he's having a good time being caught in the middle.

Maybe you're being too hard on yourself and expecting drastic results too soon. Day of meaningful work + gym consistently over an extended period of time will help further you in life. Reading can help further you in life (obviously pending what you read). Only thing I see up there that I'd consider as a time waster would be video games... but even then a few hours a week to unwind can't be all that bad. I think Steven Spielberg and Elon Musk are known to game from time to time

The upcoming videos in this series are mostly presented by startup founders, employees, and investors speaking from their personal experience. To your point about generic advice not working for startups, his advice seems distilled down to the most general advice that does work for startups. Given the number YC has incubated he probably has a good grasp on that. To me these videos are like candy, intuitive but great reminders nonetheless.

"Comfortable beds, nice linens, soft towels, and well-chosen amenities and essentials."

Clean linens alone has me interested. That is by far the biggest headache for me when comparing an AirBnB to a hotel. Can I trust that the host actually cleaned the bed sheets?

Other things I'd add after building a React project:

1. "Configuration over Convention" seems to be the mantra with build settings and organization of the entire application. This can make adding features slower if you're used to frameworks like Rails.

2. SEO will require additional effort via server side rendering

I think you have a great point looking at the deal in hindsight, however Instagram couldn't have looked that impressive to the typical institutional investor at the time. Facebook already had 845 million monthly active users with a large portion using mobile. Instagram was much smaller and if anything people were skeptical if a social network could be profitable. The acquisition could've made Zuckerberg look wreckless and backfired.

Interesting title considering the article's as much about Uber and battery efficiency a la Tesla as it is Larry Page.

I'm still curious about how highways for these types of aircraft will be implemented. I imagine the goal is ubiquity and at some point, with thousands of these things flying around, flight paths will be the bottleneck.

I admire Mark Zuckerberg's confidence to pull the trigger on an acquisition like this, especially doing it without consulting his board. My initial thoughts was that he has a visceral feel for the rate of growth that makes a social network successful, having gone through it himself. He could probably tell just by their publicity of growing to a million users within 2-3 months that they were going to be huge.

I agree. Unfortunately I think this is only subjectively better to the author, provides less functionality than the example it compared itself too, and adds an extra dependency.

Nice job! I've spend the last 2 months learning React and other tools in the ecosystem and was baffled at how complicated most of the tutorials were. I appreciate that this one is simple to follow yet powerful. Maybe for a part 2 you can show how to integrate React (client and/or server side).

How about the discussion around the post? Like this comment section. That's a masssively different value proposition that you only access by linking to HN rather than the article itself.

This seems like it might be an automated response but at any rate - give him a break. Mentioning the HN post to people on Twitter hardly translates to "manipulating upvotes" to me.

I can't agree with this more, and with the addition of Turbolinks in recent Rails versions you get the snappiness of a JS front end framework in areas like page load. After building a service oriented architecture with React and Rails I truly realized the benefit of a tightly coupled front end / backend for speed of development and deployment. Building bespoke API's for other clients isn't as much of a headache as it's been made out to be.

Being a general ledger, the Blockchain also can be used as a more professional way of proving you made a prediction at a certain time. Sure, as an individual, I can tweet where I think the P/E of Amazon will be in a year and refer back to it to prove my point, but is that the best way for a financial institution? Having an entry in the blockchain has a more business oriented feel to it.

Meta - What's the reasoning behind labeling it a '28,000-Word report' as opposed to a page approximation? I find 28,000 words hard to conceptualize compared to pages

Edit - I could have phrased this better. I definitely understand that word count is a more concrete measurement than pages, however it seemed unnecessary to include in the title because length doesn't imply quality and it was hard to conceptualize. The title of this post has since been edited to '100 year study' which I think supports my initial point.