If you want to win an election, Google might be arguably the worst possible company to directly threaten, not gonna lie.
Pretty sure uf they wanted to, they could wbd your political career with any manner of ways.
I bet trump’s Google search history would be devastating if they threatened him with releasing it to the public, lol.
She has so much more sway than The Chicks had at the time, by such a huge amount.
The Chicks were already controversial, and had always been so.
But Dolly is the fucking queen of country, people revere her.
How many Dixie Chicks lookalike competitions were you seeing right before their career nosedived?
Dunno why ppl are down voting you, this is 100% the way.
Architecture as code is amazing, being able to completely wipe your server, re-install fresh, and turn it on and it goes right back to how it was is awesome.
GitOps version controlled architecture is easy to maintain, easy to rollback, and easy to modify.
I use k8s for my entire homelab, it has some initial learning curve but once you “get it” and have working configs on github, it becomes so trivial to add more stuff to it, scale it up, etc.
Why is it that blatantly lying about your political opponent and actively spreading clear disinformation that is easily reputable isn’t penalized?
And I don’t want like “cuz capitalism” zero effort responses, I’m wanting to know from an actual legal complexity standpoint what would go wrong if this was made illegal.
The fact it’s so clearly provably as a false claim by countless directions, it should be an open and shut “you spread obvious disinformation” and at least a notable slap on the wrist should occur each time.
Why can a candidate just go and openly lie and say whatever without penalty, legally? Shouldn’t this be under something like Libel, defamation, etc?
Shouldn’t Kamala’s crew be able to take Trump to court right now for defamation?
Might wanna read it again, it’s right there :)
The best architectures, requirements, and designs emerge from self-organizing teams.
It’s an incredibly critical part companies love to completely ignore.
If you assign devs to teams and lock em down, you’ve violated a core principle
And it’s a key role in being able to achieve these two:
Agile processes promote sustainable development.
And
The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
This is talked about at length by the likes of Fowler, who talk about how locking devs down us a super fast way to kill sustainable development. It burns devs out fast as hell.
Note that it’s careful not to say on the same project
That’s actually a pretty important part of its original premise.
It’s a big part of why scrum meetings were a thing, as the expectation was any curious dev could just join in to see what’s up, if they like.
Not tying devs down to 1 specific thing is like the cornerstone of agile, and over many years of marketing and corporate bastardization, everyone had completely forgotten that was literally the point.
The whole point of the process was to address 2 things:
That client requirements can’t easily be 100% covered day one (But you still need to get as many as you can!)
To avoid silo’ing and tying devs down to specific things, and running into the one bus rule (“how fucked would this project be if <dev> got hit by a bus?”)
And the prime solution posited is to approach your internal projects the same way open source works. Keep it open and available to the whole company, any dev can check it out, chime in if they’re familiar with a challenge, etc.
One big issue often noted in non-agile companies (aka almost all of them) is that a dev slent ages hacking away at an issue with little success, only to find out far too late someone else in the company already has solved that one before.
An actually agile approach should be way more open and free range. Devs should be constantly encouraged to cross pollinate info, tips, help each other, post about their issues, etc. There should be first class supported communication channels for asking for help and tips company wide.
If your company doesn’t even have a “ask for help on (common topic)” channel for peeps to imfoshare, you are soooooooo far away from being agile yet.
I’ve literally never actually seen a self proclaimed “agile” company at all get agile right.
If your developers are on teams that are tied to and own specific projects, that’s not agile.
If you involve the clients in the scrum meeting, that’s not agile.
If your devs aren’t often opening PRs on a variety of different projects all over the place, you very likely aren’t agile.
If your devs can’t open up a PR in git as the way to perform devops, you aren’t agile.
Instead you have most of the time devs rotting away on the sane project forever and everyone on “teams” siloed away from each other with very little criss talk, devops is maintained by like 1-2 ppl by hand, and tonnes of ppl all the time keep getting stuck on specific chunks of domains because “they worked on it so they knpw how it works”
Shortly after the dev burns out because no one can keep working on the same 1 thing endlessly and not slowly come to fucking losthe their job.
Everyone forgets the first core principle if an agile workplace and literally its namesake us devs gotta be allowed to free roam.
Let them take a break and go work on another project or chunk of the domain. Let them go tinker with another problem. Let them pop in to help another group out with something.
A really helpful metric, to be honest, of agile “health” at your company is monitor how many distinct repos devs are opening PRs into per year on average.
A healthy company should often see many devs contributing to numerous projects all over the company per year, not just sitting and slowly be coming welded to the hull of ThatOneProject.
Harpoon is pretty much just tabs, but, without the actual visual ui of tabs, from my experience.
You pin a specific buffer, and can jump back to it, but unlike normal markers it persists between sessions and has a couple other nuances to it.
It pretty much works like tabs do though.
Yup, I usually have it set to the slowest setting when typing.
I find I work much better and can think clearer while walking, as it keeps the blood flowing and makes me feel more awake and engaged.
If I have a tough problem I’m trying to work through I turn the speed up to a faster pace and sorta just work through it in my head while speed walking, often this helps a lot!
During meetings when I’m bored I also turn the speed up a bit.
I often get around 10k to 12k steps in a day now.
Note I don’t stay on the treadmill all day long, I usually clock a good 4 hours on it though.
Then I take a break and chill on the couch with my work laptop, usually I leave my more “chill” tasks like writing my tests for this part, and throw on some Netflix while I churn all my tests out.
Highly recommend it, I’ve lost a good 15ish lbs now in the past year since I started doing it, and I just generally feel a lot better, less depressed, less anxious :)
I have heard of jupyter but am not familiar with its nuances.
But doing python dev with neovim is very doable, it uses the same LSP I think.
I personally have a dedicated dev machine running debian that has everything on it, including nvim configured.
I SSH into my dev box from other machines to do work, because neovim is a TUI it “just works” over SSH inside the terminal itself, which is what I like about it.
It feels good to just
tmuxinator my-project-nameAnd boom, 4 tmux tabs pop open ready to go in the terminal:
And I can just deep dive into working asap in just those 2 steps, it feels very smooth.
I often can even just do tmux a (short for attach) to just straight re-open whatever session I last had open in tmux, instantly jumping right back into where I left off.
From my experience the only big changes I’d say I made overtime are:
Font size bumped up
Switched to neovim from visual studio, which took like a year to relearn my entire workflow (100% worth it though)
Switched from multiscreen setup to one single big screen (largely due to #2 above no longer needing a second screen, tmux+harpoon+telescope+fzf goes brrrr)
Switched to a standing desk with a treadmill, because I became able to afford a larger living space where I can fit such a setup.
If I were to do this meme though it’d mostly be #1, there just came a day when I had to pop open my settings and ++ the font size a couple times, that’s how I knew I was getting old.
but the best way to avoid getting them is still to just avoiding stupid shit.
This is fine and dandy on a personal pc, but in a work environment you are now being actively targeted by malicious actors if your company is a good target.
Constantly.
So once you are in that zone you do need some fast acting reactive tools that keep watch for viruses.
Nowadays it’s less of an issue with docker and whatnot.
Just set the image to refresh every night at midnight and if they tried to make manual changes it’ll just revert back to its original state at midnight.
Customers don’t really get direct access to deployed code now, it’s buried under like 4 layers of abstraction on most CDNs now.
Simply deploying to azure already smears multiple layers of access control and RBAC overtop that it’s hard enough for me, the dev, to answer the question if “what is actually deployed atm?”, let alone for the customer to get in their and meddle.
There aren’t standardized screens for smartphones, as the inside of the screens typically has a bespoke aluminum chassis they are adhered to as part of their construction.
And since every single phone model has different insides, every screen is bespoke to its model.
You have to look on ebay for your phones screen model.
If you look for ones with a couple dead pixels they are pretty affordable though.
I broke this down in my post.
For a document up is back (the top is the start), and down is forward (we read top to bottom)
Left is also back, and right is forward.
We read left to right, and top to bottom.
Thus, I also associate left with “back” and right with “forward”
Thus j and k are backwards.
J is left and thus “back”, so it should be up.
K is right and thus forward and should be down.
For casual users I typically recommend using Cinnamon Desktop, it’s the most Windows-esque UI and will be the easiest for them to pick up and use.
I roll with Cinnamon on Ubuntu and it’s been extremely painless, very simple to get stuff do and shit just works.
I’m wondering if there was some other popular interface for some other device (elevators perhaps?) That had Down on left and Up on right.
Since for an elevator, up is forward and down is backward…
And I wonder if they copied from that order, not thinking about (or remotely expecting) the UX of how down on left would fuck people up for countless years to come.
That wasn’t my question lol, I know why they used hjkl, I asked why they made j vs k backwards.
J should have been up and K should have been down, but they have them flipped for no sensible reason.
What I want to know though is why the hell did he paint j as down and k as up.
That has always seemed backwards to me.
Left is back, and up is back. Right is forward, and so is down.
We read left to right, and top to bottom.
I constantly instinctually press K to go down, since it’s the right key, and down is “forward” in the document, but nope… it’s backwards and I go up instead.
Several months of using nvim and I still fuck this up everytime. Whhhhyyyyy
I use Hugo, it’s not super complicated.
You basically just define templates in pseudo html for common content (header, nav panel, footer, etc), and then you write your articles in markdown and Hugo combines the two and outputs actual html files.
You also have a content folder for js, css, and images which get output as is.
That’s about all there is to it, it’s a pretty minimalist static site generator.
Hosting wise you can just put it on github pages for free.