roneesh

That isn't agile. Tickets should be based on relative effort, not hours, and certainly not more hours being better.

I tried to cover my tracks here and say "increasingly" aware. For instance I saw an ad the other day that offered unlimited internet on your phone for $40 a month, but in slightly smaller text (not fine print, think H1 vs H2 relation) it said that after 1.5Gb speeds reduced to 128k. Disclosures like that I think will make people more aware of their data usage over time.

However my supposition is predicated on the continued restriction of data and speed by carriers. If any new business model comes along that upends that, then I suppose Americans won't become data usage aware.

It doesn't have to be a debate, everyone can move any one language into the other (JS into HTML, HTML into JS, CSS into JS, etc), as long as they feel that what they write will be something they can reason about later. They should take into account their mindset in 6 months, other people that might be brought on and what their background might be.

The only real issue I see is that if you move HTML into JS, you might make it harder for a pure visual designer to step in and work on HTML/CSS, but outside of that I can't see an issue as long as you keep reasonability of the code in mind. And if you have a good designer, I have a feeling they'll be more than glad to learn how to navigate around Javascript.

I'm not so sure that the average person won't care. They are increasingly aware of how much they pay for data on their phone plans, and how crossing limits decreases their speeds. After a big bill or two, people start looking for options.

I really love this site, it's a great quick intro to Flexbox. Kudos to whoever is hosting it here now (from my understanding the original author stopped hosting it some time ago).

As I said above in a post, in my opinion Flexbox is win, it's an attempt to create a logically consistent tool for layout, vs the comparative hackery of combining float/position/display/margin to achieve your desired layout. Is it perfect? I doubt that, but it's definitely a step towards CSS being less broken.

Flexbox takes a few hours of work to learn, as others here have said. However, once you learn it, you have a logically sensible system of layout. It's worth the time. As far as it's quirks go, that's because it was slow to be standardized, so there is outdated info out there.

If you start to learn the older tools to do page layout, you can learn each one a bit faster (float, positioning, display properties), but combined they do NOT form a consistent logical system of page layout. Your learning is just repetition to see what works, Googling of CSS tricks and then hopefully you develop some intuition about when to use which property to achieve your desired effect. This confusion is why Flexbox is a net positive comparatively.

With flexbox you can know what elements will do when you apply a CSS property pretty assuredly (well, if not now, in the near future). Without, it's a bit more learn by error. Flexbox is a brighter future.

I suspect a part of this is due to America's losing of a Spa culture. Korea, Russia, Germany and Scandinavian countries seem to have (comparatively) thriving cultures, which make people more comfortable being naked around each other.

I do agree with the common sentiment here though, what a tired, boring trope to pillory millennials for this quirk. It's hardly ideal that they're becoming more body conscious, but it's quite a great solace to instead appreciate how much they're advocating for tolerance in our society.

You might be a good candidate to teach at a coding bootcamp.

PROS: 1. Your energy level would match the students 2. You could make sure the curriculum stays up to date, and every few years transition some large parts of the curriculum to a new language/framework. 3. You have tons of experience to draw for the many left-field questions you would get 4. The consistent new influx of students might feed that need you have for novelty

CONS: 1. Not sure if you could teach each session knowing 80-90% is the same content as the last, but you're just changing 10-20% for this batch. 2. Could you handle answering some of the same newbie questions every 3 months? 3. They would, like most jobs, want you to stick around, but this isn't a total CON, they are likely more amenable to you leaving than almost any corporate gig.

So maybe it's something to consider!

I do think you might need some more help in managing this, but in the meantime, you can always find work that fits what some part of you needs right now.

I don't think anything is wrong with you. I've talked with lots of friends (devs and not), who have noticed their attentions have changed over time. I don't think it's causation that your attention has eroded with the rise of social media, just a correlation from the times you happen to live in. I suspect people in the 50's lamented vinyl eroding their ability to practice music for hours on end.

I think the ability to concentrate on one task singularly is really a gift the young get. I can't think of a single friend who has ever said it has gotten better over time. Enjoy the positive changes that come with age though. The ability to reason more objectively, the ability to control your emotions, the ability handle defeat and disappointment with grace, and the ability to plan larger things. Your body and mind change with age.

I really feel for the person in this story. Given the heightened media lately, it's hard to feel totally secure in any interaction with the police. I don't feel completely secure talking to them or interacting with them when I see them.

I however, do think the police did just an ok job handling this situation. It clearly could have gone worse, but they could have de-escalated this even further. Why isn't it possible to simply say clear statements like "We intend to respect your rights." or "We have no intention of escalating this situation". When it comes to the officer seeming to reach for his firearm at the beginning what's wrong with saying "That's something we do for our protection, and is not an intent to use?"

I'm sure people in law enforcement have answers for all these questions, and I'm sure they make sense. However, something in me will probably always wonder why we as a society find it easier to blog about police encounters, or make police wear body cameras, when it might just be easier for two people to talk more openly.

This is an amazing follow up to the greatly missed FlexBoxIn5. Kudos to the creator!

Agree, please please please not a prequel!

The big joy of Star Trek is speculating about the future, in these times especially I think we could use more optimism about a future we haven't thought of yet, not just a dramatic retcon of stories we already know.

There's no order to see it in or order to avoid seeing it in. The writing is strong for each series (though which one is best is debatable). Also every series's episodes largely work as standalone, though Deep Space 9 and Voyager have some overall stories (a war and getting home respectively). My advice is start with Next Generation, it's the best, and most any episode works on it's own. Voyager is my soft spot. Never saw the original, seeing it isn't necessary to enjoy the later ones.

