|
hot take: frontend dev is not as legitimate as backend The further I get from pjarvascript the more legit I am.
|
#
?
Oct 6, 2016 16:13
|
|
|
|
| # ? May 25, 2024 16:07 |
|
|
Shaggar posted:lol
|
|
#
?
Oct 6, 2016 16:16
|
|
|
Finster Dexter posted:hot take: frontend dev is not as legitimate as backend https://twitter.com/steveklabnik/status/783322064497307649 and then the real  https://twitter.com/steveklabnik/status/783323004856045568
|
|
#
?
Oct 6, 2016 16:17
|
|
|
create table facts ( id text not null, attr text not null, val text not null ); there i fixed all ur database problems
|
|
#
?
Oct 6, 2016 16:19
|
|
|
tef posted:just one thing: don't use auto increment, use uuids why? i'm genuinely curious and i can't recall hearing about that before. or think of any advantages uuids would have off the top of my head
|
|
#
?
Oct 6, 2016 16:22
|
|
|
HoboMan posted:
e: i don't know why that one quote is hosed up. looks like a bug in the forums because it's this: [quote="tef" post="465028358"] HoboMan fucked around with this message at 16:33 on Oct 6, 2016 |
|
#
?
Oct 6, 2016 16:30
|
|
|
VOTE YES ON 69 posted:https://twitter.com/steveklabnik/status/783322064497307649 plangsplaining
|
|
#
?
Oct 6, 2016 16:32
|
|
|
Deep Dish Fuckfest posted:why? i'm genuinely curious and i can't recall hearing about that before. or think of any advantages uuids would have off the top of my head * don't rely on your database for pkey uniqueness * keys are unique across tables, databases * which makes it much simpler to shard across multiple databases * you can layer (partial) sequencing on them if you really want to
|
|
#
?
Oct 6, 2016 16:37
|
|
|
this guy is putting "people are lovely to front end developers" and "there's too much churn in front end" against each other but... both are true??
|
|
#
?
Oct 6, 2016 16:39
|
|
|
HoboMan posted:yeah we got guids for most primary keys (except the tings our last dba built out is all autoincrementing ints since they hated guids because they are annoying to type out) index fragmentation means the index content is spread out across more pages on disk. When sql server needs to read a section of indexes it does it pages at a time so the more fragmented your indexes are the more pages they're on and the more disk sql server has to read. optimizing index storage for uniqueids is hard because theres a shitload of possible values and they aren't sequential. that means they can fragment your index pretty easily. on the other hand, sequential auto increment ids are the easiest possible index to predict so they make for totally unfragmented indexes. So why not always use auto-increment ids? Cause if you're doing active-active replication you can get collisions on the auto incremented values. one solution is to set auto increment ranges and another is to use guids. guids is more scalable from a design standpoint because you don't need to setup auto-increment ranges on every database instance, but the downside is index fragmentation. However! if your entire index is already in memory this is totally irrelevant! The performance hit is on the initial disk read to get the pages into memory. So the best solution is get more ram and keep everything you can in memory and never go to disk ever.
|
|
#
?
Oct 6, 2016 16:45
|
|
|
HoboMan posted:e: i don't know why that one quote is hosed up. looks like a bug in the forums because it's this: that doesn't really tell me why you'd want to use uuids instead of autoincrements, though not using uuids for clustering indices definitely makes sense to me though: the clustering index determines the physical layout of entries on disk, so just adding things to that table will effectively have you do random inserts all over disk. it also means creating new pages whenever you try to insert something in a full one, leading to more partially full pages all over the place and worse disk usage, instead of the tightly packed full pages you'd get from an autoincrement clustering index edit: gently caress, beaten by shaggar
|
|
#
?
Oct 6, 2016 16:45
|
|
|
the biggest advantage of guids over auto increment ids is that the guids are going to be unique across database instances
|
|
#
?
Oct 6, 2016 16:47
|
|
|
FamDav posted:* don't rely on your database for pkey uniqueness eh, ok, that does make sense. i wasn't really thinking about things beyond the "single machine classic rdbms" realm, i guess
|
|
#
?
Oct 6, 2016 16:50
|
|
|
Mr SuperAwesome posted:re ide and gitchat just use git at the command line and vim, its p great i've been trying to learn it for the last few days and i have such a hard time with those really interactive emacs modes. just buffers going everywhere and the buffers i want not being sticky and so on. i actively trying to get better because i switch between projects frequently and having to switch to a shell in $PROJECT_DIR just for git is getting old
|
|
#
?
Oct 6, 2016 16:53
|
|
|
Shaggar posted:index fragmentation means the index content is spread out across more pages on disk. When sql server needs to read a section of indexes it does it pages at a time so the more fragmented your indexes are the more pages they're on and the more disk sql server has to read. Or add a separate autoincrement column that is configured as the clustering index and you get the best of both worlds.
|
|
#
?
Oct 6, 2016 16:54
|
|
|
lol at this loving truth table for javascript holy poo poo
|
|
#
?
Oct 6, 2016 16:57
|
|
|
lolquote:Why would you ever want && and || to give back anything but a boolean? After working with this for a while, though, you will likely realize you would not want it any other way. hell yeah i want it another way. i want option types and sensible behavior of logical operators. wtf, our internal training is 100% dedicated to ensuring you drink the koolaid on whatever we use.
|
|
#
?
Oct 6, 2016 17:04
|
|
|
javascript is very very very bad and front end web "developers" are definitely retards you can and should look down upon
|
|
#
?
Oct 6, 2016 17:06
|
|
|
nope everything is equally good or bad and there are only opinions and some people are really mean
|
|
#
?
Oct 6, 2016 17:08
|
|
|
nope. javascript is objectively bad and front end web "developers" have been promoting it and its bad conventions for like 15 years now
|
|
#
?
Oct 6, 2016 17:08
|
|
|
eschaton posted:I know a couple people with the Spectrum hardware, people without the GCR model had to do weird things to talk Macs into formatting disks as 720KB MFM with HFS and copy software onto them yeah and iirc sheepshaver is descended from the Amiga mac emulators I downloaded the Spectre manual and wow, it was all done by one guy disassembling the macintosh ROM in his basement
|
|
#
?
Oct 6, 2016 17:11
|
|
|
Shaggar posted:nope. javascript is objectively bad and front end web "developers" have been promoting it and its bad conventions for like 15 years now yeah If I was in a room with shaggar and javascript and had a gun with one bullet, I'd shoot javascript close tho
|
|
#
?
Oct 6, 2016 17:11
|
|
|
dear god so the de-facto hdl is a php-tier mess of gotchas within gotchas and the entire field is full of tiny bug childs who throw a tantrum at any attempts to make tools whose design isn't actively malevolent
|
|
#
?
Oct 6, 2016 17:16
|
|
|
LeftistMuslimObama posted:lol at this loving truth table for javascript holy poo poo thing is it's not too different from most of the other p-langs
|
|
#
?
Oct 6, 2016 17:19
|
|
|
Finster Dexter posted:thing is it's not too different from most of the other p-langs then they deserve all the hate they get. i tolerate and trick myself into enjoying mumps cuz its my job, but any time ive set out to do something and the only library out there to do it has been for python, i spend about 5 minutes before i decide "gently caress it ill roll my own thing in a real language".
|
|
#
?
Oct 6, 2016 17:22
|
|
|
I think the antipattern of using NULL as false in database design is from idiot php devs that grew up learning that null == 0 == false.
|
|
#
?
Oct 6, 2016 17:24
|
|
|
what the gently caress? how can this be common enough to be deemed an antipattern? what possible reason would you have to do this when there's a boolean type and null is handled differently from every- ah gently caress it why am i trying to make sense of this
|
|
#
?
Oct 6, 2016 17:29
|
|
|
Arcsech posted:Itym tcl scripts Wrote some TCL yesterday. Writing some more today. 
|
|
#
?
Oct 6, 2016 17:32
|
|
|
Deep Dish Fuckfest posted:what the gently caress? how can this be common enough to be deemed an antipattern? what possible reason would you have to do this when there's a boolean type and null is handled differently from every- ah gently caress it why am i trying to make sense of this It's in the SQL Antipatterns and I've seen it a lot in bad database schema quite a lot. I think they get tripped up because in MySQL there was no boolean type, you typically just used tinyint. They added aliases of bool and boolean that were just alias for tinyint. I think MS SQL doesn't have boolean, only bit. So, if you are really terrible and don't know what a BIT is, then there you go.
|
|
#
?
Oct 6, 2016 17:34
|
|
|
I bet a lot of these other antipatterns can be traced to lovely LAMP devs. Source: My junior dev days were as a LAMP dev. Now I'm a lovely .NET dev.
|
|
#
?
Oct 6, 2016 17:36
|
|
|
bit is displayed as true/false in sql management studio. idk why they didn't call it bool other than dumb consistency with other numeric types.
|
|
#
?
Oct 6, 2016 17:37
|
|
|
Finster Dexter posted:I bet a lot of these other antipatterns can be traced to lovely LAMP devs. I would hazard a guess that most lamp devs never leave lamp or they go into even worse worlds like node and mongo and ruby.
|
|
#
?
Oct 6, 2016 17:38
|
|
|
Shaggar posted:I would hazard a guess that most lamp devs never leave lamp or they go into even worse worlds like node and mongo and ruby. I think you are very accurate on this. I was definitely headed down that dark path. I happened to get my first senior dev job and I knew enough about MVC (the design pattern) and enough C# to get through the technical interviews and they hired me for .NET stuff. I will never ever ever go back to LAMP poo poo. I check in on old php co-workers and it's still the same old poo poo, PHP 5, MySQL, etc.
|
|
#
?
Oct 6, 2016 17:41
|
|
|
mysql is so bad at everything it does i dont know why anyone uses it anymore
|
|
#
?
Oct 6, 2016 17:44
|
|
|
CRIP EATIN BREAD posted:mysql is so bad at everything it does i dont know why anyone uses it anymore I'm using it because idiot devs 5 years ago didn't know better and now there's that many years of web forms built on top of it. fml Thankfully some of our platform is on SQL Server, too. I think anymore, people go to Postgres when they want a FOSS db.
|
|
#
?
Oct 6, 2016 17:46
|
|
|
postgres is the best foss db im not really familiar with sql server enough to say one way or another oracle is objectively the worst
|
|
#
?
Oct 6, 2016 17:52
|
|
|
Oracle doesn't have a boolean type either (well ok, it does, but only in Pl sql, you can't query with it or store it) We use char(1) with a t or f And our ceo used -999999 for 'null number' forever ago and we're stuck with it
|
|
#
?
Oct 6, 2016 17:53
|
|
|
CRIP EATIN BREAD posted:postgres is the best foss db sql server is great because the db server is very good but you also get a lot of great add-ins under the license like SSIS which rules hardcore.
|
|
#
?
Oct 6, 2016 17:54
|
|
|
dick traceroute posted:Oracle doesn't have a boolean type either (well ok, it does, but only in Pl sql, you can't query with it or store it) 
|
|
#
?
Oct 6, 2016 17:54
|
|
|
|
| # ? May 25, 2024 16:07 |
|
|
only time i ever used sql server was i was brought in as a consultant to "speed up" a database and the devs at the company refused to show me their queries and claimed that i should be able to optimize it by just looking at the schema. they kept fighting me and i had to keep going to management to tell him that i cant do anything unless i can see what the gently caress they were trying to query. in the end i finally saw the code/queries and they were doing things like manually locking tables when they didnt need to and running recursive queries accidentally because they hosed up some for loops in code. i fixed all their problems without changing the schema whatsoever (or adding any indexes) and some devs got in trouble (and probably got the axe) not sql servers fault, but it left a bad taste in my mouth.
|
|
#
?
Oct 6, 2016 17:59
|
|