Im usually ok with some slowness, i unfortunately accept that we live in a bloated world now. But, wow there are some things now that its just awful, i want to find some of these devs and ask them how did they even let it get so bad.
home depots site is seriously one of the worst. Mobile phone that is from this year, on good wifi, and it takes many seconds to load any page, HOW!?!?
Why are we sinking huge amounts of already processed resources... yes theres cost but, thats a lot of steel, copper, brass who knows what else. So crazy and ridiculous to me
Complaining about ads is generally discouraged here because it doesn't add anything. Buy YouTube Premium if you don't want to see ads, it's pretty simple.
This is a very high quality documentary and it's not like running YouTube is free either so exactly what are you expecting?
There are plenty of comments complaining about paywalls, I never saw a comment like yours below one. But it's the same thing. Buy ft, nyt, bloomberg, youtube, whatever and spend $500 month to read a single article or watch a single video per month on that specific site. It's ridiculous and broken and it's ok to complain about it.
I just picked up a project car, and have decided to use AI as my side-mechanic and helper. I had it build a local site, which has a checklist with subtasks, note and photo abilities and parts tracker. The checklist was built up by ai based on what ive been telling it, etc. I have tuned the project ai to handle part searches, identification, and general help. I just added a trigger for things like adding notes and photos, so that when i add them, a request is fired off to the ai, and it will analyze, id, etc. Ive also given myself a way to directly prompt the ai from the site for help, instructions, diagrams, whatever. Ive got a little thinkcentre pc in the garage where the site is accessible, and its also available on my phone for pictures. Its still early in the car project itself but its already been helpful in identifying the engine, and found 2 issues i overlooked.
Also ai helped me build an offgrid setup for said garage because the garage has no power. Helped me size things out, gave me diagrams, etc. Also has already provided me with a way to setup an automatic generator startup when the battery is low. I havent set that up yet, but its in the pipeline.
I started and then abandoned a really deep circuit simulator, which was going to be able to emulate full actions and code eventually.
aaaand lastly, ive spent the last 2 months in the evenings with ai building a complex rts game in godot, its almost 1.0 ready. Sadly the ai im using has been really struggling to turn out quality 3d models, so thats probably going to be on me, which will delay significantly.
A coworker created a whole financials site, and then another coworker did the same thing, but turned it into a game. You add your real financials (age, income, stocks, etc) and then as you walk through the hall it changes your financials and allows you to see the various changes, even has life event changes, retirement age markers, all kinds of ridiculous things.
Im not one to take a horse drawn carriage except in maybe two instances, but i see the appeal as a "general tourist", the horse ride around central park is one of those touristy things that seems like you do, because youre there. That being said, i agree that its not great for the horses, and unfortunately i can understand the want for it gone.
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.
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.
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.
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.
Because it's about the journey and not just the artefact. If you're not thinking of something that's useful and preparing snippets to share every day you are not practising it. Having to come up with something stretches your imagination and critical thinking skills. What's true for the writer is true for the reader - if you just shared a simple repository with tricks, exceedingly few are going to read that, and the ones who do will forget it. Daily practise is important.
Sharing an hundred tips one tip a day has certainly more chance to be shared correctly than pointing to a page containing those hundred tips.
Personally I don't care if the guy looks for attention or not. IMO people that do care have likely some jealousy issues ("I don't want other to get more attention than I do"). Lose-lose attitude.
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
home depots site is seriously one of the worst. Mobile phone that is from this year, on good wifi, and it takes many seconds to load any page, HOW!?!?