The use of commit-hooks is also very clever (mentioned here in the replies)
Command line bros, assemble!PS1 is the settings that give you the cool prompts on the command line.I've gone searching for a directory of PS1's where I can browse, save, and try out different command prompts.Do i need to make this? Or is my google-fu, perplexity-fu, and gpt-fu just not where it needs to be?Or do I need to make one?
Then those tokens would be saved in the database for your freelancer to use on their customer's behalf.
I've created oauth2_capture (https://github.com/heysamtexas/django-oauth2-capture/), a Django package that makes it easy to capture, store, and refresh OAuth2 tokens from multiple providers.The package currently supports Twitter/X, LinkedIn, GitHub, Reddit, Pinterest, and Facebook, with more providers planned. It handles the entire OAuth2 flow, from authorization to token storage and automatic...
One left tech to join his brother in an outdoors adventure company where they rent/sell rafting and camping equipment and run tours.
I know another one who shutdown his zombie startup. Now he just manages his rental properties and runs a newsletter for a "ZeroHedge" type crowd.
No one seems to be getting rich but they seem much more fulfilled.
This is in my requirements.txt
git+https://github.com/richardpenman/whois.git@master#egg=python...
And the meat of the file:
import whois
"""Get WHOIS information for a domain."""
try:
domain_info = whois.whois(domain)
except whois.parser.PywhoisError as e:
return Response({"message": "Bad request", "details": str(e)}, status=400)
if domain_info["domain_name"] is None and domain_info["registrar"] is None:
return Response({"message": "Bad request", "details": f"{domain} not found or registered"}, status=400)
return {"result": domain_info}If this thing takes off and becomes a thing then adding those will be fairly straight forward.
Long story short is that I've decided to build an API service that wraps many of the most useful libraries and other services, even those "one-feature" SaaS offerings.
Be gentle, I'm sharing it to poke and critique.
I have some colleagues in F50 companies who asked to have a service like this deployed internally because of a number of bureaucratic reasons.
It is easier to get an internal API approved than it is to add it to the existing compiled/deployed software stacks. (weird, but it is what it is -- mostly about software supply chains)
Anyway, go look at the openapi spec and see that it is mostly just about scraping and format conversions (for now).
That didn't work for a number of reasons (cooking the books), but also network bandwidth is not fungible. Unlike commodities such as oil or natural gas, bandwidth’s value is highly dependent on specific factors like location, time, and network conditions. This variability makes it difficult to standardize bandwidth as a tradable commodity, complicating efforts to create a seamless trading market.
There are a few in the crypto/DePIN space poking at this problem. I remain highly skeptical.
I've implemented this in our workflows, albeit a bit more naive: when we kick off new processes the user is given the option to "put a human in the loop" -- at which point processing halts and a user/group is paged to review the content in flight, along with all the chains/calls.
The human can tweak the text if needed and the process continues.
It is a land grab like everywhere else.
The crypto people have already shown up, and the solopreneurs are chiming in as well.
Hopefully Bluesky’s algorithm can make the experience significantly different that people stick around.
Instagram launched a recent thing where they allowed people to reset their profile history and clean the slate.
I'm out of my depth here but genuinely interested and curious to see over the horizon.
David Tippet (formerly opensearch and now at Github)
A great podcast with David Tippet and Nicolay Gerold entitled:
"BM25 is the workhorse of search; vectors are its visionary cousin"
It is incredibly sad that companies and executive leadership teams are more devout to cloud and long-term contracts than their people. This is a function of poor procurement and short-term IT strategy, sure. More on that later.Every day we see the hits come in. 15% here, 20% RIF there, it is relentless. Eventually these places get down to a skeleton crew.I wonder, though, when many of these...
I dont know who that would be.
Multi-sided marketplaces are really hard to bootstrap, but with the right offering to the right people— it could be a win.
So it's been a decade-long round-trip from IC to management to senior manager back to IC.And in the time you see some skills develop while others atrophy. And some new skills appear on the market that I'm shallow in.In this case that could be Golang and Rust. (Lets not talk about how I feel about the Javascript ecosystem)But, man, it is hard to let go of the cozy warm and lazy blanket Django...
Hey HN!I'm working on some early demos that will support much better async communication for Developers, Engineering Managers, and Product people.We are all too familiar with the empty tickets that were used more as breadcrumbs rather than actual context, criteria, and purpose for getting work done.I want to solve that as well as help non-technical product managers be able to give sufficient...
but seriously, this is a neat idea. and kudos to OP for building a full prototype -- this is the level of geekery I show up for.
I remember the days of T9 on the old Nokia phones. I was so good that I didn't have to look down at the screen.
My favorites were fixed in my phone. I knew how many down clicks on the button would land on the right friend/family member. I could literally send messages from my pocket.
And yes, I admit -- I did engage in texting while driving. And this is the part where I justify it -- "but I had eyes on the road the whole time!"
Oh! and there was old skits on late nite where people woudl compete with the old morse code guys.
Senior Python/LLM/Django Engineer & Technical Leader
"Let's do this" attitude + proven track record
└─── IMPACT
• 40K+ nodes/validators (petabyte-scale)
• $1M+ annual infrastructure savings
• 150B+ messages/month (200M+ MAUs)
└─── EXPERTISE
• Django, Python, LLMs, MLOps, Automation
• AWS/GCP/Azure, K8s, Terraform
• PostgreSQL, Vector DBs, Observability
└─── LEADERSHIP
• Technical architecture & strategy
• Team mentorship & process design
• ISO 27001, GDPR compliance
┌───────────────────────────────────────────────┐
│ Linkedin: https://linkedin.com/in/heysamtexas │
│ Github: https://github.com/heysamtexas │
└───────────────────────────────────────────────┘Having all that in place really changes my attitude from "playground on my machine" to "put my name on it and ship it." -- it makes me proud.
I'm heavy on python, so there are a few "aftermarket" bolt-ons:
- ruff for linting and formatting - flit for package management (will experiment with uv in the coming days) - commitizen for commit formatting - pyright for type checking (but not for Django projects) - pycharm is where all the magic happens - pre-commit for commit hooks and final checks before it get shared to the repo
I don't mention all the CI/CD stuff here because that is a separate thing.
Building up this stack took a while to onboard into. Taking it on all at once would be overwhelming and leave me bewildered.
It is nice to have claude or chatGPT around to have around for going into the weeds. However, "trust but verify" -- these LLMs will hallucinate, so you should check the original documentation.
The overall impact has been that I now use template repos where I can spin up a production-ready codebase with all the fixins. Not only that -- it is also ready for others to consume in a predicable fashion.
I still need to write docs, use cases, and things like that. But having this in place give me the opportunity to run faster, ship faster, and revisit old work with a confidence that was not there before.