Sounds cool! If you have any code you're willing to share, I'd love to take a look :)
425 karma · joined March 18, 2014
That being said, I definitely agree with the sentiment here that the file based routing is sub-optimal and I think the hurt goes up exponentially with the size of a project. I've also found that straying off the opinionated path even a little gets you in all sorts of trouble almost immediately. For me it was trying to add a SvelteKit app to an existing Nx codebase, did manage to make it work in the end luckily.
Btw, if anyone has found a good solution for creating an OpenAPI spec for SvelteKit server routes, let me know. :)
IIRC this is actually one of the plot points in the Three Body Problem, where they used the sun to send out a signal and make first contact with an alien civilization.
Grover's algorithm is quite complex and I'm not qualified to say much about how it works, but I do know that the underlying mathematics is very different.
Also, testing is quite annoying too. If you're using sqlite, you can use in-memory mode and that's quite nice. But for other databases you basically have only two options: 1. setup and teardown an actual testing db 2. wrap your sqlx interfacing code in something vaguely resembling the repository pattern and create an in-memory implementation for testing. I'd call both of these options less than ideal.
Oh man have I felt this pain, trying to do anything mildly complex with Diesel's types is so ridiculously difficult. I once (foolishly) tried to write a generic repository implementation for database entities which could either have sqlite or postgres as a backend. I thought this would be very convenient for testing, being able to just keep all of the code the same safe for using a sqlite backed repository instead of a Postgres one.
I gave up after about ~10 hours of battling incomprehensible error messages.
Also, testing is quite a drag. If you're using sqlite, you can use in-memory mode and that's quite nice. But for other databases you basically have only two options: 1. setup and teardown an actual testing db 2. wrap your sqlx interfacing code in something vaguely resembling the repository pattern and create an in-memory implementation for testing. I'd call both of these options less than ideal.
At work we predominately use TypeOrm, which for all its (many, many) faults is really ergonomic and succinct. So maybe my views of ORMs is just warped.
Like, I just don't understand what's to gain.
I feel for the majority of transplant cases the answer is going to be along the lines of "you shouldn't have gotten (into an accident|leukemia)" which is technically true yet at the same time very unhelpful.
Also the ecosystem is not in the best shape; the quality of libraries is allover the place, lots of unmaintained ones or ones that only support older SDK versions of Android/iOS. Not sure it's entirely fair to blame CapacitorJS for this, but it's nonetheless the reality when developing Capacitor applications.
All-in-all Capacitor is pretty great though, definitely one of the most productive ways to develop high quality cross-mobile apps.
Definitely keeping an eye on this.
I can't imagine there's a data scientist alive who could devise an algorithm that accurately, reliably predicts "kind of a good match but not really", given only some limited inputs (basic info + photos).
I reckon from the company's perspective that positive word of mouth from people who like the app is a much better focus point.
This works so much better than swipe-and-chat, because you become much more selective in who you like (keeping you from swiping endlessly) and because it's so focused on getting people to meet IRL I imagine it has a much better higher success rate than Tinder et al. Needless to say, I met my SO through the app after using it for a couple of months. :)
Also, most of these exchanges have their own tokens which they control the supply of and keep as "assets" on their books. In doing so they can use these self printed tokens as collateral for loans. Add to that some nicely leveraged positions in all kinds of shitcoins and you start to understand how we got here.
Apparently these numbers come from a self-reported survey, so either the questioning was vague/confusing, people are not reporting the truth for whatever reason, OR... we're gonna see one hell of a drop in birthrates in the next couple of years.
I'd say that 90% of the new graduates we hire straight up cannot program beyond what you'd need for your typical uni assignment (a few months ago one asked me what 'git' was). If they're motivated and eager to learn, I can usually get them to productivity in a month or two. The ones who are not take months to get up to speed and become a real drain on the team's productivity.
The more senior colleagues I interact with are kind of a mixed bag, some are really good and a pleasure to work with others have learned just enough to get by in their current role and become useless as soon as they have to do something slightly different.
That being said I do think that the level at my company is above average in relation to "the industry". If you want to see truly large amounts of non-contributing employees, have a look the IT-department of a large bank, pension fund, government agency or some other technology adjacent big organization. They can't hire the most talented engineers to start with and then most of them are actively kept from doing productive work by layers of middle-managers and bureaucratic procedures.
The beauty with crossfit is, that it offers a nice balance between strength training and HIIT. Also, if you're of weak mental resolve like me then Crossfit is doubly great because something about doing the same workout with a group of people is extremely motivating and makes it much easier to really push yourself.
If you have a crossfit gym within a 15 minute drive of your home then I would definitely seriously consider this!
That being said, the part about people speculating on animal extinction was new to me and saddens me deeply. One wonders in what way such a person views themselves, I can't imagine it being very favorable.
Edit: just noticed I misread Austria as Australia (lol), point still stands though, a D rating is not that bad.
If I had to take a (very uneducated) guess I'd say as a society we're currently experiencing an epidemic of unhappiness, especially amongst young people, and what the article describes is just one of many symptoms.