I'll continue sharing the stuff I build or explore, and my learnings along the way :)
To give some context, I've been working remotely since the start of my career and transitioned to a more content-oriented role last year, so I never progressed beyond being a junior engineer. But I do remember the deep discussions and technical planning sessions being the most rewarding and mentally challenging.
I have seen that AI has the same tendency of over-engineering solutions when you are in the documentation phase, where it tries to scope out the entire plan before I have a clear idea of what I wish to do. So I typically begin with a simple markdown doc and disable auto-complete before reaching out for it later.
Just curious what folks think.I've personally learnt a lot and benefitted greatly career-wise from building and showcasing projects in communities like Reddit and Discord, as well as blogging about them -- even though none of my work was ground-breaking per-se.Do you folks think non-senior engineers can still build presence and gain employment opportunities this way? If not, what needs to...
I've switched to OpenRouter with the 3.6-pro model right now, but will have to play around and see if some other model works out better on the cost front.
Honestly, Qwen had spoiled me with their free plan.
I kept getting 401 'token expired' errors on my existing Qwen session. Attempting to resume it after quitting, I got: qwen resume [API Error: 401 invalid access token or token expired] [API Error: 401 invalid access token or token expired][API Error: [API Error: 401 invalid access token or token expired]] An unexpected critical error...
Since I primarily work with Notion for content creation, I never realized macOS does it by default.
This was very helpful, thank you :)
Regarding monitoring Kakfa execution times, absolutely agreed. In my previous job, monitoring Celery had helped us understand consumer bottlenecks, because we couldn't see background job traces containing the celery consumer spans. And when they did appear, they were hours late. So the entire trace took 8 hours instead of the expected couple minutes.
Happy to hear you've been enjoying OTel and Rust!
I had recently done a write-up on OpenTelemetry baggage, the lesser-known OpenTelemetry signal that helps manage metadata across microservices in a distributed system.
This is helpful for sending feature flags, parameter IDs, etc. without having to add support for them in each service along the way. For example, if your first service adds a `use_beta_feature` flag, you don't have to add logic to parse and re-attach this flag to each API call in the service. Instead, it will be propagated across all downstream services via auto-instrumentation, and whichever service needs it can parse, modify and/or modify use the value.
I'd love to discuss and understand your experience with OTel baggage or other aspects you found that maybe weren't as well-discussed.
I am curious, what are people and organisations building with web crawlers, especially since now all of them seem to have LLM support for further refining the output from crawled pages.Open source projects like crawl4ai[1] have a crazy amount of stars (~59k). This got me curious.https://github.com/unclecode/crawl4ai
From my experience generating db models/SQL schema at my last job, it did a fine job based on existing patterns and the outlined requirements. Point to note, we did optimise our AI prompts and LLM rules a lot, to the point we were able to get end to end unit tested, functional PRs out rather quickly
It feels like with AI, a lot of engineering practices that were de-facto standard have somehow been phased out. Or atleast that's the emotion I can see on reddit or on few threads in HN.That led me to this question, what are some practices you feel have been phased out over time, that should make a comeback?One off the top of my head: startups or even large orgs in general not hiring junior...
I forget that I've set it up as a PWA on my iphone many times and use apple notes, but that's also fine since it's convenient to use. But anything semi-relevant goes to my SilverBullet instance. The vim mode on the desktop version makes the mobile version feel 'gutted' through no fault of the app itself- its more a proof of how comfy vim feels (even though I'm a perennial VIM noob).
A key thing to note, git periodic sync (which backed up notes to a configured git repo) was removed as part of the v2 version. That's a bummer although there's a thread[1] on the forums with snippets for a cron job? setup. I just haven't explored it yet cause I'm lazy, gotta do it sometime.
Hope someone finds this thread useful, and can maybe spark discussion around some new shiny apps. Side note, does anyone find themselves drifting back to the good ol apple notes or whatever your phone ships with?
[1]https://community.silverbullet.md/t/running-the-silverbullet...