321–330 of 334 posts
Earlier quoted context omitted.
“you should be smart enough to figure this out from here” bravado probably for some cases.
You do realize that writing good docs takes time, skill, and effort, right? Not to mention the docs you're blanketly scorning at were most likely written on someone's spare time who has no obligation to do so.
Earlier quoted context omitted.
“you should be smart enough to figure this out from here” bravado probably for some cases.
You do realize that writing good docs takes time, skill, and effort, right? Not to mention the docs you're blanketly scorning at were most likely written on someone's spare time who has no obligation to do so.
Earlier quoted context omitted.
It’s more common than you think. I graduated in 2013 and can tell you there were minimal opportunities to learn how to operate a Linux command line (if you didn’t already want to). Most jobs will set you up with some IDE with the codebase preloaded and a big green compile button, it’s just easy to avoid I guess. I’ve been using Linux since 2008 and it’s the most high-yield skill set I have, it makes everything simple…
It's crazy how fast it changed then. I graduated in 2002 and you literally could not leave without knowing how to use Unix. When I started in '98 the school's email system had to be checked through terminals and my dorm hadn't even been wired with Ethernet, although we had it by the second half of my freshman year.
Earlier quoted context omitted.
I am the first to graduate college and to go into software. I learned a lot on my own before studying Computer Science, and still do after. I can agree that people tend to quickly get condescending ("just google it") instead of giving keywords ("I think you are looking for X, Y, Z, try to read about them and come back when you have specific questions"). IMO the latter is constructive, the former is discouraging. The…
I think there must be some sort of culture gap in play here. I've been told to "google it" more times than I could ever count and not once have I perceived a condescending intent. And similarly, I have told people to google things many times and not once did I mean it to be condescending. Usually it means "I don't know the answer off-hand, but I know that I could find it if I googled it. Therefore I'm telling you how…
Personally, when someone answers "google it", I read it as "fuck off". If you don't want to help me, just don't; no need to explicitly say you won't.
However, it's totally different if you say "you should read about concepts X, Y, Z", because that gives me keywords to search for.
> If I turn to my coworker and ask [...]
Well that's a bit different than asking a question to strangers online. Of course sometimes it makes sense to ask a coworker, though a quick search beforehand never hurts.
Earlier quoted context omitted.
The more apt analogies would be: * "chng af" * "tglCB" I will continue my crusade to fight against this and spell things out until my death.
Hear hear. I don't think programmers - as a group - get to complain about people not learning programming tools while simultaneously making them so unapproachable (especially Linux things). It's not just the overuse of acronyms. There's also: * Religious devotion to the CLI despite it having terrible discoverability. * Really bad naming. Git is probably the worst offender at this, but the whole of Unix is a naming me…
The problem is mainly one of discoverability. The non-programmer in the examples says "simple" when they mean "discoverable". The programmer says "simple" when they mean "not much code complexity". Of course you disagree. All the examples - installing and using a package manager, running a command line program - are "simple" from a software point of view, but they're not at all "discoverable". To understand the steps…
I feel like there's a fundamental understanding of man-pages that we are just missing. I find myself in the same boat quite often.
Earlier quoted context omitted.
> when somebody sends me a spreadsheet with functionality I've never seen before it's extremely easy to figure out what they did a You must have encountered only very simple spreadsheets. I've had to reverse engineer a number of technical spreadsheets that took days of full time sweated effort to merely understand the principles and more days again to extract the methods accurately enough so that they could be reimpl…
When you've done that, is it all of a sudden super-simple? You've had to incorporate all the same complexity into your model. If you sent it back to a spreadsheet user, don't you think they would say the same thing, just backwards?: "I had to reverse engineer a number of technical data processes in R that took days merely to understand the principles..."
Earlier quoted context omitted.
Solid thoughts - I neglected to let on that in my case the seniors lament about how new tech sucks, like python being just another perl… etc. They are “tear down prove it to me while I call things retarded” sometimes. Thats where mgmt should step in. Its really only a couple people.
You might be surprised how even people as aggressive or stubborn as this might still find it embarrassing or unreasonable to refuse a lunch-and-learn. Maybe sending a mass invite to a meeting on Python would be seen as passive aggressive, so just start socializing smaller ideas with key people. It sounds like you'd have to be cautious about upsetting people but I think it's always worth it to at least find the most p…
Earlier quoted context omitted.
Can't recommend PysimpleGUI highly enough for this use case. Hope it suits your needs!
Worked perfect, I had it doing something on-screen in 15 minutes, had it mostly mocked up in 30, and had it polished and pretty with error handling in an hour. Will make for a good demo on Monday.