Setting a trap for an unsuspecting co-developer...
-
{me reading page 1} lotsa blakeyrat deleted posts. I wonder what fit got thrown this time.
{me reading page 2}:
@asdf said in Setting a trap for an unsuspecting co-developer...:
@blakeyrat For fucks sake, nobody is calling you stupid, stop complaining whenever someone tries to have a discussion with you.
Yup.
-
This post is deleted!
-
This post is deleted!
-
This post is deleted!
-
Can we rename this topic to "The deleted post topic"?
-
This post is deleted!
-
@Tsaukpaetra said in Setting a trap for an unsuspecting co-developer...:
You failed
-
@asdf said in Setting a trap for an unsuspecting co-developer...:
@Tsaukpaetra said in Setting a trap for an unsuspecting co-developer...:
You failed
And now I look like a jerk! Mission completed?
-
@Tsaukpaetra Nope, I'm the one who looks like a jerk now, because it looks like I intentionally pulled a part of your now deleted post out of its context. Is there still hope or have I become a politician now?
-
This reminds me of my Java days...
There is (I assume that function still exist because it's core function) a function that accepts ArrayList<Order> as parameter. Then a whoever genius creates a <clientcompanycode>Order class that inherits Order class, but for any getters/setters it inherited it always throw something like UnsupportedOperationException (I can't remember what exactly the exeption type is) and declared a dozen completely different getters/setters.
I call it a trap and abuse of OOP. Unforturnately the code is created before the first checkin in CVS and there's no comment so I have no idea to sent <censored> to whom.
-
@Tsaukpaetra said in Setting a trap for an unsuspecting co-developer...:
@fbmac said in Setting a trap for an unsuspecting co-developer...:
join us
We reject your invitation with a counter invite: Join Us. We have space for you!
He deletes post, I edit posts. So unless NodeBB now discards old edits, the space usage should be balanced.
-
@asdf
(post withdrawn by author, will be automatically deleted in 42 hours unless flagged)
-
@asdf said in Setting a trap for an unsuspecting co-developer...:
@blakeyrat For fucks sake, nobody is calling you stupid, stop complaining whenever someone tries to have a discussion with you.
Just remember, there are three things that no one ever denies unless it's actually true:
- I'm not stupid
- It won't take long
- This won't hurt a bit
-
@tcotco How would you cause the compiler to pick the new Integer one, besides using an Integer variable? Do all the new function calls cast literals or ints to Integer? Plus, since Java does auto-boxing, how does that affect this?
-
@tcotco said in Setting a trap for an unsuspecting co-developer...:
int idate1, int idate2
Possible but I found TR.
You want a date, use a damn date type. Or even a date range type if one is available.
-
@masonwheeler said in Setting a trap for an unsuspecting co-developer...:
@asdf said in Setting a trap for an unsuspecting co-developer...:
@blakeyrat For fucks sake, nobody is calling you stupid, stop complaining whenever someone tries to have a discussion with you.
Just remember, there are three things that no one ever denies unless it's actually true:
- I'm not stupid
- It won't take long
- This won't hurt a bit
So, stupid won't hurt for very long?
-
@dcon said in Setting a trap for an unsuspecting co-developer...:
So, stupid won't hurt for very long?
This is confirmed: just being stupid doesn't hurt. Things that happen as a result of actions taken while stupid, however, may.
-
you call this a trap?
I have stepped in things like:
different copies of the same header file with subtle differences
same with libraries
global phantom variable declared with extern, with different signed/unsigned attribute
oh, the trunk isn't what we send to clients, it's an old stale version. what matters is branch foobar