Details
-
Abouta geek diggin' deep
-
SkillsJava dev, Linux/UNIX sysadmin, performance engineer
-
LocationLithuania
-
Github
Joined devRant on 2/26/2018
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
It's enough until someone fucks smth up and you have to unfuck the repo. But we have ai now to hint us those fancy commands.. Idk, I'm not yet willing to invest extra time until I have to
-
@donkulator aren't they becoming 'somewhat vintage' the next day after you buy one?
-
Now I work with guys who are very eager to deliver asap, and clean code or clean architecture is not in the dictionary. And I can tell that maintaining all that crap is hell of a pita. Yes, clients are mostly startups, but in all the cases they ask for an mvp and lts maintenance afterwards. We are making major refactorings every ~9 months. It's like an mvp gets us pregnant with a slightly cleaner mvp and 9 mos later we're delivering it and a month later we start getting the feeling that yet another one is growing inside us.
I've delivered a couple of features and I'm confident noone will need to touch them for at least a year, because they are solid. In both meanings. And I'm already about to port the same things to other projects. I might as well publish them as standalone OSS frameworks.. -
For 9 years I worked in a company that promotes clean code in all the projects. I've learned it, even tdd too. Frankly, it is not shit. Following those few principles you make your architecture flexible and resilient and very much maintainable at the same time.
Clean code is rubbish for mvp/poc, I give you that [tdd - not necessarily]. But for long-term codebases it is the only way to have a peace of mind while working on it at any given time, on any given task. -
What you're asking for is waf rulesets. Have a look at nginx modsecure's owasp ruleset. They have it all. Perhaps consider parsing their rules and reusing the already hefty knowledge base?
As for the most common ones -- do consult with owasp. Some llm might summarize it for you, like retoor said -
Laziness. Weren't people lazy they would not be motivated to ease their lives with automations and inventions.
-
It's called continuous delivery.
The master-deployment thing I mean -
@BordedDev company's been pushing feature dev over maintenance stuff since ever. Maint only got atttn when feature stuff was malfunctioning.
Now since I'm full time cto, I carry some weight to shape things and readjust the maint-feat balance -
Why do you assume devs did that? It's llm coding at its best :)))
-
Set up grafana [free tier is more than enough] w/ blackbox exporter and alerting. It will hint you when shit's down. Like now, parts of snek are 404ing :)
-
@BordedDev they are both usb. Ind I double-checked, it said MB on the box
https://transcend-info.com/product/...
i didn't check block size though.. I don't usually do that after purchasing a storage device 😁
after that I nuked it all, formatted it to ext4 w/ truecrypt and copied it all into the TC container. Even w/ encryption, copying speeds were >900MB/s. And stg usage was as expected.
Windows support loss is a bummer, but then idk if I really need it 😁 everyone in our company is a linuxist there anyway -
Various utilities [pwpush, owncloud, cctv, etc], vpn server, home wifi router, plex server, multimedia hub, dropbox for temp files, firewall, pihole/dns server, meshcentral server, etc.
-
@Lensflare same here
-
Only up to a point. Then time becomes the most valued currency
-
Use protection next time 😁
-
@whimsical naah, it's been reserved the same day Irene deleted its account
-
@antigermanist you would know
-
@whimsical iirc this alias is currently parked by uyouthe. Irene has been impersonated at least twice
-
back when we still had @rutee07, @Fast-Nop, @stuxnet, @linuxxx, @Floydian / @Floydimus, @irene (the original one), @condor and a couple more, which I'm forgetting to mention... it was a good place to rant. It was an actual devRANT, not devFacebook2. You could read all kinds of absurd stories.
Now it's more of a habit to open up dR. The content is rarely any good, mostly childish posts desperately hoping for any attention -
@whimsical @wojtek322 is right. I clicked on that post initially and waaaaaaited for it to load, then I apparently misclicked on your post and didn't read again before jotting down my worthless opinion :)
-
back when we still had @rutee07, @Fast-Nop, @stuxnet, @linuxxx, @Floydian / @Floydimus, @irene (the original one), @condor and a couple more, which I'm forgetting to mention... it was a good place to rant. It was an actual devRANT, not devFacebook2. You could read all kinds of absurd stories.
Now it's more of a habit to open up dR. The content is rarely any good, mostly childish posts desperately hoping for any attention -
@antigermanist how on Earth can you miss a seat....?
I guess you have a condition that only allows you to ride a feminine bike after all. Preferably with side wheels -
Or you can do a little bit of both. Works best for my use cases.
Define high-level plans in advance with contract layers set or partially set, define epics and their DoDs, assume they will work, and split all of them into tasks, divide across teams. Let them figure out ["carve out"] the solutions. Then in the end make final adjustments to both impl and contracts and voila. All teams were creating value, client had a pretty good definition of what's going to happen, with some RnD DoDs have been achieved. -
Bear in mind muskets were very inaccurate back then. You aim for a belly and you hit a squirrel in a tree kind of inaccurate
-
Shove the ice cream up your butt and vomit your bowels out
-
Rookie [???] miskate
-
well I'm not!
There may have been a hunch of autumn blues in the early morning, as I was sipping coffee in the balcony while watching the morning sunlight playfully shining on trees' leaves and listening to lofigirl tunes, but that's about it. -
On a more serious note:
- 1 cup of warm water
- 3 reaspoons of sugar
- 1 teaspoon of salt
dissolve, drink it all, do your best to keep it down. Should start working after 30-60min.
Sacharose is split by intestinal sucrase into monomer sugars - glucose, which then feed active ionic carriers in your intestines. They carry Na from the salt into your blood stream, rapidly increasing osmotic pressure there -- water from your intestines will follow right away
grandma's recipe. Tried and true -
Use the right tools
-
Shower
