The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Seems the same in every office, one of my colleagues always complained of stuffy and too hot, the other was always shivering. The hot one luckily moved to a separate private room where he could cool off by opening all windows, even now in winter time !
Microsoft at it again. Power point by default breaks a word to next line so you have few letters on first line and rest on next and there is no direct way to turn off this feature ( Elephanting bug !!! ). The only way you can turn it off is...
You install an Asian Language (eq. Japanese ) from Control Panel and then in PPT you select the textbox for which you want to turn it off and select Paragraph and go to Asian Topograpy option and you can turn off the feature there. If you only have English language you don't have that option. What a software design.
I've just attempted to reproduce your problem and I can only do it if I deliberately shorten the input area to less than the length of an entered word ... and it "breaks" the word at the right-hand edge, which makes sense.
I'm intrigued by this. Do you have a specific example you can describe in more detail?
By the way your link is NSFW - it was blocked when I tried to look at it
The first thing that works. That's what you use. The collateral knowledge gained might be bookmarked for a later look. Forget the problem. Get up the next day. Might or might not encounter another problem and recall that it IS the same ... what was it? A problem?
This is the definition of a bad character. You do this, you're bad.
When I went to college I don't remember anyone teaching anything like that for the languages that they taught which included pascal and fortran.
So not sure why anything should be different now.
More so since I have since learned of course that often "best-practice" is very likely only "my opinion" when someone actually questions the source. In college though the 'source' at least sometimes was cited as some book which the teacher was the author - so often not really a viable source even then.
Chris Maunder wrote:
...as to how knowledge of these ancient arts is passed down in a way that let's people move on sanely.
By doing it day to day in a job. Certainly how the two people that I worked with in a lab in college did it. The lab certainly wasn't teaching anyone how to create an actual circuit but at that point they had been doing it for a job for about 15 years. They were only going to the university because, at that time, the only way you could move up at their company and get paid more was by getting a degree. Despite the very obvious evidence that taking the class wasn't going to teach them anything at all.
They didn't teach JS when I was in college (Java instead ). Tbh I think a lot of JS confusion comes from attempting to apply how other languages work that you already know to how JS works - and it's almost always wrong. The topic that always comes to mind is this[^].
Personally I like that JS lets you have flexible control on context, use, and binding. I disliked the complexity at first but after spending some time with the language I see the usefulness on top of it being much less mysterious now. Some stuff is obsolete but some things can only be accomplished using a specific technique as the article points out.
I grad I'm NOT using C or C++. The day of manual memory management, its so flexible, so archaic, its such a dinosaur. I have to go back to it once in a while when developing IoT stuff, but other than that, I'm happy with C# and even JS.