|
DONT THREAD ON ME posted:also this will be my last post about my girlfriend.  ?
|
#
?
Jan 25, 2019 01:05
|
|
|
|
| # ? Apr 28, 2024 05:36 |
|
|
air fryers are garbage. source - my wife wanted an air fryer and we got one and it's just a loving convection oven raaaaaa
|
|
#
?
Jan 25, 2019 01:29
|
|
|
air fryers are just ovens
|
|
#
?
Jan 25, 2019 01:30
|
|
|
Fatty Crabcakes posted:Do you really deep fry that many things? yes
|
|
#
?
Jan 25, 2019 01:34
|
|
|
Shaggar posted:air fryers are just ovens you should try paying 1000 dollars for a dyson air fryer, it will redefine how you think about frying
|
|
#
?
Jan 25, 2019 01:52
|
|
|
the wife asked me if she should learn to program, before realising that she likes people and solving actual (rather than invented) problems
|
|
#
?
Jan 25, 2019 01:56
|
|
|
Shaggar posted:air fryers are just ovens correct
|
|
#
?
Jan 25, 2019 01:59
|
|
|
air fryers are a sandwich
|
|
#
?
Jan 25, 2019 03:17
|
|
|
We use our air fryer all the time. It's awesome.
|
|
#
?
Jan 25, 2019 03:24
|
|
|
DONT THREAD ON ME posted:ctps: girlfriend wants to learn to program and i really hope it sticks because i think we'd be a good programming team that quote about wherever your relationship is going it will get there faster on a tandem bicycle except programming
|
|
#
?
Jan 25, 2019 03:59
|
|
|
DONT THREAD ON ME posted:a long time ago i was telling her about how every programmer at some opint has had to remove the word 'butt' from their code. i tried to explain it but she just didn't understand why. we work with a closed-captioning format called EBU-TT and its identifying enum value is ctEBUTT getting to leave some of the butts in the code pleases me greatly
|
|
#
?
Jan 25, 2019 05:18
|
|
|
DONT THREAD ON ME posted:ctps: girlfriend wants to learn to program and i really hope it sticks because i think we'd be a good programming team Krankenstyle posted:i dont really care if its ugly as long as it works...
|
|
#
?
Jan 25, 2019 06:19
|
|
|
ugh this new offshore dev is making GBS threads out mvc code that manually builds urls to pass parameters then uses piles of if statements to decompose them including the always ridiculouscode:just pass your loving params as a form and bind the objects ffffuccckkk
|
|
#
?
Jan 25, 2019 12:19
|
|
|
it is loving shameful that me, someone who was never even hired as a programmer and bases all the knowledge off yospos, is in a position to effectively teach our supposed "proper" developers how to do their jobs the curse of offshoring strikes again 
|
|
#
?
Jan 25, 2019 12:22
|
|
|
Powerful Two-Hander posted:it is loving shameful that me, someone who was never even hired as a programmer and bases all the knowledge off yospos, is in a position to effectively teach our supposed "proper" developers how to do their jobs Don't have to offshore for that kind of quality, I was code reviewing a task to duplicate functionality from some a public API into a private one. His first pass was to simply copy and paste one class into the other one, I told him that was a bad idea, the code in both classes is the same it just matters where it's called from. So he replaced it by an effectively empty class instantiating an instance of the other one and calling the methods in it. What the christ?
|
|
#
?
Jan 25, 2019 12:59
|
|
|
tired: conform to a schema wired: just ignore it galaxy brain: edit it a bunch, send data conforming to that, and then not tell anybody until i have to go debug loving parse errors
|
|
#
?
Jan 25, 2019 13:02
|
|
|
c tp s: i love unannounced major infrastructure changes
|
|
#
?
Jan 25, 2019 13:43
|
|
|
Fatty Crabcakes posted:If you choose the right framework and stick to backend development, dependency injection shouldn't be something you have to deal with. lol
|
|
#
?
Jan 25, 2019 14:21
|
|
|
Fatty Crabcakes posted:If you choose the right framework and stick to backend development, dependency injection shouldn't be something you have to deal with. ???
|
|
#
?
Jan 25, 2019 14:23
|
|
|
context is important
|
|
#
?
Jan 25, 2019 15:33
|
|
|
Captain Foo posted:context is important I mean obviously when talking about dependency injection.
|
|
#
?
Jan 25, 2019 15:36
|
|
|
Check urself b4 U inject urself
|
|
#
?
Jan 25, 2019 15:39
|
|
|
Fatty Crabcakes posted:If you choose the right framework and stick to backend development, dependency injection shouldn't be something you have to deal with. 
|
|
#
?
Jan 25, 2019 15:59
|
|
|
Aramoro posted:Don't have to offshore for that kind of quality, I was code reviewing a task to duplicate functionality from some a public API into a private one. His first pass was to simply copy and paste one class into the other one, I told him that was a bad idea, the code in both classes is the same it just matters where it's called from. So he replaced it by an effectively empty class instantiating an instance of the other one and calling the methods in it. What the christ? That just sounds like good DRY OOP, op
|
|
#
?
Jan 25, 2019 16:08
|
|
|
Finster Dexter posted:That just sounds like good DRY OOP, op He didn't extend the original class, he added all the methods signatures from the original class, then in each one instantiated the original class and called the method. So yes, better than just copy and pasting the methods into the new class, but still wrong.
|
|
#
?
Jan 25, 2019 16:27
|
|
|
man im bad at runloops, i keep accidentally creating recursion hell fixed now though
|
|
#
?
Jan 25, 2019 16:33
|
|
|
Aramoro posted:He didn't extend the original class, he added all the methods signatures from the original class, then in each one instantiated the original class and called the method. So yes, better than just copy and pasting the methods into the new class, but still wrong. Why would you extend a Public API for a private one? Ostensibly, you want to be able to modify/extend the private one without affecting the public one and vice versa. Inheritance is actually really bad, and this is a good case for why. Public API should be sancrosanct, and being able to change and update the private API for something like an admin portal seems like a clear reason that you'd want a private API in the first place. Finster Dexter fucked around with this message at 16:40 on Jan 25, 2019 |
|
#
?
Jan 25, 2019 16:36
|
|
|
redleader posted:the wife asked me if she should learn to program, before realising that she likes people and solving actual (rather than invented) problems Same. Oldest daughter is learning to make pictures with Processing.js, tho.
|
|
#
?
Jan 25, 2019 16:46
|
|
|
Finster Dexter posted:Why would you extend a Public API for a private one? Ostensibly, you want to be able to modify/extend the private one without affecting the public one and vice versa. I'm using public vs private in very loose terms there. It's to do with the authentication mechanism used to access the resource. So that calls made from within the container do not use the same authentication as calls made from outside. Inheritance is actually really good.
|
|
#
?
Jan 25, 2019 16:48
|
|
|
count_von_count posted:Same. Oldest daughter is learning to make pictures with Processing.js, tho. my nephews are doing something with that jigzaw piece programming language
|
|
#
?
Jan 25, 2019 16:50
|
|
|
Krankenstyle posted:my nephews are doing something with that jigzaw piece programming language Scratch? It's pretty cool.
|
|
#
?
Jan 25, 2019 16:53
|
|
|
Osmosisch posted:Scratch? It's pretty cool. yeah theyre 7 & 9, probably a good age for that. i started with basic on our c64 when i was around 7
|
|
#
?
Jan 25, 2019 17:03
|
|
|
It has an insane pedigree straight from smalltalk
|
|
#
?
Jan 25, 2019 17:07
|
|
|
Aramoro posted:Inheritance is actually really good. Actually it's really bad. Composition is (almost) always a superior approach.
|
|
#
?
Jan 25, 2019 17:10
|
|
|
Finster Dexter posted:Actually it's really bad. Composition is (almost) always a superior approach. Composition is superior depending on the design pattern being used, and it being superior in no way makes inheritance bad. They are in fact both good depending what it is you're trying to do. They're also both bad if you implement them badly.
|
|
#
?
Jan 25, 2019 17:28
|
|
|
Aramoro posted:Composition is superior depending on the design pattern being used, and it being superior in no way makes inheritance bad. They are in fact both good depending what it is you're trying to do. They're also both bad if you implement them badly. this is true but a lot of the inheritance i see in the wild is bad inheritance and it's good to point it out to people so they stop doing it for bad reasons.
|
|
#
?
Jan 25, 2019 17:51
|
|
|
I've always been confused by inheritance and I guess it's partly because sometimes it's being done to gently caress with subtyping and get the compiler to let you do what you want with some amount of genericity, other times it's to prevent copy/pasting by just overriding or adding some methods, and other times it's a bit of both and you'll not know unless you have the full context of when it was written. Then you mix that poo poo in with dependency injection (because your side effects are all encapsulated but still directly causing issues through dependency chains for tests) and interfaces because that's another way to check the typing of things and you get the fun OO mess that I could never get comfortable with.
|
|
#
?
Jan 25, 2019 17:55
|
|
|
covariance and contravariance can just gently caress right off
|
|
#
?
Jan 25, 2019 17:56
|
|
|
like it's good when your framework exposes a controller class and you can inherit the controller class and use and it automatically knows how to do the things a controller should do. it just quickly gets out of hand from there. i've found sticking to a single level of inheritance (almost always from an interface) in my own code has worked just fine for me. but if you're implementing an interface i'm not sure that really counts as inheritance.
|
|
#
?
Jan 25, 2019 18:03
|
|
|
|
| # ? Apr 28, 2024 05:36 |
|
|
DONT THREAD ON ME posted:like it's good when your framework exposes a controller class and you can inherit the controller class and use and it automatically knows how to do the things a controller should do. the controller class is a good example. ime inheritance works better if it's shallow, even if it's wide; e.g., a handful of classes that directly extend a single superclass. if your inheritance tree is ten levels deep, it's probably fragile interface implementation seems closer to composition than inheritance
|
|
#
?
Jan 25, 2019 19:31
|
|