thedoops

Scala and Akka are... less simple. It's also not like the actor model takes over the whole paradigm. Actors are largely a runtime concern. You're still using modules and functions. The JVM is also less suited to implementing an Actor model. A lot of the BEAM's power comes from the preemptive scheduler.

If all you're doing is CRUD apps, there's not much more to gain from Elixir. But if you're doing things like pulling in Redis or Sidekiq, or building around realtime use cases - Elixir has so much more to give you.

I've found CQRS and DDD designs fit well with OTP and elixir. The actor model with pattern matching ends up cutting away a lot of the classical OOP DDD details.

The issue I see is carryover from other ecosystems taking paradigms that aren't necessary and don't fit into libraries and patterns. It feels like there are still conventions to settle on.

Different tools for different jobs. Rust is more of a systems language for close to metal performance and memory safety. Elixir is memory safe from a functional perspective utilizing the actor model. Elixir is good for real time concurrency and higher level systems.

Good rule of thumb is that the best production per panel ratio to get the most utility consumption offset (so you drop to the lowest tier) will return the most savings.

Shaded or North facing panels in the northern hemisphere are almost never worth it. Put what you can on the south and look into a better AC unit, new windows, LEDs, and insulation first.

Pattern matching is a good fit for lambda use cases.

Like alcohol, if weed is taken close to bedtime it will interfere with the sleep cycle. I wonder how much of the cognitive impact is sleep related?

Deployment and configuration is among the top priorities from both the core team and the community from what I can tell. There's been a lot of discussion about it and some resources being dedicated in the last year. So only a matter of time, but a little heavy on initial deployment for sure.

In Elixir+Phoenix you get all the CRUD conveniences as in other frameworks, but you also get trivial Reactive/real-time capabilities that would get very hairy in something like Rails.

The Star's My Destination by Alfred Bester (also known as Tiger Tiger). Really great Count of Monte Cristo type plot with teleportation and a great antihero. I'm surprised it hasn't been adapted to film or long form series yet.

Anathem by Neal Stephenson is superb and I recommend you carve out some time to really let it soak in. Anything by Neal is phenomenal, but Anathem stands out for me.

Aurora by Kim Stanley Robinson is my favorite sci-fi book I've read in a while. Generation ships, AI, and a fascinating narrative perspective. I'm a sucker for realistic/hard scifi with well-researched technical explanations, and KSR is among the best.

I'm cautiously anticipating Lenovo's announcement of the P1 which will supposedly ship with the intel+Vega chip. Rumors are that same chip will be used in the next Gen MacBooks.

They're also working on some Ryzen cpu model equivalents to the t480, t580, etc. All of which will have better graphics performance than the equivalent Intel cpu.

What I really want is a Ryzen Thinkpad x1 2 in 1 with good Linux support, but maybe that's too much hopeful thinking. My t430 will suffice until I find something worthy to upgrade to.

Elixir is an absolute pleasure. The benefits of Ruby's developer experience with a maintainable, scalable backbone.

You're right. Salesforce is a big, complicated, multi-tenant, CRUD application coupled to an Oracle database. Multi tenant architectures themselves aren't an issue, but Salesforce implemented it well before the days of containers. All the Apex code has to be "bulkified" which means writing almost everything for multiple records in an execution context. This adds to the mental effort and reduces readability. A major concern when not all consultants do it well.

They've been trying for years to replace the Oracle database with Postgres, but it's not easy in such a large, heavily used enterprise application.

For many situations I recommend integrating with a messaging system and using the REST apis from something like Ruby.

Lightning is not bad, but it's slow compared to the front end framework competition. It is pretty fast to develop with though.

The classic solar sales and installation company business model isn't shaping up very well. Operating margins aren't the best due to the need for local assets in frequently changing markets as incentives come and go. It's definitely more profitable to sell batteries/panels/etc to the solar installers than to run the operation itself.

