1,554 karma · joined December 2, 2013
My comment on value is mainly one of "all or nothing". I think a manual typing at the edge is probably sufficient for most people.
That said, you could implement all of your forms and events as structs or schemas and rig up a piece of the dev process to convert them into types. I think many in Elixir would view it as overkill so it hasn't been done afaik. But I also think it could be implemented very easily and then you'd have end to end typing.
You could rig something up in probably 2-3 days if that was super important for you.
I did manual typing at the edges and that sufficed for me.
I got really good at creating them in the end, but it was all homegrown patterns that I don't think I'd want to push on others.
My favorite (and fairly simple) pattern was emitting an event from server to client to get the client to send it's entire form state to the server. That was my escape hatch because it worked inside of any component structure.
I bet I'll see 5% within next 2 months. Obviously interest rate changes drastically over time.
Feels like a better test would be for the healthcheck to time the query RTT and report that back. Completely remove the web request from the equation.
I'm getting 7ms RTT on us-east-1. Of course I messed up my setup the first time and had RDS in Ohio... That was 30ms.
You would probably get sub 5ms if you did public RDS connection. Don't know if that would ever pass an audit though.
In startups there's a push for founder-led sales because it's the best way to learn from your target customers.
It's the same for engineers. The quickest way to validate your assumptions, see where the rough edges are, identify an easy bug, etc. is directly from the customer.
I found that doing it myself with a support rotation was the best way to do this. That said, it's not "throw engineers into the deep end". It was managed by support team to optimize my time and their benefit. We were able to mutually teach each other a ton.
> You either have the client call 20 service/data?client_type=ios or you have the frontend backend call 20 different service/data?client_type=ios
The article touches on this point, and it mirrors what I've seen as well. The time from client -> backend can be significant. For reasons completely outside of your control.
By using this pattern, you have 1 slow hop that's outside of your control followed by 20 hops that are in your control. You could decide to implement caching a certain way, batch API calls efficiently, etc.
You could do that on the frontend as well, but I've found it more complex in practice.
Also a note: I'm not really a BFF advocate or anything, just pointing out the network hops aren't equal. I did a spike on a BFF server implemented with GraphQL and it looked really promising.
Fee-only simply means they are paid an agreed on price from you and they don't get kickbacks, commissions, any type of reward for where you put your money. Fee-only fiduciaries will also have a link on their website to a PDF that very clearly describes the relationship and pricing.
There are hourly fees and AUM fees. I have only seen hourly fees apply for the creation of a financial plan. I did not see any offering in my area of someone managing a portfolio for less than 1% AUM.
The cost of a financial plan was quoted to me at least $6500, so not cheap.
I talked to a "normal" financial advisor as well—they get kickbacks. They tried to put me in super aggressive setups, life insurance, etc. It was not discussed upfront what their cuts are and it was very clear that it wasn't best for me. Be very very cautious if you ever go down this route.
I did find one that sold hourly consultations and she was really helpful at confirming my plan and that another situation I may have gotten myself into was not a good deal for me.
I say all of this because $500-1000 for a fee-only advisor is something I literally could not find. Additionally, advisors I researched have minimums in the hundreds of thousands range.
I ended up following bogleheads methodology and I think I'll be happy. It's still pretty new so no real data yet.
For actual investments, I am basically bought into the "bogleheads" methodology. So, I don't think it's worth it to pay for an advisor.
BTW, Wealthfront minimum fee is 0.25% annually. I only say this because if you have more than 500$ in WF then your fee should be higher than $.11
This could be an artifact of how I build systems. I have heard of some people that build really small actors and do a lot of data exchange. Without knowing details, I'd lean towards that being an anti-pattern.
When I wrote apps in other languages in the past, I felt like I was building a big skyscraper. Everything was sorta connected and it was difficult to add new doors into the project. I was sometimes limited to building something I wanted because the runtime just wouldn't allow it.
When I'm writing Elixir, it's like I'm building a city. Everything works in concert, but I could build a small building next to a skyscraper next to another building.
This is because of the runtime, not the language. It's easy to build self contained "apps" that are deployed with everything else but isolated. It let's me build the app I want rather than forcing me into a very specific way of building.
And just to be clear I'm not talking microservice, that would be like building multiple cities connected only by little roads.
I'm work shopping this analogy since it's not as clear and concise as I'd like :)
PS. I'm pretty active in the community and other private communities and didn't know about the survey. I would have a hard time imagining large scale survey orchestration given that.
Is it really true that tax is only if the asset is liquid? Does the IRS make a distinction between liquid and illiquid here?
It will still work exactly as expected if you provide the index name manually, even if it's not the same order as the constraint in the DB.
As others have mentioned, the slack access is potentially more concerning.
However, hot swapping is not super common in practice. Mainly because it's added complexity that most people can live without.
The new LiveView book is great if you're interested in going fully into Elixir (server/client basically). I use LiveView for my product and it's great.
I think that the important question is "why does this protocol exist?" Most likely, you'll end up solving similar problems as to why Channels exist in the first place. So from a protocol perspective, it's nice that some problems are solved for you.