Tcepsa

Had the same issue with C-x C-c; I remapped mine to C-x C-c C-t because it worked for me as a mnemonic (assuming a "soft c"): "ex-s-t" => "eckst" => "exit"). Major productivity boost!

I rather interpret it as "If you do a good job with simple tools you'll be given opportunities." (I'm interpreting the parent post to be implying that the simpler, solid hire is the one who is no longer there because they were able to leave for a better place). Also, as cautionary tale for managers: "If you give folks who write solid code boring work, they will find something that suits them better."

Today I learned why the bottoms of the staircases in the building where I work look like they've been sprayed with porridge. Thank you!!! (I had assumed it was insulation of some kind but could not figure out why they'd put it there)

Yes, I am OK. In the micro, immediate term I'm a little burned out: The summer was fantastic, but draining; I have 4 weeks of PTO and I used most of it within a two-month period on 4 different trips with my family. It was tough to make sure I stayed connected enough at work, and in some ways I am still catching up a couple of weeks after returning from the last travel. Speaking of work, I'm thinking of making a MAJOR transition; it is a fantastic opportunity, but I am also concerned about the details (it is an internal move and I like the group I am with quite a bit, so I really want the things and people I'd be leaving behind to be in as good a shape as possible, avoid burning bridges, etc.) There are so many projects at home that I feel like I'll never catch up (e.g. it's the end of the summer and I haven't started building the raised garden beds that we were going to put in last year)--much of that is because other projects with higher priority bump them back in the queue, but it still rankles a bit. And our spending has been outpacing our earnings for long enough that I'm a little worried about our savings.

But longer term, things are fantastic. I've been a software developer/engineer/architect/whatever for about 16 years now, the last 12 with the same (non-FAANG) organization (though I did a similar internal transfer about 7 years ago, which has turned out to be an incredibly positive change of direction for me). I have a high degree of autonomy and several different very interesting projects that I could choose to be working on. (For example, I recently stepped back from a managerial role that has been taking most of my time for the past 3 years or so to focus more on technical work). I'm making in the low six figures, and expect to see my salary continue to increase steadily (though it will be interesting to see how my stepping back to a more technical role will be reflected). The work-life balance and corresponding flexibility that I have here are wonderful (generally 40 hours a week, and if I go over because of travel or deadlines I can usually take a corresponding amount of time off in the next pay period or two, and it only happens once or twice a year). My commute is about 15 minutes. I have a spouse and kids, and that's not without its own stresses but in general things are going well with them. I am on great terms with my parents and siblings, though I don't see them as often as I might like.

Thank you for the opportunity for me to step back and appreciate that for a minute, especially in the face of all this short-term anxiety I'm facing. If you would have told me this when I was back in highschool and the hell that that was, I probably wouldn't have believed you. Heck, if you would have told me this back when I was struggling with VBA 15 years ago in my first job, I might have been pretty skeptical (me, a manager? Pshaw!) But I am so glad that I didn't give up, that I made time to hone my skills, and that I took those uncertain leaps into the opportunities that I found.

Disclaimer: I'm not a lawyer; everything in this comment is my opinion and/or based on things that I have found on the internet or vaguely remembered from legal notices posted around my workplace. EDIT: Also this is only about things in the USA--I do not know how it works elsewhere.

Short answer: You can't go home early because if you don't put in the time your employer requires of you they can fire you!

Longer answer: The 40 hour work week is set forth in the Fair Labor Standards Act (FLSA). All that the FLSA says is that depending on what kind of work you do, your employer may or may not be required to compensate you for overtime. Your employer is allowed to set your work hour requirements, but if you are considered "non-exempt" from the FLSA, then if you work more than 40 hours your employer is required to provide time-and-a-half compensation for the extra hours worked. Many positions in tech are, I think, generally "exempt" from the FLSA's overtime rule (software dev types, at least--I'm less sure about ops/IT services folks) and therefore employers are not required by law to compensate software developers for overtime.

The FLSA does not address whether or not an employer can require you to work more or less or exactly 40 hours per week; it's all about what obligations they take on if you are non-exempt and they do require you to work more than 40 hours per week.

If this[0] is what you're talking about, my wife and I also really want it to be a thing! (EDIT: If it's not, would you mind posting a link?)

[0] https://en.wikipedia.org/wiki/Volkswagen_I.D._Buzz

