User talk:jennasloan

Useful links

Liskov substitution principle

Hi Jenna, Care to discuss the Liskov Substitution Principle page? I replaced it with a redirect to Behavioral subtyping because I believe the "substitution"/"substitutability" terminology, used throughout the page, is technically incorrect. (Please see the "Substitutability" section on the Behavioral subtyping page for details; see also Leavens, Gary T.; Naumann, David A. (August 2015). "Behavioral subtyping, specification inheritance, and modular reasoning". ACM Transactions on Programming Languages and Systems. 37 (4). doi:10.1145/2766446., bottom of page 5. This journal is the most prestigious and most strictly peer-reviewed academic journal in programming languages.) I'm teaching a course on object-oriented programming, including behavioral subtyping, at a university in Leuven and I wanted to keep students from getting incorrect information when they Google "behavioral subtyping". (It's better now than it was originally, though: before I did the redirect, Google sent people to the LSP page for "behavioral subtyping". It seems that now, the Behavioral subtyping page is the first hit, and the LSP page the second hit. I just hope the LSP will not overtake the BS page again, given that it is probably linked to more.) Bart Jacobs (Leuven) (talk)

Hello, I reverted your edit because it removed the information about the Liskov substitution principle, as the behavioral subtyping page did not contain all of the information on the Liskov substitution principle, and did not contain the Solid principles template. Please don't edit pages on Wikipedia just because you believe the terminology is incorrect or the first result on Google is different than what you expect. The Liskov substitution principle page uses those terms correctly. Honestly, seeing how the behavioral subtyping page just restates a bunch of what is already present on the Liskov substitution principle page, and because said page has also existed for a longer amount of time, the behavioral subtyping page should probably be redirecting to the Liskov substitution principle page. jennasloan (talk) 07:28, 6 June 2020 (UTC)[reply]

Both the authors of the academic article I cited, Gary Leavens and David Naumann, and myself (an expert on this topic) are of the opinion that the term "Liskov Substitution Principle", and the use of substitution terminology more generally when it comes to behavioral subtyping, is flawed. You seem to disagree. I guess we need some kind of dispute resolution, then? Bart Jacobs (Leuven) (talk) 07:47, 6 June 2020 (UTC)[reply]

BTW: I just discovered that Liskov herself basically confirms that the term "Liskov substitution principle" is not technically correct, in the following video: https://www.youtube.com/watch?v=-Z-17h3jG0A At 2:27, she starts talking about what she said during her keynote (note, by the way, that she does *not* use substitution terminology at all in recounting it!!!), and at 4:03 she says "Technically, it's called behavioral subtyping." which implies that she believes LSP is not the technically accurate term to use. I submit that Wikipedia should try to use technically accurate terminology as much as possible. The LSP terminology should of course be mentioned because of its widespread use, but the technical discussion of the concept should be in terms of behavioral subtyping, not substitution, and should therefore be in an article titled "Behavioral subtyping". Bart Jacobs (Leuven) (talk) 15:08, 6 June 2020 (UTC)[reply]

User Namcokid47

Hi, there! I noticed that you also noted some deletions in the past that were made by user Namcokid47, and I would appreciate your input on their talk page regarding recent deletions of other pages. Thanks! Pacack (talk) 21:30, 25 March 2021 (UTC)[reply]

Could you possibly get a skyline photo for Fargo?

Fargo, North Dakota's current lead photo is pretty unrepresentative of the city, but every other photo isnt better. Please let me know if you can do this. Thanks! WeaponizingArchitecture | scream at me 15:02, 8 May 2023 (UTC)[reply]