105 karma · joined March 17, 2021
Desktop wise, I’ve been using PopOS for 7-8 months now, so it’s quite great to have that same setup in a portable fashion now.
“… we’re all alike.” Rest in peace, Edwin.
Looks amazing!
Downloaded: 7.84GB Uploaded: 64.64GB
sheesh, one popular magnet!
As a complete layman, is this a major breakthrough? The ability to communicate information via photons in a computational setting absolutely blows my mind.
Influencers (in joint union with targeted advertisements-- and even more tangentially cross-site/browser/device fingerprinting) has made me extremely embittered and disillusioned to social media in general, going so far as to delete old accounts made while I was younger and even abandoning certain platforms. (early-mid-20's here btw)
I’ve already done the legwork, cloning to the current prod DB locally and playing around with migrations, but the fear of applying anything potentially-production breaking is scary to a dev who has never had to work on a “critical” production system!
First of all, I think the caching layer (which we currently don’t have) is going to be a necessity in the coming weeks as we scale for an additional project (that will be relying on this architecture)
Second of all, it is just PK lookups. We don’t actually have a single fk (contractor did not set up any relations), which makes me think moving all of this replicated JSON data from fields to tables may help.
The queries that are currently causing issues are not filtering out any data but returning entire records. In ORM terms, it is Video.objects.all(), and from a URL param in our GET to the api, limiting the amount of entries returned. What’s interesting is this latency scales linearly, and at the point we ask for ~50 records we hit the maximum raw memory alloc for PG (1GB) causing the entire app to crash.
The solution you propose for s3 blob store is enormously fascinating. The one thing I’d mention is these JSON fields on the Video table have a defined schema that is replicated for each Video record (this is video/sensor metadata, including stuff like gps coords, temperature, and a lot more).
So retrieving a Video record will retrieve those JSON fields, but not just the values: the entire nested BLOB. And does so for each and every record if we are fetching >1
Would defining this schema with something like Marshmallow/JSON-Schema be a good idea when you mention JSON schemas we control? As well as explicitly migrating those JSON fields to their own tables, replaced with an FK on the Video table?
Tangentially related for those who have experience, I am using Django-silk for latency profiling.
EDIT2: to further comment on current table architecture, we have 3-4 other tables with minimal fields (3-4 Boolean/Char fields) that are relationally linked back the Videos table with a char field ‘video_id’, that is unique on the Videos table. Again, not a proper foreign key so no indexing.
see: Frida, xposed framework (not sure if still relevant)
I’m not sure why this is the line crossed for me. Perhaps it is only because I willfully choose _not_ to store _any_ data on iCloud (or at the very least a minimum amount as possible). Even moreso, I’m a bit unsure of what that line even is.
Is it a software vs hardware thing? No, because one could argue the service is not Apple hardware-specific, but rather specific to the iOS software.
So perhaps the line crossed is this being an OS feature rather than a SAAS feature. It is unfortunate that the precedent has been set where I am OK with potentially privacy invasive features on SAAS products, but I suppose it is what it is.
The GID signature piece is especially interesting, I have ran into blockers in scaling scrapers in the past and this sort of organizational/tracking platform sounds awesome.
I’ve been eyeing the Pinephone for quite some time now. Do you use yours as a daily driver? Or have you paired it with an a more-mainstream iPhone/Android?
I’m currently using an iPhone as my social circle uses primarily uses iMessage and I’ve found it hard to migrate. As a secondary device for debugging, testing, and a “burpsuite playground” I’m using an extremely cheap Nokia I picked up a few years ago.
I think a Pinephone would be cool to replace the Android I have.
FYI: after signing up with the MailChimp form, clicking the “Continue to website” link on the signup confirmation page results in a 404.
As a dev currently building out several fairly-complex in-house tools for a small startup, I can relate to this first-hand.
It’s enormously frustrating as a perfectionist with a slightly neurotic obsession with (in a balanced and healthy way, trust me ;D) and appreciation for best practices, I have had to (against better judgement) sacrifice many things such as extensive time spent on in-depth automated testing, abstraction of reusable code for polymorphism and shared packages, extremely in depth documentation, and many other aspects that would contribute to long term viability and efficacy. This is of course for the sake of a business-friendly timeline, and that I can appreciate.
There is a definite balance, and I have (and continue to) learn enormously from this business view on software. The “it just works” ethos can be scary further down the road. The economic upsides to this perspective for an MVP or POC type of development are absolutely massive, but I can’t help but think this could be supplemented further by dedicating more resources to focusing on best practices.
Whether that focus comes from an internal team with more dedicated resources or a third party, I’m still unsure as to how that decision should be made.
Either way, it has been very helpful in further developing my skills in communicating things like tech debt (what notions like automated testing actually mean in terms of value to a SaaS company) to the CEO and other colleagues who do not have software dev experience.
With a lifelong obsession with cosmology and astronomy, and perhaps even more applicably relevant; our own human advancement to and into the stars, I have increasingly become more and more inclined to the notion of further developing my current skillset with the eventual goal of transitioning to the space industry.
My recent experience and exposure to renewable energies has given me massive insight to just how important companies like you guys are to furthering humanity’s progress. My question to you all regarding your technology, is how you manage what I imagine to be extraordinarily large, rich, and complex datasets that must vary between use cases (you mention hotels, debris removal, etc.). The data between these use cases must vary in structure— how is it normalized/standardized to work with your pipeline(s)? The commonality I see (as a fairly novice layman in terms of space technology) is of the rocket propulsion, orbiting, and payload delivery kind, but I’m sure the data it is far more nuanced and goes far beyond that.
Furthermore, is any sort of machine learning applied on your side, perhaps in some sort of statistical analysis / metric reporting?
I’m going to definitely keep an eye on you all at Epsilon3. Perhaps you will be looking for more engineers with web dev, data, ML, and cyber/info security experience in the future!
Huge props. I can tell there is an extraordinary amount of innovation involved with this venture. Excited to see where you all go with this =)
HTMX seems as though it will catalyze those efforts.
So far I think the UX is incredibly sleek from my brief usage of the iOS app. Writing markdown feels really good, this will be a large improvement from the stock iOS app.
Excited to check out the VS Code extension and desktop experience.
However I must say that I find myself having difficulties adapting to a new note taking environment. I always seem to drift back to simple markdown notes in my preferred editor.
Perhaps this is due to ease of access and how efficiently I am able to write markdown. The only real issue I have with this system is organization. It’s very difficult to track down a specific note in a file that I have not worked on recently.
For more general note taking and journaling I still prefer pen and paper, but that is a whole other topic of discussion :)
I love using it as a "one-off" scripting language which usually involves interaction with some sort of an existing codebase.
I'm also fairly confident in doing any sort of backend-centric work, in which existing components most likely exist as well (or at the very least something POC-esque to iterate on or scaffold from).
With that said I believe most of these difficulties stem from most of my experience being backend-centric roles, so when it comes time to implement a frontend from scratch, I become unsure of where to start. The sheer amount of technologies available and vast amount of flexibility is also very intimidating.
However I've been slowly but surely immersing myself in the stack(s), and have found that much like my experience with CSS the best way to learn is to simply do it-- making mistakes and learning from them in my exploratory learning.
I do appreciate what you said about build pipelines and feel much better about my current projects :-)
quick edit: I think my lack of experience in functional programming is another factor here, however Typescript's object orientated style is very attractive.
I have began utilizing Node + React for frontend use cases but find that my build pipelines become incredibly cluttered and esoteric rather quickly.
Am going to explore wasm solutions, thanks :)
My statement was more intended to be a critique on the current perception to the layman. I believe bitcoin and crypto as a whole should be looked on as a currency, rather than a get-quick-rich investment that absolutely anyone with a spare penny can leverage for their own profit.