I'm a little confused about their apparent implication that they have to single step all the way to the point that they want to inspect. Maybe older debuggers made you do this? But today, breakpoints are useful and seem to be widely supported, so you can run the program at full speed to the point of inspection, and then instead of getting a drive-by snap-shot as you do with a printout, you can do a more in-depth interrogation of the state of the system "Oh, this part of the state has value X as I expected, maybe it's this other part of the state instead--yes, there is something weird over here!" instead of discovering value X in the first run, adjusting your print statement, recompiling, and discovering the unexpected behavior.

All that having been said, surely there is still great value in applying a similar amount of consideration as to where to put the breakpoints as you would in determining where to put a print statement! (edit: and also in thinking hard about what new values to inspect if your initial guess is not borne out)

Tried again just now to use Remote File access from my Windows desktop to my Linux (Ubuntu) cloud VM. I'm using Helm, and if I do C-x C-f (helm-find-file) and then type /ssh:me@remote: it opens a new buffer called "C:/ssh:me@remote:".

There was a suggestion on a Reddit thread to use Dired instead: C-x d /ssh:me@remote: which I also tried. This appeared to get further but subsequently failed with the error "ssh_askpass: exec(/usr/lib/ssh/ssh-askpass): No such file or directory".

So I figured I'd try launching Emacs from within a Git Bash prompt to see whether that would provide the extra commands it was looking for, and it failed to locate my dotfiles (must have a different $HOME in that context...). However, when I attempted to open a remote file it did actually prompt me for a password! ...but then the LDAP authentication failed after timing out.

I'm out of gumption for now, but hopefully that helps to illustrate why I still want to be able to SSH into a machine and launch Emacs from the terminal.

Because I can. I've tried TRAMP a few different times in the past and, for whatever reason, I bounced off of it pretty hard every time. They were long enough ago that I can't remember what went wrong, but I have a pretty deep and lingering feeling of frustration whenever I contemplate giving it another go. Compared to the effort needed for me to shell into the remote machine and start Emacs there, I just haven't bothered.

I think it's great that the capability exists and that others find value in it; it's just not for me (or maybe vice versa). One of the great things about Emacs is that it can still work for both sets of people: folks who like TRAMP and folks who like to SSH in and run it locally.

"Now that I've SSH'ed into this system I sure wish I couldn't use Emacs!"

--Nobody, ever

(My point being that I think abandoning the terminal would be a huge loss to many people and therefore a poor decision)

You might also be interested in some of the work that bunnie has done with paper, copper tape, binder clips, and various components in this blog post[1] and also with Chibitronics[2]. That having been said, I'm glad they mention why they didn't use copper tape here before I tried to stick any down on a Lego plate!

[1]https://www.bunniestudios.com/blog/?p=5259

[2]https://chibitronics.com/

What about the idea that senior people design stuff but then hand it off to junior people to write and then coach them through the bug fixing and refinement? (Honest question; doesn't seem like there's much of this where I work and I'm considering trying to introduce it because it seems to me like a good way to leverage the senior folks' skills while also transferring them to more junior folks, but I'm wondering whether there is some kind of taboo against it or something else that I'm missing)

One additional thing I've found that I needed (in Windows) is

    (setq omnisharp-server-executable-path "C:\\path\\to\\OmniSharp.exe")

So it can actually start the OmniSharp server (EDIT: Possibly because I haven't installed OmniSharp so much as just unzip it)

I would try to set up a healthier lifestyle, primarily by working on establishing consistent exercise and eating patterns.

In the article they mention that "The discerning viewer might notice that the MEGA logo is bleeding together a bit in the little vertical gap. We will tweak this. Also, the printing on the fronts of the keys is currently black instead of grey, and there is a little over-bleed on the graphical symbols. We will also get this fixed."

I'm not sure whether this will completely resolve the issue, but it seems likely to at least help. [EDIT: Just noticed that it specifically says "on the graphical symbols" so I'm not sure they'll be adjusting the lettering]

Perhaps, like beer, it is a taste that I have yet to acquire, especially if it is as useful as it sounds for differentiating user input from machine messages/feedback :)

TIL! Thanks for pointing this out; it makes me feel much better than my previous assumption that all these people running around proclaiming the greatness of CL were just _okay_ with the allcaps!

I believe there is another case, very similar (also involving a closed loop): If you pass a (properly oriented) magnet through or even across the opening of such a loop, an electrical current will flow around the loop (while the rest of the atomic bits will stay more or less in the same place ;) ) and no charge will accumulate.

(This caught my attention because I had up to that point believed that electrical fields are always conservative, and this demonstrates that not to be true: an electron traveling around the loop in such a manner will eventually return to its starting point having done non-zero work)

I liked Human Resource Machine for brushing up on Assembly language concepts

