539 karma · joined December 3, 2009
Professional SQL Server 2000 Programming by Robert Vieira
Programming BASIC for Tandy Computers by David A. Lien
This might describe 80% of all the disagreements people have.
Start screwing yourself, now! With this line of reasoning, there is no behavior that people who think like this will not justify themselves in managing.
Until Macs run games, it's a pointless comparison. If Steam did for Macs what they did for Linux, then we'd have something interesting to talk about. But a PC without games is about as attractive as... a Ferrari, I guess. If somebody handed me a free 200K$ sports car, I'd just sell it. It's useless for my lifestyle. A PC that can't play games is equally useless to me.
All documentation and non-code files are in OneDrive, SharePoint, Teams, or good old fashioned shared network drives. IT handles backing that up for us. $Deity bless them, we've never lost anything from a database or file storage.
(Warning, possibly discouraging? ... If the original post is true, then you really must already have a clue about what's up. It seems impossible to me that you could be all that, and do all that, and still really have no idea why it's not working. If none of your friends can possibly fathom what's up, then maybe you need more honest friends. There's something they're not telling you, or that you aren't letting yourself recognize.)
"You are right," said Pangloss, "for when man was first placed in the Garden of Eden, he was put there "ut operaretur eum", that he might cultivate it; which shows that man was not born to be idle."
"Let us work," said Martin, "without disputing; it is the only way to render life tolerable."
The author of the post here is coming at this idea from one specific angle: it's worse than you think. But this is a specific instance of a larger insight. None of it makes any sense, nor has any meaning. He could go one step further with all of this. yes, it's true that your to do list is a complete f-up. No doubt. But it's not just your to do list, or your imposter syndrome, or etc. It's all of everything. The whole of existence. It's all just one complete cosmic joke of a guy slipping on a banana peel joke.I think the Hitchhiker Guide Galaxy books by Douglas Adams captured this. When I was a kid I didn't realize the existential dilemmas that kept cropping up. I just thought it was funny. Now in my mid-40s it's still funny, but it feels a lot more true, too.
I'm also getting vibes of this from Jesus.
John 18:36 Jesus said, "My kingdom is not of this world. If it were, my servants would fight to prevent my arrest by the Jewish leaders. But now my kingdom is from another place."
My angle being, this world is not what's important. Sure it's important because you're here now. There is that. But don't get too caught up in it. It's all going away soon. It doesn't really ultimately matter if you're late to your daughter's orthodontist appointment.If it's not ambiguous, then let me do it. If I rely on ambiguity then throw an exception. In the case of multiple foreign keys, throw an exception, as there's no way to know which one I mean. It'd be nice if I could disambiguate the situation though. Normal SQL allows the `on` clause.
from TableA
inner join TableB on <expression>
What if I could specify a foreign key constraint just as easily... from TableA
inner join TableB by ConstraintC
Where ConstraintC is the name of a foreign key constraint between Table A and Table B. It'd be nice to specify the constraint without having to specify the column name details.The same goes for the many to many relationship with an intermediate table. It could look something like this...
from TableA
inner join TableB through TableC
I wouldn't introduce TableC into the scope of the statement. It's not in the FROM clause. It's used in the query but is not available for selecting from. If you want to bring in columns from it, join on it the usual way.As applications grow, and initially simple lookup table semantics get more nuanced, it might be nice to be able to constrain the join on the lookup table like this...
from TableA
inner join TableB through TableC where <expression>
That way if my TableC has some extra columns, such as effective dates, or deleted flags, or that sort of thing, then I can filter out some of the joins that might usually happen.