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
Search - "fk y'all"
-
I just got told on a video meeting that I am far too pretty to be a developer.
To be fair, I am well aware of this, most devs I have met on the wild are some ugly ass motherfuckers.
I is a pretty ass mfker.41 -
Some of y'all talk way too much shit about web development tools/libs without being web devs yourselves......
I don't know enough about OS development to talk shit, you see me doing it? no
fk me I am getting so fucking fed up with this community, it used to be cool rants about the shit that we go through, now is just pop wannabe dev ranting meme bullshit39 -
I wanted to take a minute from y'all sucking on each other's dicks regarding language/tech-stack/os/editor wars to mention that Netflix just premiered Saint Seiya(here in the U.S don't know about the rest of the world) and it is pretty sweet.
Evangelion is in it as well, so if you've never had the chance to watch it and would like to well there is a nice chance :D
BTW bets are on: at least 1 or 2 fgits will say some shit about Netflix.1 -
Im creating a "settings" functionality of sorts, unique per "account"
Ideally I'd create a new table, FK it with the Accs table with each Setting variable being a column
But im also inclined to just turn it into a JSON and not bother with N columns for it specially since arrays are involved in the settings
Could version it to ensure that if Settings change on code-level, old accs with old settings dont get fucked up
Now this is a pet project so im free to experiment, not bound by high level design documents
What do y'all prefer/recommend? JSON<->Settings Obj or plain old Table/column with FKs9