Microcorruption is a fun resource for learning about reverse engineering, assembly language, and cybersecurity (the concept is that you're going through the assembly code of dev kits of different versions of software-controlled locks to find vulnerabilities that can then be exploited to get into warehouses full of MacGuffins). I've gotten through about half of the stages so far--they get really tough, but it is extremely satisfying to successfully complete one!

I also really enjoyed the couple of Zachtronics games I've played (I've done the first 5 stages or so of Konstructor: Engineer of the People and I managed to get through all the main modules in TIS-100)

Lightbot is a cute app for initial programming concepts through puzzles (program a robot to walk around a grid and light up various squares)

I believe the point is that IF the problem with nil is that when it shows up you can't be sure whether it was on purpose (to indicate an "empty" value) or on accident (because an error in the code caused a variable to not get bound). By introducing a separate identifier (e.g. :id-unknown) to explicitly handle the empty-value case, it frees up nil to solely signify improperly bound variables.

[EDIT: Emphasis]

Also, some public libraries have partnerships with them to provide free access to anyone with a library card.

Pedant that I am, I would like to point out that 120 is not a "normal" IQ. The test is scored such that 100 represents the median IQ, with 85-115 being within one standard deviation of that median. This means that less than about 1/3 of people will have a score outside of that range.

That having been said, I apologize for not being able to answer your actual question since I don't know the IQs of the folks I maintain friendships with. Most of them seem like they probably are higher than that range, but that might just be confirmation bias.

+1 for Alex French Guy Cooking (mentioned in sibling comment). I like his method of chopping onions; most of the onions I chop don't need to look particularly pretty, so it's great.

Also, You Suck At Cooking https://www.youtube.com/channel/UCekQr9znsk2vWxBo3YiLq2w is one of my guilty pleasures. I think he's hilarious and figured it was purely a spoof channel, but then I actually watched a couple and if you don't mind and/or enjoy his fooling around (and have a moderately well-tuned BS detector to tell when he's fooling around) the recipes are pretty good. I particularly like how he doesn't spend a whole lot of time measuring things out. It's a great counter to the precision generally present in recipe books, which used to be a big hangup for me (pipettes broth into Pyrex measuring cup "gotta get EXACTLY 1 C broth in this soup!" => dumps broth into drinking glass "Eh, close enough!") I'm still adjusting to that style but it has already saved me both time and unnecessary tension. (Seriously. The error margins in most cooking seem ridiculously large to me!)

I just got a Pebble 2 SE and loving it so far. I even wrote a little timer app for it; getting set up was comparatively straightforward and the API seems to be really well designed. Fun to be doing something in C again, though there's also a JS route for folks who are more comfortable with that path. The company was recently purchased by Fitbit and they are going to end official support for the Pebble devices so things like voice recognition are going to stop working. However, they released a firmware that removed the dependencies on their servers and there's a pretty substantial grassroots effort to keep things moving forward. I like it enough that I'm thinking about buying a couple more to keep in deep storage for when my current one dies. I imagine it's hard to find a more capable watch for $60, though I haven't done a super exhaustive search.

https://www.pebble.com/pebble-2-se-smartwatch-features

https://www.amazon.com/Pebble-Technology-Corp-900-00057-se/d...

Really great to know that I'm not the only one struggling with this--thanks for sharing!

I'd like to put in a plug for Finex cast iron. They're milled smooth on the bottom which I prefer to the finish on the Lodge pan that I have.

Regardless, +1 for cast iron!

The ability to use Emacs with a decent degree of proficiency. I find its text navigation abilities beyond compare. This is huge for me since I write software and and the creation of software generally involves a lot of text manipulation. This is perhaps less of an edge now that other IDEs are better at autocomplete and jumping around the code than they were when I started learning Emacs.

On the other hand, the fact that I can write Windows applications, compile them using Microsoft's compiler, launch them, and follow their log files all within Emacs is wonderful.

So between the keybindings, 3rd party packages, and flexibility it not only makes me more productive but also helps me have more fun and stave off burnout.

(EDIT: Readability)

You have just made my day!

(Was planning on picking it up eventually, but hadn't figured out how to negotiate stealing my wife's Windows laptop for a week straight. Now I don't have to! ^_^)

I think it's more that I totally misinterpreted the data. For some reason I assumed it was the number of students from each group that scored above some threshold, rather than the average score of that group.

My calculations are completely garbage, and I would withdraw the comment but it looks like I can't at this point.

I totally misinterpreted the data; for some reason I assumed it was the number of students from each group that scored above some threshold, rather than the average score of that group.

My calculations are completely garbage, and I would withdraw the comment but it looks like I can't at this point.