24 karma · joined January 21, 2014
I will say that for some sites the images will be only ok (stripe was only on). But as long as you have a good mobile render, It will work very well.
If you don't know what OG images are it's basically the miniature version of your site that shows up on social networking sites like Facebook and X.
Some people spend a lot of time optimizing that sort of thing but you can just throw this in your meta tags and it works well enough for now.
Anyway I would welcome some feedback, it was sort of fun to put togethe.
• hours worked • cash invested • revenue generated • expenses covered
Calculates “ownership slices” from those inputs and shows how the split changes when assumptions change.
Nothing you can't do in excel. The full site (also free), allows more complex calcs.
Any advice or requests for more details are deleted by the moderator.
This is a "set up", designed by the owners of the subreddit to make people who don't know how AI and tooling work afraid of AI. Clearly the author is colluding with the moderators to prevent difficult questions or concerns.
Embedding + tsvector scored ranking (OpenAI)
GPT-4.1-mini reranking + 5-bullet summaries
CSV export
No signup required to try it — free for up to 200 resumes/month.
Tested it on batches of 1,000+, and it holds up (worker/scale/queue).Stack: FastAPI + async workers, GPT-4.1 rerank, pgsql, Fly.io, nltk
Would love feedback on:
Ranking quality
UX flow
Whether $49/mo feels right or not for pro-modeThis is not about posting some big summary, it's about creating a draft for an actual human to pick through.
It drives focus and productivity, doesn't take away from it (for me at least)
Anyway, a lot of it runs in the browser and uses indexdb for storage. Should be possible to make all of it do that.
I might throw ads on it one day, but it took me 2 hours to build it, and it runs clean.
Any advice for features? Was thinking of linking it to a crop/cut thing.
I added a login button so I don't get too much spam and I can throttle use (for now). Looking for advice.
My goal is:
- one input box. maybe a browse button to pick a file - no controls, sliders or things. just free form text as the only ui - currently it's only really good at flowcharts and system diagrams - want suggestions for types of charts people might like, types of data, etc. - vague idea that a "public" checkbox could feed community charts through to some social page where people can comment. maybe just tweet it out. not sure if that idea is useful or annoying to anyone. maybe i should scrap it. - thinking i will do venn diagrams next because it's cute and fun. or maybe maps. or maybe a stock price link? not sure what people want tbh. - generally just want feedback on the idea
An ORM layer should always serve as your primary object interface, not just a weird way to execute SQL calls, while your real objects do the work.
Also, I like my DBA's to be DBA's: to know everything about how to optimize databases, indexes and to do so with SQL. I don't need or want them to be experts at some ORM.
omen2 takes a unique approach to object management by generating "convenience code" based on an existing database's schema. Also, the codegen layer is completely optional.
I'm not going to claim it's done the best possible way, but it's good enough for the dozen or so databases we're using it for, and it's makes far fewer assumptions and has no built-in limitations.
omen2 allows a full separation between marshalling, serialization and databased design.
The syntax/structure below seems pretty clean (suggestions welcome), and because it doesn't do that much, it seems unlikely to stop working randomly.
db = notanorm.SqliteDb(":memory:")
db.query("create table foo(bar)")
db.insert("foo", bar=22)
db.select("foo")
db.select("foo", bar=[22,33,44])
(that last statement is a placeholder-generated IN clause)It's left as an exercise for the reader to structure create statements properly (mysql and sqlite syntax is actually pretty compatible).
But realistically, your DBA doesn't want you running create statements from python anyway.
Many libs I write wind up being discarded eventually or replaced with something better. This one has stuck around for 4 years now, and seems to be pretty useful.
It currently only has mysql/python drivers but writing a new driver is pretty simple.
For example: `cloudsync file://home/me/gdrive gdrive://folder`
In addition the cloudsync python module can be installed via pip, and the library can be used in software (LGPL) that performs file synchronization. This also provides a unified interface for working with cloud files.
By design the interface is the minimal needed to support sync across a broad set of providers. Metadata that is not needed for sync is not supported.
Support for new cloud providers can be easily added by anyone producing a module that uses the "cloudsync.providers" plugin endpoint. As long as the 'provider tests' pass, any cloud service should work with the sync system.
We're currently supporting the local filesystem (via watchdog), along with OneDrive, GDrive, Box and Dropbox.
This library is probable most similar to rclone, which is much more mature for those who want a single-direction 'rsync' like service without support for events.
I'm having mild symptoms, but it's been weeks, fevers come and go, and honestly it's like nothing I've ever had before.
In other words, many of those who died today would have died within the year. Many were already in and out of hospitals for serious diseases.
So, not only is the IFR wildly unknown without serology tests. The CFR itself is also severely biased.
Currently in the U.S. you cannot get tested unless you have severe, life-threatening illnesses.
The fact that the U.S. has such a low CFR speaks very well of healthcare in the U.S.... considering the majority of those tested have severe symptoms.
By failing to contribute, small companies cost themselves money very quickly. How can a small business afford to live in a world of un-maintainable forks, patches and tech debt?
Only large companies can afford to maintain private forks of FOSS. Small companies have to give back, or they will simply disappear.