What is your source for the number of ruby/rails jobs at the moment?
967 karma · joined August 19, 2015
What is your source for the number of ruby/rails jobs at the moment?
The external key is base64 encoded for use in URLs which results in an 11 byte string.
This hides any information about the size of the data, the creation date of customer accounts (which would be sort of visible with UUIDv7) and prevents anyone from attempting to enumerate data by changing the integer in URLs.
I thought about using UUIDs as external keys but the only compelling use case seems to be the ability to generate keys from many decoupled sources that have to be merged later.
64 bit should be enough for most things https://youtu.be/gocwRvLhDf8?si=QBheJCG21bAAV0Z7
In our application we have one important join that actually makes things a lot faster than the denormalized alternatieve. The main table has about 8 references to an organization table. To figure out what rows should be selected for a particular organization, you could either query on those 8 columns, making a very big where/or clause. As it turns out, PostgreSQL will usually end up doing a full table scan despite any index you would create.
Instead, there is an auxiliary table with two columns, one for organization and one reference to the main table. Joining on this table simplifies the query and also turns out to be much faster.
So at some point I wrote a script that read the ActiveAdmin parts and used a library to convert it into its abstract syntax tree. Now I could manipulate the tree and shape it into regular Rails controllers and plain old HTML views. That took care of about 90% of the work. The remaining 10% was of course the weird exceptions. Finishing it took a lot of testing, a ballsy deploy to production, and a further hour of frantic bug fixing, but then it was done. No more productivity destroying hassling with the smart admin framework. I think I would have quit my job way earlier if I wasn't able to fix that, and had to live with it instead.
I think a lot of companies would not really be capable to setup an alternative in time and would just have to start paying instead. Which would not be a bad thing. The opportunity cost of switching might be higher than just paying Docker for their services.
function handleClick() {
setCount(count + 1);
console.log({ count });
}
Since count is enclosed within the function, it could be mutated by _anything_. In isolation, you can't really be sure of what setCount does, since the "count + 1" statement passes a completely new value unrelated to count.If setCount didn't have any side effects, it is an obvious mistake to assume the value of "count" would have changed.
So if the intention is to log the incremented count, it is bad code in any situation, React or not.
For example the "Accessing state after changing it" has absolutely nothing to do with React or async code, and everything to do with the scope of the count variable and how JavaScript passes numbers by value.
The job is not without any hard parts though. I may have a lot of freedom to build a product the way I want, but I didn't have any technical colleagues to discuss problems (or joke around) with. A start-up naturally comes with a lot of uncertainty. You have to make a lot of hard decisions and then make sure they were the right ones. And it might take some time before I make as much money as I did working for someone else.
Every job will have pros and cons and you'll always need to make some trade offs.
At Lean Customs we are building better software for declaring goods to Customs. We are a self-funded startup focusing on building a good product with good people, without the pressure of investors that want to see continuous growth.
We build our product backend in Rust and take a very pragmatic approach to keep things simple. No complicated cloud setups, no distributed computing, no unnecessary glitter. A focus on a good user experience with a target of very low response times for everything.
We are looking for a (mostly) backend engineer that is comfortable in a start-up environment in a very small team. You should be able to diagnose problems and come up with solutions on your own from end to end, including some frontend or devops work when necessary. The work requires good organization and carefulness, a tiny mistake can cost a lot of money. Experience in logistics is preferred as you will need to learn a lot about the domain.
We are based in the Netherlands but it might not be an issue if you are located elsewhere in the EU.
If you are interested and want to know more, you can reach me at: dirk - leancustoms.com - Please only reach out if you are personally interested, recruiters or agencies not welcome.