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
-
ColdFire should pound sand:
@coldfire Na; I back up my programming drives and keep that computer offline.
However: what you described: deleting the existing partition, and then repartitioning with a new partition, which is 1 MB less than the old one: would be recoverable via the linux photorec program.
What I or os described: overwrighting using dd or shred; would not leave (easily) recoverable data. It would also take many hours for 16TB.
So how long did your hack last? A few min? Or many many hours?
That's what I thought. Pound sand.
> https://devrant.com/rants/9171521/...
5 -
> ticket comes, new feature is requested
> create the new feature from scratch. Code is neatly splitted in files and methods, each with clear responsibilities
> every method is documented, there are clear service layers for the business logic, which resulted in controller having 10 lines of code, give or take
> commit the whole code, everything works
> check the develop branch today, team leader littered business logic in the controllers because "the codebase is a mess anyway"
14 -
The postcard I got from dev to back from when I was a part of it.
Let’s make sure 2020 is special indeed. Aged like milk.
4 -
This is the result of 2 days of investigation. The diff between the commit that works and the one that doesn't.
So yesterday morning, I wake up, I'm told that the deployment from the day broke my tool. Good thing nobody was using it, anyway, I checked that I could reproduce it. It's only when deployed, I cannot reproduce it locally. I used netlify to start digging. I could pinpoint the problem to a line that was adding a key to an object:
const newState = { ...state, [key]: value }
So for non-JSers, it takes all the keys from object State and sets the key 'key' to value. You would expect newState to have the same number of keys as state, or one more, right?
But not anymore for some reason, newState now had only one key. The spread operator just went away with transpilation.
So I started questionning my sanity, and I migrated the whole fucking thing to vite (newer framework, this project is still using CRA). I still get an error, only in production.
But i still fucking need to deploy this simple change they ask me. So I start breaking down the commit that is responsible for the change. I mock the function. Still breaking. I comments out my changes. Still breaking.
At the end, I could pinpoint the error to this line. And yes, I'm questionning my sanity, but I have two commit that I can deploy to prove it. For the record, trailing commas have been in js since ES6 and I'm using all the others ES6 feature so there's no reason for this one to fail in the builder while the dev server is working fine.
There is a stupid fucking glitch in deployment and I'm gonna fnd that stupid glitch and destroy it.
45 -
Check out my retrospective on dR Community Server (Discord guild)!
https://kbin.melroy.org/m/drbboard/...
It's the story about our devRant meetup back in October 2020. Hope it will bring you a little tear to your eye. 🥲
15
Top Tags
Testing on prod without getting the whole world to collapse