545 karma · joined March 24, 2011
I still think that LT is going to slowly peter out, as there isn't enough momentum to dethrone existing IDEs / upcoming actively developed contenders.
That said, I think this level of transparency about where your collective heads are at is great. While some people may still be annoyed (particularly those who donated to the kickstarter) I applaud your willingness to change paths and do what you think needs to be done to succeed.
I'm excited to start playing with Eve.
http://tryclj.com/ http://www.braveclojure.com/ http://aphyr.com/posts/301-clojure-from-the-ground-up-welcom... http://clojurekoans.com/ http://www.4clojure.com/
If you're saying eating red meat 7 times a week is bad, that's obvious, but I've seen no studies that say that grass-fed beef 1-2 days a week would be bad for you.
I think both monolith and microservice architectures are valid, it just requires software architects to think a bit more about the size of the problem. If you just have a slow growing self-contained app, then monolith is probably the way to go.
If you have an app that has the potential to grow quickly, or is already integrating with multiple external services, it may make sense to look at microservices.
We switched from monolith to SOA a couple of years ago, and it's been a net win in terms of price, reliability of site performance, and ease of development. There were the obvious drawbacks you stated above of network timeouts, lag, and async issues, but it's just a different set of problems.
Furthermore, if these articles really wanted to help people, they would explain what pieces of the paleo are bogus, and what pieces make sense, because the fact is, if most people cut back on processed grain, refined sugar, and processed seed oils, and doubled down on fresh fruits and vegetables and solid protein, they would in fact become healthier.
One trigger for VAF is indigestion in the stomach, which irritates the vagal nerve, which messes with the heart. The vagal nerve also runs into the brain, so I bet there is some form of two way conversation happening between the stomach and brain being facilitated by something like the vagal nerve.
To your point, when I was heavily symptomatic, I felt depressed (deeper then just being sad about my situation), and changing my eating habits cleared that up, and in your case, fixing the brain chemicals seemed to have benefitted your stomach.
Its just a guess on my part, but this is really all fascinating stuff.
Regarding the diagnosis of IBS, What I'm saying is, I've yet to have had (or seen) a test that definitively states "yes, you have IBS".
During my time with stomach issues I've been tested for UC, Crohns disease, Celiac disease and gluten sensitivity. All the bloodwork and whatever else came back with definitive nos.
Once all of those were ruled out, then the diagnosis became "IBS". Meaning, I didn't take a test that said I had IBS, I was symptomatic and all the actual tests they could run were negative, and hence, I had IBS by default.
What that meant to me was, something is wrong, they just don't know what it is, I should keep searching and trying things to figure out what they don't understand.
I've read so many posts where people get diagnosed with IBS, take the prescribed drugs, and just suffer for the rest of their lives. I just want people to understand they should feel empowered not to settle for the IBS diagnosis and explore options to try and solve the issue for themselves (like you did via SSRI).
Yeah, I think for those of us with "Generic IBS" we need to be aggressive in trying out different approaches to try and heal our gut issues.
I went paleo once I realized wheat was causing me all sorts of stomach issues, and over the years I drifted more and more towards a "natural and whole food" diet, and as my intake of veggies grew, I realized that asparagus and brussel sprouts seemed to do a number of me. When I went to the gastroenterologist to try and figure out what was going on there, he first recommended drugs, which I declined, but he then suggested looking into the FODMAP diet, and it turned out that most fructans were triggers, as well as some polyols.
When I ate wheat, I suffered from tenesmus, depression, back acne, short-term memory loss, alternating constipation/diarrhea, migraines, etc. Now my only symptoms are diarrhea and some stomach pain when eating fructans. I'm hoping going FODMAP only will solve the remaining issues I have.
All that said, I'm just advocating that we try whatever we can so collectively we can get data on what works and what doesn't. If we just accept the doctors diagnosis of IBS and treat it with drugs, we'll never collectively solve the underlying problem.
Doctors told me I had IBS for 10 years, then a friend suggested to stop eating wheat, and 95% of my symptoms went away.
I'm actually about to start testing a FODMAP diet to see if I can improve my health any further.
Have you tried anything to improve your health, or did you just accept the IBS diagnosis? I only ask because I've seen no research that suggests IBS is a real thing, just a catch-all for many potential things.
Github is a great resume if you're young and don't have real work experience, if you want to change "tracks" and show you have skills in a different domain, or if you really love and support open-source.
I guess it's a self-resolving problem as companies who take not having github activity as a negative probably aren't places people without github account would want to work anyway.
In a production server I'm running right now, I've used three java libs, wrapped them very nicely and neatly, and they work great.
> I was sold in part by the JVM argument. But in reality, in practice, I found it to be more a burden than a delight. First, the stack trace errors. To deploy your application, it is not just a "copy your jar in Tomcat". You have to serve using Clojure. So in reality, you don't get all advantages provided by the JVM environment, only some.
For my current app, I just need to do: lein ring uberwar, copy to tomcat directory. done.
The rest I can't speak towards as I don't know Haskell. Also, it should be noted, I'm only offering counterpoints because I don't want people to not use clojure because of some of the incorrect claims. I guess we've had different experiences with clojure. :)
The parens are annoying, until:
a) You build that fully composable library that you always wished you could have written in X language, but it neeeeever quite worked the way you wanted.
b) You realize that by keeping your data immutable, it allows you to write less tests, be more confident in your code, and you stop worrying "is that value is what I think it is?"
c) By building on top of the JVM, you are able to use java interop to save yourself a day of coding a custom library for something that exists and is well tested.
d) Deployment becomes a breeze because you just export a jar/war file and load it up into any of the existing app servers.
e) You get phenomenal speed increases for "free" if you're coming from dynamic languages like ruby/python/PHP
f) When you need to dip into async code, you can write your async code, in a synchronous fashion, which (for me) is much easier to think about then keeping track of callbacks in my head.
Good luck, if you decide to give it a shot, I think you might realize the parens isn't such a big deal in the long run!
Clojure sits on top of the JVM, and as such, has the benefit of interop with some of the most robust software packages in the world.
Unless I'm missing something, you'd need to roll your own packages in Haskell for all this functionality.
I would argue that the most efficient code is well maintained open-sourced code that you don't have to write.
I don't use Haskell, so there may be lots of libraries I don't know about, so forgive me if this question is naive.
In general, I'm not the biggest DHH supporter (although, he's made me a ton of money, indirectly, via rails), but I do like that he's stirring the pot here.
Back in the 90s and early 2000s, I wrote tests, when needed. Sometimes before application code, sometimes after, it was a discretionary tool that I had in my arsenal that helped me both solve problems and feel confident that "my code won't break".
At some point in time the majority of the rails community decided that if you don't test, you're a terrible programmer. Full Stop.
The problem with this was that testing tools were terrible at the time, RSpec, before it's API solidified was breaking every other release, things like capybara and selenium and watir, always kinda worked, but not really, and you'd often spend 10 minutes writing the business logic, and then 40 minutes writing tests, getting them to pass, wrestling with external dependencies, etc.
Furthermore, because people were practicing test-based application design, you were constantly re-writing your codebase and your test suite, because if you're designing for tests, you're not designing for the domain, and as domain requirements changed, and broke your testing model, you basically had to fix everything, and you couldn't get a handle on the domain because you had to be ruled by tests.
All that said, I do think tests are useful. TDD isn't as useful for me. My thoughts are in line with Rich Hickey who said:
"Life is short and there are only a finite number of hours in a day. So, we have to make choices about how we spend our time. If we spend it writing tests, that is time we are not spending doing something else. Each of us needs to assess how best to spend our time in order to maximize our results, both in quantity and quality. If people think that spending fifty percent of their time writing tests maximizes their results—okay for them. I’m sure that’s not true for me—I’d rather spend that time thinking about my problem. I’m certain that, for me, this produces better solutions, with fewer defects, than any other use of my time. A bad design with a complete test suite is still a bad design."
Mark spends a great deal of his post talking about how the world is getting smaller, and his time is getting more and more scarce. There are so many "early stage investors" now that entrepreneurs have the same problem. You could take 3 meetings a day on investors who "want to catch up and see how your traction is". Many of them claim that they can provide insight, mentorship, yadda yadda. Some of them will, some of them won't, and as others have pointed out, some of them will want to, but may have to invest disproportionally in backing other horses.
I understand why he wrote this paragraph, as he wants to reinforce that he's one of the ones who gives attention to his startups, but it reads as if he's either naive or lying.
This paragraph aside, the rest of it is solid.
-edit- spelling
In consulting, I think this makes all the sense in the world.
a) When you hand off code, you can demonstrably prove what you handed off works. b) You can take the business objectives of whoever you are consulting for and translate those into high level tests, which helps you stay focused. c) You get to charge double what you'd normally have charged the client.
When running a in-house team at a startup none of those bullet points translate, and while TDD does offer other benefits, really at the early stages of the game every line of code you write needs to solve the problem you're trying to validate.
There was a period in time between 2005-2008 in Boston where if you didn't practice TDD you were persona non-grata.
I think interestingly enough, a good number of those people now have 10+ years experience programming and now understand what those of us who had 10 years experience at that point in time were trying to tell them.
That said, there's plenty of great places here in NYC to co-work from, so it's probably all for the best.