2,236 karma · joined August 17, 2012
Building indie and BigTech
Building: https://getgabrielai.com
Email: sisciapub [at] gmail [dot] com
But nobody is bringing it up, so there must be some qualitative differences, are there?
But if everybody it in the company it is using it, maybe it is worth to have.
Must be well though of from the beginning, like proper ACL and notification of reception (so we know what messages some other people listen to) but overall it does not seems so bad.
In your example, the trading desk would either need an intern to communicate the trades or some software developed ad-hoc. Similarly for the second examples. The data need to be moved from the trade to the risk analysis someway. Either custom software or some human need to do it.
For the third pattern, I agree that should be backed into the EBS, but you need ACL anyway. Either you let all the people in the company see the trade or you have ACL implemented somewhere.
I definitely can see the problems, but I can also see the benefits...
Just imagine all the things that it would be possible to make automatic if all the events that happens inside a business environment where in a queue.
And don't even think about how it would be great if the same queue were open to outside providers.
A tar file is a concatenation of different 512 bytes of data. The first block contains the metadata of the file, and the next blocks contains the content.
Of those first 512 bytes of data, only the first 100 bytes contains the text.
Trying to play with the orders of files to make 100 bytes of data fit next to each other in block of 512 bytes, it does not seems a successful approach.
gzip use a 32kb windows, that can include up to 64 tar headers. At the very best we are saving 100bytes * 64 => 6400 bytes alright 7kb every 32kb. For an optimal compression of the (32-7)/32 => 78%.
The author says that the standard gzip compressed to 45768 / 337920 => 13%
I believe there are better approaches...
There are deeper points in what the author says. Even if you let a process crash in the BEAM, but you don't leave the system in a consistent, recoverable state, the BEAM is not going to help you.
Once you realize this, and have a way to apply back pressure, you can get a lot of the benefits of the BEAM in any language. (Not all, being a VM carefully tuned and design for this pattern still means something, but still.)
When you realise that it is so much simpler to leave the system in a consistent state and program very very aggressively, following only the happy path without worrying about errors, you can apply the same pattern every where. Of course within reason that perform can be impacted.
My takeaway is that the BEAM (and the community around it) force upon you a very particular style of programming, and most of the benefits comes from this style, not from the BEAM itself. You can apply the same style in any programming language.
You can read as much as you want about the topic, but my suggestion would be to go and create something with it. You need to feel the difference yourself.
If you got the time, I really suggest to try the BEAM, you will have fun and you will approach software differently (and this time also better) after you internalise the BEAM way.
I don't buy that the only disadvantage is the increase repair cost of the car in case if accident.
What if it use a patched version of a weird library?
Software preservation is an huge topic and it is not done based on instructions.
Too expensive? Not as fun?
Asking as I am offering a similar service, hosted database.
simplesql.redbeardlab.com (not production ready)
If we (as relatively wealthy people in the world) really want to judge them, we should start by providing education and resources to sustainably earn a living.
Sending there our army and creating chaos was not a great idea.
The most common services like S3, Kafka, RDS (pg and mysql), Redis should be enough to cover most use cases.
With k8s and a dedicated smart team, it would be a possible adventure.
Moreover it can work great also on-premises. Several old medium business have their own physical infrastructure and they are not yet ready to move to the cloud.
I don't see it wrong to use it as marketing strategy.
I had the idea to work on this: https://jr2sr.com but I don't see much interest yet... Even though I am not pushing it nearly as hard as I should
It is useful to focus on a single technology or it can be as wide as a general topic?
(And hash map are not even that difficult, but I got asked stuff much more complex than that...)
Yes there is still a tiny possibly that it is just a talker, but such possibility seems much smaller than the possibility that it pass a coding interview on a whiteboard and then he is not that good.
Can you say the same about all your dependencies?
You will be definitely surprised.
What is this deal about commit small and often?
I usually work on problems that requires a lot of thought, a lot of back and forth between solutions, a lot of a reach this state where stuff kinda work but it is not what I need yet and I am not sure it is gonna be in the final version.
Eventually I reach the final version and I commit all together, but the commit is rather big.
Do you guys come back and fix everything after? Like re-code the solution from scratch committing at the right moment. Do you just add pieces related from the final version in multiple small commits? And how do you make sure that each commit is correct? Do you re-run the test suite after each commit? While developing?
I must say that in smaller and simpler codebase than the one I usually work with it might be possible. But if you work in complex stuff that have a test suite that take hours, the approach of commit small and fast seems wrong.
As long as we are close to each other, very important things don't get lost.
As long as you start with this hypothesis whatever analysis you do will be wrong.
We do have problem coordinate between teams that share the same hall and the same boss, I cannot even imagine what would happen with complete remote team in Vietnam to save money. It would be just better to stop develop software ourselves.
Now with COVID-19 things are changing, but we must wait a full cycles of hires (read 10 years) before we can really tell. At the moment we are all remote, but the conditions are the same of when we left the office. And on-boarding people seems though now...
Should people get excited about it?