jb3689

25 ms·

211.
by jb3689 8y ago
Kubernetes and other container systems are so widely adopted and accepted that most common system services are solved and require only minutes to integrate. As a result people move back to their monoliths because it is easy and productive
212.
by jb3689 8y ago
All good things must come to an end
213.
by jb3689 8y ago
The number of times I've said "oh I bet this works" just to be wrong when I wrote the tests is countless. For me it's more about having small well-defined interfaces with very strong tests Moreover, tests that don't
214.
by jb3689 8y ago
Totally agree. Had a similar experience as well and then tried again a few months ago and am happy. I do still need to jump over to Le Goog for some searches though. The UI supports a good amount of tweaking which was helpful for getting me
215.
by jb3689 8y ago
> also in javascript, it's very easy to roll out "frameworks" Also worth mentioning that the switching costs for changing frameworks in JS is incredibly low. You can just load different JS files and presto - you can use a
216.
by jb3689 8y ago
> Why do you think front-end development is in such a constant state of change? Browsers have been resistant to change and meeting standards for the longest time. This resistance to change has meant that the core libraries (i.e. vanilla
217.
by jb3689 8y ago
If you look back another generation the difference is more apparent. What did you use prior to Phoenix? Node was popular for a bit, but Rails/Django was much larger. In their lifetime there have been a number of major players in the fr
218.
by jb3689 8y ago
I used to feel like the author of this post, but trees have come up at each of my last few jobs. BFS is a trivial algorithm and you really should know it. It is only a few lines. Do you work with things that have dependencies? Do you work w
219.
by jb3689 8y ago
Just found "Handmade Hero" last weekend and now this. Programmer's dream
220.
by jb3689 8y ago
To be fair, in my experience rewrites always take longer regardless of technology choices. You are often reverse engineering requirements which is really consuming both in time and energy. That said, I agree with the point you're tryin
221.
by jb3689 8y ago
Losing it any time at work is totally unprofessional. Don't work with these people. Moreover, interviewers go bananas over the strangest things sometimes. Just be reasonable and agree with or politely disagree with feedback
222.
by jb3689 8y ago
Elixir's comparisons with Ruby are almost totally superficial. It borrows only high-level concepts from Ruby (strong metaprogramming, clean syntax, concise stdlib, excellent tooling, excellent testing tools, REPL) Elixir's stdlib
223.
by jb3689 8y ago
Ruby isn't perfect but it's a great utility language and can do a lot of powerful things with very little effort. Read through Eloquent Ruby The only problems I wouldn't go to Ruby for are CPU intensive ones or ones where I n
224.
by jb3689 8y ago
Haskell. I don't like how it is whitespace sensitive and the compiler errors can be terribly unhelpful, but it's cool to see what you can do with lazy evaluation Clojure. Not something I find myself using day-to-day but I think it
225.
by jb3689 8y ago
It's worth mentioning that there are much faster JSON parsing libraries than the default in Ruby stdlib. I still don't think Ruby is the best choice for doing raw JSON parsing. Last time I had to care about JSON speed we were tran
226.
by jb3689 8y ago
I love Elixir but it's worth noting that I'd be hard-pressed to recommend it for every project because of the performance and base OS integration characteristics of the BEAM. The BEAM is a truly amazing piece of software and I do
227.
by jb3689 8y ago
I think my issue with Clojure is that it's hard to learn how to write good Clojure. There is very clearly a way that it should be written (to keep the code clean, readable, and concise) but unless you are very familiar with working wit
228.
by jb3689 8y ago
Thank god for buffers :)
229.
by jb3689 8y ago
Sure, in retrospect you could create the same thing. It's just various text processing at the end of the day. What I'm claiming is that their choice of Rails led to certain choices which were really transparent throughout the prod
230.
by jb3689 8y ago
You're right - all of those things are possible. What I'm arguing is that given you have a reasonably good test suite and are aware of what patterns to are dangerous, you can refactor fairly confidently with the tools given For ex
231.
by jb3689 8y ago
I noticed something similar with Elixir with regards to the number of tests we needed thanks to the compiler, but it also has late binding (albeit it is statically typed). A "best of both worlds" exists out there
232.
by jb3689 8y ago
Something-something IO something-something
233.
by jb3689 8y ago
Github would not have been the same in any of those. They really took to some of the Rails concepts - a lot better than most Rails companies - and it shows in their product (routing, object structures, etc)
234.
by jb3689 8y ago
My current company doesn't even lock most of their dependencies. At first I thought it was crazy (and it is crazy) but it does mean we address compatibility issues immediately. We are mostly running background jobs though so it's
235.
by jb3689 8y ago
I disagree with this slightly. I've been using Ruby for a long, long time and Ruby does give you the tools to refactor safely - few people actually know how to use them though and there aren't very many high-level tools aimed at d
236.
by jb3689 8y ago
> only being 2 years into my job I still feel like I'm thrown into a pit I think it will always feel like this. The best you can do is learn skills to make this easier to manage (whether they be about learning how to break projects
237.
by jb3689 8y ago
Use Erlang/Elixir. You get the benefits of the monolith and the benefits of the microservices
238.
by jb3689 8y ago
> Every MongoDB project I've touched has run into a schema version issue. Sure, you can put freeform data into Mongo. But when you're querying your database, will a record made yesterday have the same shape as one made six mont
239.
by jb3689 8y ago
This is not a great intro to Pony. The most interesting thing about Pony is how data permissions work and how that allows for safe shared memory (a place where Erlang can fall down for certain applications as data is always copied between a
240.
by jb3689 8y ago
If you like the O'Reilly format then I liked Designing for Scalability with Erlang/OTP. I thought it was light on the details beyond scaling beyond single node OTP apps but it covers a lot of the built-in Erlang functionality pret

More ›