|
The term is "sphexishness".
|
#
?
Jan 19, 2023 20:45
|
|
|
|
| # ? May 10, 2024 09:03 |
|
|
CPColin posted:If I had a nickel for every time I saw a coworker lament an obnoxious process repeatedly without doing anything about it, I wouldn't have to create obnoxious processes for them to bump into repeatedly for a living!
|
|
#
?
Jan 19, 2023 20:53
|
|
|
Meanwhile, I'm over here, empowered to spend 2 hours to change something, to save myself upwards of 5 minutes about once every year 
|
|
#
?
Jan 20, 2023 07:02
|
|
|
Heh some of this gives me vibes of learned helplessness from being stuck under some lovely micromanagement within, like, the past 7 years or so.
|
|
#
?
Jan 20, 2023 07:12
|
|
|
Google has decided to pull our app from the app store for non compliance to their guidelines. Oh no.
|
|
#
?
Jan 20, 2023 09:43
|
|
|
SurgicalOntologist posted:I've said so many times I'm not saying that this particular person doesn't suck, and I think the most likely explanation is that a previous role trained them to do this, but I think it's good for all of us to remember if that if we feel like we're repeating ourselves without getting understood, the problem isn't necessarily entirely on the listener's end. It might be worth getting a third party from your team (a manager or peer) to give you feedback on these exchanges.
|
|
#
?
Jan 20, 2023 15:32
|
|
|
raminasi posted:I'm not saying that this particular person doesn't suck, and I think the most likely explanation is that a previous role trained them to do this, but I think it's good for all of us to remember if that if we feel like we're repeating ourselves without getting understood, the problem isn't necessarily entirely on the listener's end. It might be worth getting a third party from your team (a manager or peer) to give you feedback on these exchanges. Not sure I get this point, can you just repeat it louder and angrier?
|
|
#
?
Jan 20, 2023 15:39
|
|
|
Aramoro posted:Google has decided to pull our app from the app store for non compliance to their guidelines. Oh no. Say goodbye to <1% of your revenue, sucker!
|
|
#
?
Jan 20, 2023 19:32
|
|
|
prom candy posted:Say goodbye to <1% of your revenue, sucker! It was going to be a massive problem for us, like VPs making personal calls to Google folk they knew level. But weve managed to fix it.  Android share is still small compared to iOS, we have like 1.2m active Android users something like that but its way way less than iOS in the US. The US mobile market is absolutely wild. Aramoro fucked around with this message at 23:38 on Jan 20, 2023 |
|
#
?
Jan 20, 2023 23:24
|
|
|
Aramoro posted:It was going to be a massive problem for us, like VPs making personal calls to Google folk they knew level. But weve managed to fix it. Our product is b2b so our numbers are much smaller but we had a customer who oversees a team of about 150-200 users hound us for months about how an android app was an absolute necessity for his people. We finally bundled up our web app as a PWA and put it in the Play Store for them. Fewer than 10 people used it to log in even one time.
|
|
#
?
Jan 21, 2023 05:13
|
|
|
Android does matter to us but it's always just kinda worked. Apple reject the iOS app all the time for various reasons and it seems to be a constant struggle to keep them happy. So this really came from left field, they just sent someone an email along the lines of 'by the way we're removing your app from the app store in 7 days' no appeal process, no contact at Google to escalate to just an automated message. It was pretty wild.
|
|
#
?
Jan 21, 2023 10:40
|
|
|
raminasi posted:I'm not saying that this particular person doesn't suck, and I think the most likely explanation is that a previous role trained them to do this, but I think it's good for all of us to remember if that if we feel like we're repeating ourselves without getting understood, the problem isn't necessarily entirely on the listener's end. It might be worth getting a third party from your team (a manager or peer) to give you feedback on these exchanges. Oh, absolutely. Despite that I didn't manage to weave that perspective into my post, my default assumption in pretty much all situations is that I'm to blame one way or another. (I'm the technical co-founder at a small startup so it's more or less all my fault anyway) This person actually doesn't suck, they can be quite efficient and in many situations get things done faster than most by staying focused. But this tendency to ignore any distractions can go too far and sometimes the distractions shouldn't be ignored. At least a proposal made to address it later. I've come around to think, in this recent case at least, it's mostly a matter of how they communicate their frustration. Yes, this person needs to learn how to improve technical debt in small pieces when it impacts their current work, but addressed or not it's a legitimate cause of frustration. What we need to work on is building ownership such that even if that code predates you and you've never touched it, doesn't mean it's somebody else's problem.
|
|
#
?
Jan 21, 2023 12:01
|
|
|
Aramoro posted:Android does matter to us but it's always just kinda worked. Apple reject the iOS app all the time for various reasons and it seems to be a constant struggle to keep them happy. So this really came from left field, they just sent someone an email along the lines of 'by the way we're removing your app from the app store in 7 days' no appeal process, no contact at Google to escalate to just an automated message. It was pretty wild. It's really annoying and scary how easily the big players can just completely shutter a business if they want to with no accountability. See also Twitter just banning third party clients this week.
|
|
#
?
Jan 21, 2023 14:54
|
|
|
Hey guys, I just wanted to let you know that when I followed your directions to run Address Sanitizer with your library enabled that it crashed, and when ran it without Address Sanitizer, it also crashed. When I disabled the additions with your library then it didn't crash. When are you going to fix it? No, I didn't run Address Sanitizer without your additions. That was part of your debug. No, what do you mean that you showed me where Address Sanitizer pointed out a buffer overrun before I went off on this tangent? I thought on the phone call where you pointed that out and told me to fix it that you were had to fix your library. When is your library going to fix my buffer overrun? Can we have a quick call at 7:30PM while your wife is next to you asking to figure out her favorite food? (Answer: Anything that's red. Tomatoes, tikka masala, beets, human blood, whatever.)
|
|
#
?
Feb 1, 2023 02:29
|
|
|
Rocko Bonaparte posted:Hey guys, I just wanted to let you know that when I followed your directions to run Address Sanitizer with your library enabled that it crashed, and when ran it without Address Sanitizer, it also crashed. When I disabled the additions with your library then it didn't crash. When are you going to fix it? New developer time, that one's brain is broken.
|
|
#
?
Feb 1, 2023 04:49
|
|
|
Tbh I can't make heads or tails of your post
|
|
#
?
Feb 1, 2023 12:27
|
|
|
Xarn posted:Tbh I can't make heads or tails of your post A developer is blaming a third party library for a crashed application. The crash has nothing to do with the library, and on a support call the library owner said "nah it's not us, your app crashes right here and it's your fault". Dev then says "great you've found the problem now fix it for me". A dev that truly has no idea what they're doing.
|
|
#
?
Feb 1, 2023 13:22
|
|
|
Judge Schnoopy posted:A dev that truly has no idea what they're doing.
|
|
#
?
Feb 1, 2023 15:43
|
|
|
You miss 100% of the shots you don't take
|
|
#
?
Feb 2, 2023 05:24
|
|
|
Blinkz0rz posted:You miss 100% of the shots you don't take You make 100% of the shots you don’t miss
|
|
#
?
Feb 2, 2023 05:48
|
|
|
The original program had a buffer overrun in it. It seemed to work until they started to use my library. They then blamed the library. Having just dealt with somebody else who did the same thing, and having found a double free in their code, and having fixed that, everything started working. But in this case, they listened to me pointing out the overrun we found in their code and somehow figured I was going to fix something on my side instead that would magically fix it. Normally, this kind of "it crashed when I added X therefore X is the problem" would be completely logical, but when you're playing with pointers and driving across memory like a toddler ramming a Tonka dump truck around the sandbox, then that logic totally explodes. For example, that double free was causing a crash where valgrind thought OpenSSL was doing something odd. It turned out the double free was murdering the allocation table so it could no longer even tell what was what. So when you have exposed memory violations and are letting them stay while you gently caress around, you have entered some eldritch non-Euclidian hellworld with blue and orange morality. It might claim to crash because of X but that's because the overrun shoved brain worms into the program and now it spews nonsense. My library could have issues (it uses something that does leak) but I did specifically test it for memory violations. It was also written in Rust so while having some unsafe blocks, I have a lot more faith in it's memory correctness despite the library being relatively young.
|
|
#
?
Feb 2, 2023 09:51
|
|
|
I followed your advice and removed all the calls to free, and the problem got worse. Ball's in your court now, buddy.
|
|
#
?
Feb 2, 2023 15:27
|
|
|
No it was worse than that: I commented out the call that was causing the overrun and it still crashes when it calls your code. No, I did not try Address Sanitizer after commenting out the code. Do you have time for a quick call? (My power and Internet is out right now)
|
|
#
?
Feb 2, 2023 18:36
|
|
|
Is that "clean code" book actually good advice? Lead is pushing for us to read it
|
|
#
?
Feb 10, 2023 22:19
|
|
|
Personally I think it is, and it's still relevant. But take what it says and dial it back a notch or two. The examples should be taken as unobtainable ideals not realistic goals.
|
|
#
?
Feb 10, 2023 22:25
|
|
|
brand engager posted:Is that "clean code" book actually good advice? Lead is pushing for us to read it Yes as long as you take everything with a grain of salt. Think of its advice more as “stuff you can think about as you’re building or refactoring” - you will still need to use your judgement to know when to break the “rules” it lays out. It gets crazy specifically about function length and says something like all functions should be one or two lines.
|
|
#
?
Feb 10, 2023 22:48
|
|
|
Reading Clean Code as a group and talking about it one chapter at a time is great. You can collectively decide what advice to take and what to not. It’s great for team building.
|
|
#
?
Feb 10, 2023 22:52
|
|
|
All methods should do one thing and one thing well. If it takes 20+ lines of code to do one thing so be it. 
|
|
#
?
Feb 10, 2023 23:07
|
|
|
FlapYoJacks posted:All methods should do one thing and one thing well. If it takes 20+ lines of code to do one thing so be it. https://www.youtube.com/watch?v=y8OnoxKotPQ but as your codebase.
|
|
#
?
Feb 10, 2023 23:15
|
|
|
Clean Code is a mix of banally correct advice and actively bad advice. If you can tell which is which then reading the book is a waste of time and if you can't then you're probably going to learn some bad habits from it.
|
|
#
?
Feb 10, 2023 23:32
|
|
|
Lol there's always one.
|
|
#
?
Feb 10, 2023 23:34
|
|
|
At least two. A goon wrote a long post about it a while back https://qntm.org/clean
|
|
#
?
Feb 10, 2023 23:43
|
|
|
it's not a good book. read martin fowler stuff instead
|
|
#
?
Feb 11, 2023 00:35
|
|
|
The problem with the Microservices video is that they come up with much better dumb names then any developer actually does
|
|
#
?
Feb 11, 2023 00:52
|
|
|
Harriet Carker posted:Yes as long as you take everything with a grain of salt. Think of its advice more as “stuff you can think about as you’re building or refactoring” - you will still need to use your judgement to know when to break the “rules” it lays out. This is also what I learned in school. Our professor told us that a function should do exactly one thing and one thing only, and if it does more than that, break it into multiple functions. Obviously, I don't do that. But I do use a lot more functions than I might have otherwise, and that's a good thing. Volmarias posted:https://www.youtube.com/watch?v=y8OnoxKotPQ This video is so excellently written. Love it every time Cup Runneth Over fucked around with this message at 01:05 on Feb 11, 2023 |
|
#
?
Feb 11, 2023 01:00
|
|
|
Steve French posted:At least two. A goon wrote a long post about it a while back drat, dude is getting roasted
|
|
#
?
Feb 11, 2023 01:10
|
|
|
Clean code as a phenomenon is more destructive than the book itself. A lot of teams will treat it as a Bible, even though a bunch of stuff in it is obviously bad or outdated advice. Developers who worry a bunch about "magic numbers" and breaking every logical block of code out into its own function rather than think critically about readability are the bane of my existence.
|
|
#
?
Feb 11, 2023 01:28
|
|
|
Kindle version is $30 so I'll go ahead and grab it
|
|
#
?
Feb 11, 2023 02:56
|
|
|
public static String URL_SEPARATOR = "/"; This kind of thing is when people think too much about magic numbers and anonymous string parts.
|
|
#
?
Feb 11, 2023 03:19
|
|
|
|
| # ? May 10, 2024 09:03 |
|
|
Following Clean Code is better than nothing if you're a beginner just at the point where you can create spaghetti code and have no strong opinions of your own. Once you get some experience you'll start to find examples of the book falling apart, but by then you know the rules well enough to know when to break them. If you're already a working dev then I'd read the book and let the ideas float around in your head but don't be dogmatic about anything.
|
|
#
?
Feb 11, 2023 04:07
|
|
