1,181 karma · joined February 6, 2013
- runtime/space complexity and general algorithmic heuristics to know how the system will perform, or to be able to fix scale issues in the code.
- network characteristic (eg fallacies of distributed computing)
- CAP theorem and applying it to real world designs
- A co-ordination tool like zookeeper
- Understanding of the technological lay of the land (eg compression like snappy, different tools and approaches for communication like zeroMq, kafka
- Metrics and alerting - eg get how to instrument with statsd and know how and where to alert.
- Concurrency concerns and scheduling - you can get away with understanding futures and the actor model and can steer away from threading fortunately. (eg elixir/OTP or Akka)
- BEAM is slow for computation. - Static typing
One thing that's trecherous is that rubyists can bring whatever they believe to be the right way to do things and assume everything should be exactly the same, especially with regards to ecto vs active record. Elixir isn't ruby. Ecto isn't rails active record. Not anywhere close. It just happens to look like ruby and there are some influences in the design but Ecto tells you not too implement STI like rails does for example so don't assume you're going to do it like you would in rails. I'd argue ruby is more like scala than it is like elixir as it has multiple paradigms. Elixir is squarely functional, just a very very simple functional language. The skill ceiling is pretty low and it should take very little time for someone to get up to speed which is important because you won't find a big pool of rockstars using it in the job market so you'll have to hire good people without experience and hope they will be okay using elixir and not jump ship to go work with strong typed languages.
You could write a rails monolithic app on postgres if you're building an internal application 100 people will use. Or you could use Akka and Scala with all state in memory backed by an event journal stored in cassandra.
IMO Ruby, Python and Elixir are perfectly suitable but the last languages I would choose. I've been working with elixir for the last 1.5 years and have decided I don't really like it. I'm happiest writing scala - I get more done faster and less bugs make it into production. Event sourcing and Akka cluster allow some really interesting patters that move state into application memory. But those technologies require a much different, more involved skill and experience set to lead.
I'd probably be using Go or Scala if I had to start a tech company in a small city. Scala if I were in a large city with talent 100%. There is evidence that Static typic improves speed of delivery and it's easier to refactor/maintain. And it's faster (generally). Both languages are much more widely used than elixir.
So in turn, I put forward that we should hope a discovery of the mechanism of action and a way to put it to use without ketamine. Ketamine's action itself is assumed to _not_ the primary mechanism of action but rather a metabolite is (the experience has a part of it I'm sure - it's pretty fairly a psychedelic but the yin to LSD's yang) and scientists are working to find a drug that will have the same effect without the psychedelic dissociative qualities of ketamine (and it's monstrous allure which some people notice and fall for - but many don't)
Seems to me that only certain personalities thirst for ketamine after experiencing it. But that will all come to view in time because the black market is ready to supply to an increase in demand and it will happen that way once people start diverting ketamine. The black market will compete in that market. It will offer a product of similar quality (most clandestine on the street is close to 100% purity) but will find its competitive advantage is price and availability.
Also thanks to other posters who describe their view of the updates of content.
I know the IV user in this film (they call him Chris on camera). This user is atypical but there are many people with extensive bladder damage and negative social effects. You'll have to take my word for it. I'm sure there is more research from china especially as it's very common drug used there. Police note (anecdotally) the typical user in north america has changed to middle aged and affluent as the price of street ketamine has gone up from maybe $25/g to +$90 https://www.snagfilms.com/films/title/drugs_inc_ketamine
I believe in its power as an antidepressant. I'm just concerned about the effects a bit. It will fuel research - it seems it's not ketamine but metabolites and effects on ganglial growth that spur the sudden changes to a depressed mind. And a new objective view on life and reality.
In a clinical setting I'm sure that it's very helpful but for me the "crave a cure" caused me to not getting around to dealing with my issues of depression until after I had issues with ketamine that required intervention and left me alone with depression again.
I hope other people never go down that path. She is a cruel seductress and the draw of the sudden emotional changes is a lot to put on someone's psyche. If they're suffering, and then suddenly they aren't and they feel happy for the first time in a long time it's easy to make the association to powder = happy and that's a very powerful association for an animal/human psyche to put together.
For most people, street ketamine would scare the shit out of them but for anyone else they might get drawn in to basically constant cycles of self medication.
Buy a bubbletea, get the ingame content: Straw and bubbles.
That's not a knock on the developers or content quality though. It's a knock on the business model. You guys make beautiful things.
Reading the other posters though I can see that there are some unethical products being built where you can impact someone else negatively.
I'm not a security expert - one of the strengths is one of the weaknesses - that's it's a simple spec to implement so your average Joe can implement it, but imperfectly.
And OMG trying to refactor Scala vs trying to refactor elixir?? IntelliJ is a jet powered pogostick for applying refactorings (to quote Beck) - It's very had to make large structural changes to elixir code without a static type system and tools to help you rename, extract methods and classes, and move them around. I can do things in scala I would never dream attempting without aa type system which is probably my biggest gripe for long term maintenance.
That being said, working with elixir has turned me into an Emacs junkie and I personally find a lot of value in that but it doesn't help me deliver better code faster, just gives me nerd points because I can check the weather and reply to email from my textt editor