Ctrl+r is great, sometimes. History saving sucks which can make using it difficult, but i usually use it out of laziness than trying to recall a command, especially with ssh or repeated iterations requiring flipping between two settings/states. Its hard to rely on it for other things, but its still super useful.
I use history | grep quite a lot, because of the non-fuzziness with default ctrl+r. If I know exactly what the substring is, then that's great, but sometimes I also want to see the sequence around the command too (e.g. two step processes like eval ssh agent + ssh add key)
I think that "everyday" would be a stretch, but i dont understand why youd think thats annoying, someone took the time to consider helping the rest of the engineering team grow, by posting something useful.
I frequently do the same, but not everyday; only when i think its something actually useful/helpful beyond the everyday crap. Most recently, we have had a huge push to use ai (just like everywhere else), ive been getting pretty creative with it, and at this point have a well polished setup that i can give a shitty sentence on a problem, not only does it understand the task, but theres a full ticket->branch->work->pr review->ready comment flow that it uses. My team also uses ai but they havent quite wrapped their head on ways to really work with it. I have built and shared a number of helpful things with the team to try and help them grow. One such thing was a doc i had my ai instance write, based on how ive been using my setup. This alone has started to get the rest of the team up to where i am.
My team doesnt share the same types of things i do, but they still share helpful things.
Call it what you will; I think if youre not helping your team grow by providing insights and helpful things, then youre not the kind of person i want to work with.
I rather think the opposite. People who share tips and hacks are genuinely trying to help others, while people who hoard information are competing on an individual basis without regard for team.
Please take this in good faith, as I hope your own post is, but I interpret the thread you're replying to as focusing on the "everyday' part.
Share knowledge? I don't think anyone here is arguing against that in any way (or conversely arguing for hoarding knowledge).
The concern, one I share, is where the sharing has to happen publicly "every day" - so no matter how trivial, useless, niche, overly-specific the tip is (whatever, the list isn't exclusive), someone shares it.
That's the part that's not sharing knowledge for the benefit of others, but rather self-serving. I might even go so far as to say self-serving doesn't even need to be selfish; the person might genuinely believe they're doing good, but even there, self-serving.
TLDR: Share your knowledge, don't make sharing something every day, even when you don't have something valuable to share, your target.
PS - if this note irks anyone (are routine maxxers a thing?), make the goal to learn something every day, then share where appropriate.
> Treating a public channel like ye olde facebok wall? Mildly annoying.
Every team/department/org/whatever should have channels everyone should subscribe to, and channels individuals set up that are optional for everyone. The appropriate way to handle this is for the OP to write a few tips once in a while in the public channel, and if people seem to like it, announce that all future tips will be in that channel.
We work in very different places. Wherever I've worked, the guy who knows all these tricks is not the guy getting promoted. Senior management doesn't care about your shell or scripting skills. Sure - they make you more productive, but at a very local level (may be good for a single promotion early in your career).
Most senior engineers I've worked with have forgotten all these tricks, and they actively tell you that while you should try to get better at these things, career gains lie elsewhere. Focus on things with higher impact.
Why just one each day then? Why not a shared knowledge base? Do you start with a "bag of tricks" and then hand them out one by one each day to remind people you're the guy with the bag of tricks?
"Oh, yeah, I know a cool trick, but y'all have to wait until tomorrow to find out what it is."
"Look! It's a way to evaluate SQL expressions with a select with a from! Oh, you already knew about it?"
I have nothing against sharing knowledge, especially when seeing someone else do something that can be done better. But just leaving daily breadcrumbs to remind people you're the guy that teaches random trivia feels like attention seeking.
I don't think that's a generous way to interpret it.
I see it more as: every day they will go on the slack channel and pause, wondering "Is there a neat trick I've learned or used recently?" then they share it. It's like a ritual to remember that you can share things because it's easy to forget other people don't work the same way you do. Writing it all at once is difficult (you have to remember a lot of stuff at once) and it tends to go unread.
I also think every single day is a stretch, but it's nice to pause once in a while to think about how you could help other people with something you've learned.
Artifactory (jfrog) is a laughably bad openapi spec setup. Ive even called them out on it. "we provide an openapi spec".. well its technically sort of true, except if you actually want that spec, theres no way to actually sanely grab the spec. And, when you do finally manage to get it, its incomplete, full of badly defined objects, and ends up being utterly useless. Oh and did i mention that their spec ends up being some 35MB even after beating it to death and trying to shape it up. And, while they have /v1/ pathing, you guessed it, every app version changes the spec somewhere, and theres no v2 etc.
Ive concluded that unless the person is 100% passionate about openapi, the spec is a mess, and compatibility is a joke contained in an afterthought
Did not watch the video, but the title immediately reminded me of an incident at a past job.
Was a devops engineer, whole app team (who only ever wrote nodejs) got fed up with pacemaker/corosync. "we are going to write our own" they said, and proceeded to try to whip out nodejs for it, i laughed and laughed, and then told them fuck no, dont do it.
Someone forgot to set the brake in their car, rolled into the back of my dads 70ish pickup. It rolled the width of a parking row, on fairly flat surface. The car had no chance obviously, but it was pretty funny seeing the damage; bumper and fender, not just a minor one you could slap out with a good fist slam either. There was zero damage to the truck
Can you elaborate on this some? Afaik insurance is the only thing they would accept. I think insurance is generally a nasty scam so anything to get away from it would be pretty neat
You have to deposit $75,000 to the DMV and if you get in an accident where you're at fault you will also be on the hook for damages beyond that. You can also get a surety bond for that amount, instead of doing a cash deposit.
It used to be 35k but it was increased in late 2024 (which is good because it hadn't increased since the 70s).
But to do that you really have to hate insurers or be uninsurable. Because realistically putting that 75k in a basic HISA will yield enough interests to pay for regular car insurance and you get to keep your 75k.
Thats quite a lot more than i expected, i just have never had a good experience with insurance, everything is a long drawn fight. Probably not worth it unless under specific circumstances
Interesting, something that wasnt covered on your site, although the inverse is. I sometimes get the opposite of the troxler effect, the center of my vision goes "black" while the edges stay visible. The black center gets "worse" if my eyes stay still, and is usually accompanied by a halo of various colors. It goes away after a few minutes. Ive never found a consistent trigger for it, sometimes light changes will do it (going from outside to inside) but not consistently, it can also just seemingly randomly happen
Denvers original airport was built in the "middle of no where", for noise reasons. Continue on for 30 years and lots of housing built up around it. People start complaining about noise. City decides to move the airport. Moves it 30 miles away, in the middle of no where (now DIA). Yep, you guessed it. People start building close to the airport, and then complain about the noise. I fully expect it to move again in 15-20 years
Laguna Seca, a fairly famous California race track, was opened in 1957 built out in the middle of nowhere. In 2024, people that moved near the racetrack sued to get it shut down.
I know there's some level of caveat emptor when buying a house, and realtors are guaranteed to not have any showings when it's noisy, but maybe just spell it out and the purchaser needs to be made aware.
> Laguna Seca, a fairly famous California race track, was opened in 1957 built out in the middle of nowhere. In 2024, people that moved near the racetrack sued to get it shut down.
“I swear, the race track just materialized out of nowhere!” -A wealthy liar living in California
I assume it was dismissed immediately since Laguna Seca is almost 70 years old.
I have gotten my ai setup to learn quite a bit. As i work with it, if something was encountered that would be useful to remember, i literally just say "save this into your learnings/long term memory". It writes a markdown doc for itself and a note elsewhere for context. Between the memory and rules, its been pretty nice. I touch many things at work and i can pop open a new session and say "project x needs a b c" or "project y had this issue <issue>" and it knows where to go, what im referencing and things to fix. I dont even have to be precise or ultra descriptive.
with this ive been able to, with some minor adjustments and "oh that would be a good feature" additons, oneshot a flask app at work with everything ready for oidc, ldap lookups, bunch of other stuff - from a single 3 sentence paragraph.
With some rules in its configuration (more markdown its written by it for it, at my guidance of "always do x and remember this for all sessions"), it has a whole flow and i barely have to feed it anything to get out useful results quickly.
I will say though that the ai operates however the user says, so if you dont take steps to ensure survival of info at the start of using ai (or even from now on as a fresh session), youll get mixed results, but you can shape it and mold it into amazing flows that do remember
reply