545 karma · joined March 24, 2011
I agree, if it was more community oriented there would probably lots of cool ideas, exploring lots of other areas, but, for me, that's what other languages are for. And for what it's worth, they don't solve real world problems as well as clojure does.
I do wish Cognitect was more engaged with the community at large, but they've been solid stewards in my opinion, and all the features that have come since I started with clojure (1.6) have been extremely useful in real-world situations and has made my job easier and more enjoyable.
I'm happy to make that tradeoff.
If anything, the community tends to give really well thought out reasoning around why they make the decisions they are making.
When making an argument, sometimes it's important to explain why something is different, or why you've made the choice you made. Just because you explain why your idea is different doesn't make it trolling.
For example, at our shop, we don't require devs to do TDD, however we require test coverage.
I don't think anyone would argue that writing tests at all is a bad idea, I think the debate is whether or not your tests should drive your application code.
I'm not an anti-TDD zealot, but I don't personally do it, nor require any of my developers to do it (but they can, if it helps them).
As with everything in software, some things work well for some people, and not so much for others.
Instead of TDD, HDD works best for me. https://www.youtube.com/watch?v=f84n5oFoZBc
The easiest line of code to maintain is the one that doesn't exist. :)
Everything in this list sans real-time chat I would consider as low complexity, low volume and low velocity. It's basically request a view, hit a cache / db, display some data. Send an email now and again. Store some stuff on s3 now and again.
There are lots of sites that have more complex feature sets then what basecamp does. Things like complex transcoding of media, real-time updates on their views, streaming of complex media types, need for near-real-time integration with 3rd party APIs, real-time bidding, real-time decision making, real-time analytics, etc etc etc.
I want to be very clear that I am not criticizing Basecamp as a product. Simplicity is difficult to achieve in software and their product does a great job of doing most of what you need, and not much else. I based the software stack of the first company I founded on pre-1.0 rails monolith (mongrel had just been released), so I'm not even anti-monolith.
I just think this particular post of his is entirely too simplistic and could lead younger software designers astray.
Basecamp, while a great tool, is a "simple application". I don't mean it's not well built, I don't mean it's easy to build, I don't mean it was fast to build, but if you look at what it does, it's all vanilla stuff.
Many other companies don't have the luxury of building apps that look like basecamp, and hence, our architectures are more complex.
When he writes these kinds of articles, they always feel somewhat strawman-ish.
At the end of the day, each software project has it's own unique requirements that will govern success. We got paid the nice salaries we do because it is up to our discretion to understand what is the most efficient architecture for what we are trying to solve.
That said, I will say that Rich's talks and his approach resonate with me in ways that none of those other guys you mentioned do.
It may just be how he chooses to structure his talks and how he expresses himself, but his willingness to both critique existing systems and provide (arguably) better solutions is really refreshing. I don't see that being communicated well in other talks.
That said, maybe stick with elm. The only way to make the thing you love blossom is by promoting and evangelizing it. :)
I've been using boot for smaller and experimental projects because by default it feels so much leaner then leiningen does, however, because the support tooling around leiningen is still so further advanced, for project we're putting into production here, those are still all lein based.
The other thing I'd say is, I've found what tool lein vs boot gets minimized over time as the project evolves.
In general, I do think it's gaining traction and its a great project!
I think the reason you whiteboard for google interviews because you will necessarily be a cog in a wheel, and the focus of the cog is to code.
At smaller companies / startups, you will potentially be expected to design, architect, gather requirements, code, etc.
Likewise, my wife's family can't handle traditional midwestern dishes, nor traditional soul food well at all.
That's just been my experience of course, so I'm not claiming it's indicative, but it's actually the hardest part of our marriage (which, is a good thing, I think).
One day, also in my 20s, I stumbled upon it in the "ethnic" section of a supermarket near my college. I was so excited I could hardly get out of the store before trying it out. Just like the author, I couldn't believe it was just a thick gummy starchy mess with some powdered sugar messily slopped on top.
Also, it should be noted, I'm not sure if you're from America or not, but eating sushi / thai / indian foods can actually be quite uncommon in most of America, in particular the fly-over states.
Even someone like me who grew up 10 mins from Providence / 45 mins from Boston on the east coast never had tried thai / sushi / indian food until college, and even then, I was considered weird and adventurous by my hometown friends.
You might be right that within the past decade it's become more popular, I can't say, but I know in the 80s/90s when I grew up, there wasn't much available "ethnic" cuisine.
Lastly, my quotes around "ethnic" aren't in response to your usage of the word, they are just my own response to the fact that people would consider me "ethnic" even though I grew up in America just like they did, and the false distinction has always bothered me. :)
I double checked the date of this article to make sure this wasn't written 6 months ago and posted now.
You should check out the clojurians slack channel, there you can probably get good answers for 85% of the things that are holding you back.
Good luck with it, using clojure/script + cursive clojure + intellij has been the best development experience I've had in 18 years of professional coding! It's 110% worth the investment.
Sorry, but this is a bit ridiculous. You could make the same counter-argument from the employees perspective as well.
"If my company isn't willing to sacrifice to pay my current market worth, then they don't really believe in me as an employee"
Is this company going to pay an extra 20% when things start going well again to make up the difference lost?
When you sign on for a job/salary you shouldn't feel bad for leaving if the company can't hold up their end of the bargain. If you only worked at 75% of the capacity they thought you were going to, you'll most likely be fired.
My wife's parents fit that definition, and interestingly, all her uncles and aunts who came to America are over-performing here in America, and all the ones who stayed are underperforming in Asia.