The gig economy has barely begun. It won't be in full force till I can see quest/gig markers in mixed reality. Ironically I think to implement a gig economy to this extent we'll have solved the problem of merit to the point money is much less influential. It could very well reverse the tide of egregious wealth inequality. The challenge is to build systems which can securely aggregate data on a person's subject matter expertise. The better we can estimate categorical competence the better we can make opportunities visible.

Less sugars, carbs, and highly glycemic foods such as wheat, rice, and corn will probably make the most difference. Basically avoid the sorts of things in a Little Debbie snack. It'll improve your skin a lot too!

Hire the people who worked on The Frankenstein Chronicles. They really did a great job on getting the dirty London/Ankh Morpork right.

Regardless I'm skeptical if they can pull Discworld off. Probably a good idea to start with a Vimes mystery if the casting is good.

Probably something more architecturally sound for future platforms in augmented and virtual reality among other things. One of the biggest issues with Android is managing permissions for apps to system resources. Proper sandboxing of 3rd party code is a big deal, especially if the next generation experiences are so much more immersive.

Was this a bottleneck to the end product? If at some point in the process there's a different bottleneck, I'd expect it to be reasonably construed as dangerous. That being said it sounds like an ownership problem. Red tape made from past fires (not the pink slip kind ) can easily become the real problem in a complex operation like this.

What if Facebook is weighting the votes based on content consumption and interests of users? If that's the case, then it's possible to get some interesting results. We need to be doing experiments like this.

This notion that the Alt-right is just another side of the coin is, I think, a misdirection. In fact I think the whole Alt-right label is entirely arbitrary and doing a significant amount of harm by polarizing the discussion. Black and white representations of the world leave us confused and frustrated.

Truth is the world is complex. We're dealing with multi-variate problems to use JBP's term. The societal benefits of free speech and open dialog are harmed by polarization. Reductionist generalizations pollute truth with doubt. Our societal discussions should be liquid and multi-dimensional.

Elixir and Phoenix are amazing. I use them any chance I get. The problem now is that the ecosystem is still in early stages. You're gonna end up writing some more libraries whereas in an ecosystem like Ruby there are gonna be plenty of gems handling the typical things like Api wrappers.

Based in some part on the relative upvotes of other posts in a time period maybe? California users probably haven't waken up in mass yet.

The real value of a teacher in the same room is for immediate feedback. I'm of the opinion that lectures should be replaced with active study sessions where the teacher(s) walk the class through problems and/or help individual students through gaps in their knowledge.

Lectures can be asynchronous; rather than the teacher reinventing the wheel, let them assign students to watch the best lectures available online.

Reverse the current model, do most homework at school, and watch the lectures at home.

I think it's more of a development life cycle problem, Elon started earlier and rocketry ain't easy. It's less a problem of money as it is in scaling up an R&D operation to effectively use the money. Scaling organizations of people is bottlenecked in enough ways that the added domain difficulty of rocket science creates a situation where throwing money at the problem has diminishing returns.

I'm in sort of the same place, I'm in a reading frenzy to build up a vocabulary and learn category theory, functional concepts, etc.. While this is good I know I ought to spend some time practicing algorithms or building toys to really make what I'm learning intuitive.

Most of the other books I'd recommend in this area are mentioned already, but I'll add Aurora by Kim Stanley Robinson. The primary narrative is from the pov of a generation ship's A.I.. You get to see it learn over time and with it it's vocabulary. Since it's a ship it gives KSR the opportunity to do some very fun info-dumps on the situation.

Probably one of the most thought provoking pieces of scifi I've read.

I'll also recommend Accelerondo, and Seveneves.

Fantastic article. I find the idea of cycles being pretty core to this. Jason mentioned it in more detail in a comment below, but the fact a stakeholder can't sway an ongoing project until its cycle is finished is huge.

I work on a small team building IT and IS infrastructure for a very sales-oriented business. Stakeholders are always throwing in a new twist at what feels like the most inopportune times. If we could tell them we'll consider it on the next formalized cycle that would be huge for preventing redirections. Stakeholders may not acknowledge it themselves, but they care less about what gets done and more about when. Closing that feedback loop we always be more effective than feature creeping a project into oblivion.