I agree
> avoid it if you can
avoid using it in a project, sure, but don't avoid learning it. It definitely helped me level up as a developer.
My favorite resource for learning about redux: https://egghead.io/courses/getting-started-with-redux
668 karma · joined June 10, 2010
matthewparrilla.com
@mattparrilla
I agree
> avoid it if you can
avoid using it in a project, sure, but don't avoid learning it. It definitely helped me level up as a developer.
My favorite resource for learning about redux: https://egghead.io/courses/getting-started-with-redux
This is a sincere question.
I think Twitter could have become ubiquitous, like Facebook or email, had it not gone the platform route and started to shut down third party apps. But then, how do you make money as a protocol?
that'd be "Simple Made Easy"
It was successful too. I pulled out my phone.
Try create-react-app. It's supported by Facebook and makes all of those boilerplate decisions for you. And once you have a reason to change any of those decisions, you of course can.
They did look into it. The legislature adjourned before the house and senate versions were reconciled.
http://www.massachusettsnoncompetelaw.com/2016/08/ma-legisla...
If your component hierarchy matches your application state hierarchy, don't use flux. If you need to pass pieces of state around to a bunch of different components (like sharing state across views), use flux.
My first react application was complicated enough (enterprise analytics application) to require a flux implementation. I went redux and would highly recommend it both due to its ease-of-use and popularity. However, in subsequent applications I haven't needed it and have enjoyed writing vanilla react.
http://www.ribbonfarm.com/2009/10/07/the-gervais-principle-o...
Related to the Peter & Dilbert Principles, but darker and told through the lens of the Office.
I can swap out Angular for React + Redux in my application without my backend knowing about it. The same is not true of React + Relay + GraphQL.
It's a bigger, more involved decision that doesn't strike me as being particularly practical for an individual or a small team. Couple that with the fact that making a bigger, more involved decision is harder for bigger teams and it becomes apparent why it would be hard for Relay + GraphQL to "win" over Redux.
To ask an admittedly naive question: is it possible to get funding and remain private? Does that even make sense?
Obviously investors want to make money, can profits at a private company serve that function? Or are tech investors mostly (only?) interested in > 100x ROIs?
Paul's closing remarks remind me of a bit that the late Bill Hicks used to sign off with:
“The world is like a ride in an amusement park, and when you choose to go on it you think it's real because that's how powerful our minds are. The ride goes up and down, around and around, it has thrills and chills, and it's very brightly colored, and it's very loud, and it's fun for a while. Many people have been on the ride a long time, and they begin to wonder, "Hey, is this real, or is this just a ride?" And other people have remembered, and they come back to us and say, "Hey, don't worry; don't be afraid, ever, because this is just a ride." And we … kill those people. "Shut him up! I've got a lot invested in this ride, shut him up! Look at my furrows of worry, look at my big bank account, and my family. This has to be real." It's just a ride. But we always kill the good guys who try and tell us that, you ever notice that? And let the demons run amok … But it doesn't matter, because it's just a ride. And we can change it any time we want. It's only a choice. No effort, no work, no job, no savings of money. Just a simple choice, right now, between fear and love. The eyes of fear want you to put bigger locks on your doors, buy guns, close yourself off. The eyes of love instead see all of us as one. Here's what we can do to change the world, right now, to a better ride. Take all that money we spend on weapons and defenses each year and instead spend it feeding and clothing and educating the poor of the world, which it would pay for many times over, not one human being excluded, and we could explore space, together, both inner and outer, forever, in peace.”
That said, even the author of LCTHW (Zed Shaw) recommends writing in languages other than C. He specifically mentions Go, Swift, and Rust.
Check out his rant on K&R C at the end of LCTHW for his thoughts on your question: http://c.learncodethehardway.org/book/krcritique.html
Data source: http://radar.weather.gov/GIS.html My GitHub repo: https://github.com/mattparrilla/wxGIF
Here's the continental US (@wxGIF): https://twitter.com/wxGIF
And a list of the bot network: https://twitter.com/wxGIF/following
Nothing says "state of the art" quite like a highly pixelated image on your "we got hacked" response letter.
What does this mean? Is software engineering "below" programming? Do software engineers write less code?
I've only been in the industry for a few years, mostly working on my own. I've assumed these titles were arbitrary. Are they not?
So building a career and being an entrepreneur are incompatible? I completely disagree with that idea. Not every entrepreneur is going for the big dollar exit.
I for one would be perfectly happy building my own company and never taking a dime of funding. Who wants to exit when you're doing what you love?
Fuck a career? No thanks, I like what I do and hope I can do it for a long time.
Granted, there's a lot of material to cover, I don't think that's an appropriate response–especially when delivered with contempt, as it typically was.
I don't think that that's the real argument being presented in the editorial. Rather, it's that for a large portion of humanity, success means overcoming tremendous odds. When your parents sit home and drink 22oz Milwaukee's Best Ice all day, how do you even learn what you need to do to be successful?
At any rate, this blog post provides the quote in question, from page 229 of "Omnivore's Dilemma" though it turns out it's the USDA, not the FDA that is mentioned.
http://www.businessweek.com/smallbiz/running_small_business/...
Here's the quote: "The problem with current food-safety regulations, in [small farmer Joel Salatin’s view], is that they are one-size-fits-all rules designed to regulate giant slaughterhouses that are mindlessly applied to small farmers in such a way that “before I can sell my neighbor a T-bone steak I’ve got to wrap it up in a million dollars’ worth of quintuple-permitted processing plant.” For example, federal rules stipulate that every processing facility have a bathroom for the exclusive use of the USDA inspector. Such regulations favor the biggest industrial meatpackers, who can spread the costs of compliance over the millions of animals they process every year, at the expense of artisanal enterprises like Polyface [Salatin’s farm]."
I didn't say that eliminating the enforcement of cleanliness standards would reduce illness, rather I said crushing the small farmer isn't the answer and suggested that more small farms would reduce illness.
Example (from Michael Pollan's excellent book "The Omnivore's Dilemna"): FDA regulations that require slaughterhouses to have a private restroom reserved for the FDA inspector.
For a large multinational corporation processing tons of meat per day, that is a drop in the bucket. For a small slaughterhouse processing maybe a handful of cattle/week during peak slaughtering season, that's a much more substantial cost.
Food borne illnesses are, in fact, a serious problem but regulations that crush the small farmer aren't the answer. Large scale farming may be incredibly efficient at producing food but they are equally efficient at propagating food borne illnesses.
Promoting small farms when possible is beneficial to society and the planet for a host of reasons, including the reduction of food borne illnesses. Nature abhors monoculture and always fights to restore ecological diversity.
The mountains are smaller and the states are more densely populated, but that doesn't mean that the wilderness can be taken lightly, particularly in winter. Especially for a sport that places value in isolation ("first tracks" are highly sought and many locals have their own secret powder stashes) you'll often find yourself in situations where an injury or gear failure can mean serious mortal peril. Even if you're lucky enough to have cell service, batteries don't hold their charge in extreme cold, more often than not, you're on your own.
These hobbies are, in fact, dangerous and the consequences are real. They are also incredibly fun. You've just got to know what you're getting yourself into.
Mt. Washington previously held the record for the fastest wind ever recorded at 231 mph (http://www.mountwashington.org/about/visitor/recordwind.php)
The mountain is notorious for its fickle weather.
All of those ads prompting you to visit a company's Facebook page are today's version of the "find us at AOL keyword So-and-so" that you used to see all the time in the late 90s.