thegoodlab

Well getting drunk with friends in the afternoon doesn't seem like it's the answer to life either. I'm 31 and wake up at 5am during the week. Get to the gym before getting into the office at 7:30. Definitely have enough time to get drinks with friends here or there. I'm not staying out all night partying by any means, but there is certainly a way to make it work.

“Looking back over a life of hard work … my only regret is that I didn’t work even harder.” - H. L. Mencken

Sorry, I don't mean to troll, I just dislike the strawman argument of "[being productive/working/etc] isn't everything in life."

I'm using React on a few smaller projects where I didn't want to over engineer the whole Flux architecture. I put together the app using Backbone (for the models and collections) and used React for the view layer.

The models and collections worked great as "stores" and I used the simple dispatcher from Flux to handle the actions being sent.

While I really like the Flux pattern, for smaller'ish apps it did seem a bit of overkill.

A couple articles I was referencing for BB and React:

https://blog.engineyard.com/2015/integrating-react-with-back... http://www.thomasboyt.com/2013/12/17/using-reactjs-as-a-back...

It's all relative. At any moment in time there are going to be "native," fat client, devices that are running more powerful applications than that can be run on a thin client, "web," model. There is always going to be a transition to move those applications to a thin model, for scaleability reasons, and when that happens there is going to be some new software that requires the fat client model again.

Either way, it's about figuring out which model works for the problem you're trying to solve. If you advocate for one, you're missing opportunities in the other.

marionette should pretty much be prerequisite for using backbone IMO

Let the hate begin

Yeah, I suppose that's what I was trying to allude to in my original comment.

<opinion> This guy seems pretty lucky.

> I mean, how you can feel that burning love when you’re sitting at the table discussing how to use the last twenty dollars in your bank account?

These are types of issues that, IMO, people need to figure our while they are dating, and not just jump into marriage with someone before knowing how they handle tough, down-on-your-luck, situations. How you handle finances, how you divide chores, the dynamic of a family you want... all these things should be figured out before you pop the question, to make sure you're on the same page with someone before you make to commitment to be with them forever.

It's great this guy found happiness with his wife, but that's quite the gamble he took, not knowing those things before getting married.

</opinion>

>This is the perfect example of everything wrong with modern web design.

This seems to be quite the hyperbole. Sure, it might over use some modern design trends, but there is nothing inherently wrong with that. Also, what is wrong with themes on themeforest? Many are built with great design in mind.

More than anything govt. sites are not friendly, don't organize their content well, and do a horrible job at engaging their users. I would say this site does all of three, making it at least a decently designed and well built site.

> In some respects, the plethora of choice this problem represents is the power of the web, but overall I think it does the web a disservice because there isn't enough weight put behind a single platform.

Fair argument (I guess?) but the opinion comes down to, do you prefer an open and ever-changing ecosystem that has no limits on what you can build and how you can build it; or do you prefer a contained ecosystem dictated by a few powerful stakeholders who subtly apply their own methodologies and beliefs, to shape the capabilities and limits of the platform?

The latter seems like a slippery slope and would eventually serve the the powerful stakeholders rather than the people building the platform. The former, while it may require a higher learning curve, puts more competition between technologies that enhance the platform, and doesn't dictate what or how things can be built, serving the developers and users above all else.

Personally I would prefer the former.

PHP "out of the box" is very easy, sudo apt-get install php5 mysql-server apache2.

I started freelancing a little over 2 years ago and have more than doubled how much I was making at my previous agency job. A few tips would be:

- Save up 3 - 6 months "salary" before you jump-ship. While you are doing that, build your portfolio and start lining up work. If after 3 - 6 months you can't find work, you can always go back to working for someone else again.

- Hire an accountant. For the amount of stress they reduce, they are worth every penny.

- Establish good relationships with a few agencies close by, where you could possibly do contract work. You may not be able to charge them as much, but having them as a fall back when you are slow is nice.

- On a related note: Don't consider contract work through other agencies bad. From my experience, one agency gets work from another agency, who gets work from another agency, etc.. There is good money to be made being the production guy.

He's trolling.

The article was well written. Obviously not everything someone would need to know to start freelancing is written in this article, but it does present some very valuable information.

Thanks for writing and sharing.

I agree, having a full time job and a freelance career is not easy. Having also done this myself, I always felt somewhat guilty about moonlighting. Once you decide you want to go freelance, my advice would be to start saving money so you can get a 3 - 6 months "salary" saved up, and during that time start trying to line up work and get your portfolio ready to go.

Glad to see progress, but the big gotcha is that even though you can specify quantity of subscriptions, you still can't subscribe them to multiple types of plans. Seems like thats the next step...

Most do.

37Signals, Pivotal, Zurb are great examples of companies who have transitioned from client based to product, or are currently doing both.

I'm a freelance developer and based on my situation and those of my peers, everyone is working on side projects. The reason I choose to consult and have clients is because it lets me be my own boss and create a business doing other people's (clients) work. I can craft and hone my skills doing client work, while always brainstorming an idea or product to launch in my spare time. When the moment strikes I will already have all the resources and knowledge available to make a great stab at the startup scene.

Neil deGrasse Tyson does a good job of explaining the difference between modern science and philosophy at the 1:02:00 mark in this video: http://www.youtube.com/watch?v=9zXYTwuwsyI