Dive in, have fun, my personal suggestion is any episode that deals with time travel or the mischievous life form called Q. You can't go wrong there.

Honestly that's not the archetypal style, most reviews are more measured and often have thoughtful things to say about the record. If anything, the Onion article in which Pitchfork gives all of music a 6.8 is a telling parody and fun summation of their style.

For what it's worth, Kid A really is one of the best records of the 2000's, so if you're going to be histrionic about one, might as well be that one.

Don't let people decide if your other things are actually "better things to do", certainly not a boss, they're hardly objective. Simply state that like work, they are obligations you can't miss. I frequently have artistic obligations in the evening, and I make sure everyone knows they are unbreakable.

I've posted about the benefits of Meteor on HN before (the tiny apps I built were easy to do), and many times I've been told that the Meteor packages you'll use are out of date and require effort to make work. On this thread however people are saying using Meteor is buttery smooth. Any people care to chime on this issue? Without diving in myself and building a large app, I'm having a hard to determining if the Meteor package ecosystem is thriving or stagnating.

As much as I want to identify with the writer of this, it's hard to. A seasoned dev, especially in startups should know that a Startup Weekend can be amateur hour when it comes to people knowing the rules and norms of business. There are many ways to do startup weekend right, but being the dev for someone else's vision is almost certainly one of the wrong ways to handle that weekend, it just breeds too many resentments.

The author is right, the devs have the power now, so why did they cede it?

You Don't Know JS by Kyle Simpson is essential if you want to learn Javascript in depth.

Leave it to PG to dismantle the myth of founder as psychopath with clear, succinct reasoning and basic math.

When I met this guy in college I knew he was an awesome dude, but lost track of him. Surprised and glad to see he's risen so far in the world!

Thanks for the feedback! It sounds like you know the ecosystem more than I do, so it's good to get this point of view.

Thanks for the feedback! It sounds like you know the ecosystem more than I do, so it's good to get this point of view.

I think there can be a few avenues, each worthwhile:

1. Use Rails as a back-end only and commit to a front-end stack like Angular or React+Flux. Rails will continue to be viable for a long time, but even longer as just an easy API server.

2. If you don't know the Node ecosystem, it might be time to dive in. I haven't really enjoyed Express.js, the Sinatra-esque framework for Node, but it can be a good excuse to learn NoSQL db's (though you can use them in Rails as you know) and just increase JS chops. Also if you hire a front-end dev I think it's a tad more likely they'll know Node than Rails.

3. If this is really just to learn, I'd suggest trying other languages, Clojure seems like a great mix of mind-expanding programming along with web ready usage.

4. Meteor.js is a project I'm really interested in. It's 'Rails but for Javascript'. They have funding to stick around for a while, and they have a vision of pushing the web away from stateless API's to an always connected client. This is my answer of what I'd start a new web app in if I had to begin one today.

That's kind of the reasoning I'm rejecting. In the year 1915, Americans could on average tie 100 knots (can't cite the source, but yes it was something I once read), and I'm sure many more were a bit more seafaring and horse riding. As we developed cars and planes and clips, all those skills have receded. They aren't gone, we can all tie our shoes and swim in a pool, but these are physical actions, I doubt we'll ever lose them. And yes, kids are dumb, but eventually they become adults who understand that writing has a place in their lives.

We obviously type more than we write now, but I've always found the implicit suggestion of abandoning writing, or engaging in the hypothetical of having to pick only one, a bit of a pointless discussion. While it's not an exact analogy, I would say it's like walking and swimming. Both can get you somewhere, but just because we do one a lot more than the other doesn't mean we don't need both.

I'd be remiss if I didn't use the comments to mention the amazing and totally free, "Unix for the Beginning Mage". The author of the article also didn't mention this great resource. It's an amazing book and a short read. It took me about 3 hours to work through completely. www.unixmages.com

If you don't know how to use your shell, block yourself off an evening with this book and change how you forever use you computer.

> I found the opportunities available -- especially fulfilling ones that provide the mentorship to give foundation to a long career -- few and far between post-graduation. The opportunity that I did take will lead to another year of just scraping by and a lot of uncertainty while I continue to "prove myself" worthy of a decent fulltime offer.

I appreciate the honesty. I think you hit upon a common problem. There's really not a great job track for people coming out of bootcamps. Also, you're right, it deserves mentioning that those months afterward while you hunt for a job are lean months indeed.

I think a company that goes all in on bootcamp grads and makes what is essentially a second program for them might really find themselves with a lot of talent on their hands. But sadly most jobs you'll get afterward lack mentorship.

Which, not to beat a dead horse, but this industry needs to get a better grasp on tech mentorship.

I'm curious to know what better options you're talking about?

I'll be honest, I disagree here. I know on the onset 10-18K is a lot. In fact I warn people before they do a bootcamp: "Do you want to spend what would fund a trip around the world?"

But over a life time, if they work hard after and keep coding after, they can 10 fold reap what they sow. If they get a tech job, it might be a 10-20k a year increase from whatever other field they're in, more if they were a barista or something. Even if it doesn't lead to coding, but other jobs at a startup like tech support, the income boost might be substantial. Also the time is so condensed, they get a lot of learning out of those 11-15 weeks. Also, unlike grad school, there's no loss of income for 2 years. Worst comes to worst, I'd imagine in many cases their old employers are likely to bring them back.

For your honesty, I would upvote this a hundred times if I could.