> including a visit at 5:30pm or 6:30pm to see the state of the office and attendance
As an academic, I used to work 11am-8pm many days when I was younger thanks to flexible working hours, and I wasn’t the only one working late but not early. I realize this is probably more rare in corporate settings, but keep in mind if the place has flexible hours you might see more people at 6pm despite people not doing 996.
I think that is great if you want flexibility, and I used to do that also!
What i'd assess at 6:30 is whether people are on meetings or on focus time. If you have monitors with zooms full of 5-6 people, I wouldn't think that is flex hours, i'd assume that is a meeting being scheduled at 6:30.
On the other hand, if you have people focus working, you cannot draw any conclusions from that.
Personally, I stay at work late. But there is a difference between me being obsessed with a problem and working thru the evening trying to solve it (awesome for me) vs meetings that are being scheduled at 6:30pm or 7pm
This is really my priority to achieve at a job, and one of the reasons I try to be good enough to be indispensable is to be allowed to roll in in the morning whenever I get there.
I have a very tough time in the morning convincing myself to go to work, and a very tough time at work tearing myself away from something in an intermediate state. Things at work are always in an intermediate state at 5:00, unless you stopped working well before then (or got very lucky), so I always end up working late whether I come in on time or come in late.
So I'm always trying to get to the point where management lets me get there when I get there, and trusts me to be productive. It's a mental thing. I get up early and do a lot in the morning; I'm a morning person. Maybe too much so. The time between getting off work and going to bed is garbage time for me; a long annoying commute and a meal. When I leave at 5:00 I just fall asleep by 9:00.
That was true of me as well, and at the same time, I was working alongside parents who worked 7:30-5:30 with a break to pick up the kids from school.
Nobody wants a "visit" from the founder, anyway. They want timely two-way flow of information, access and guidance on the occasions when they need it, and maybe (maybe) an occasional chance to hang out socially as a group with no reference to work. Nobody wants the founder randomly dropping by during work hours to assess morale.
Depends, it’s hard to make a blanket statement like that. Recycled steel and aluminum for example is absolutely not a scam. But for plastics, I agree that waste incineration is mostly a better solution than recycling (which produces low-quality plastics with some risk of unhealthy contaminants in the few cases that it’s not actually a scam).
Markdown was based on the "syntax" already being used informally in emails and on IRC. So the author did do some searching to define the syntax.
I don’t like many parts of markdown either (like the syntax for bold), but those were also IIRC already being parsed by some IRC clients before Markdown was specified.
> Markdown was based on the "syntax" already being used informally in emails and on IRC.
News to me :-/
> So the author did do some searching to define the syntax.
I recall using tin/rtin in 1995, and people used the org mode syntax for italics, underline and bold (not that it made any difference). Same with plain-text email (I used elm, then pine, then mutt). Same with IRC clients - convention was the org mode syntax, not the markdown we have today.
The very first time I saw '**' for bold was in setext, circa 2004. People weren't actually using setext though; they were using *some text*, _some text_ and /some text/.
In short, no, I don't believe that the authors did any research. I think what happened is that they saw something like setext, though "great idea, lets run with that!", and did so.
I feel it depends whether you inspect and edit the code as part of the workflow, or just test what the AI produced and give feedback without participating in the coding yourself.
Most of the slop i witness is the latter. This is evident in huge multi 10K pull requests. The code is just an artifact, while the prompting is the "new" coding.
Shellfish is underrated. It has a very convenient tmux integration (auto-restore a specific tmux session per host to work around iOS suspending background apps), supports SSH tunneling via other configured hosts, and can be used as an SFTP file provider for other iOS apps. It’s also generally polished and supports the expected standard terminal features.
There’s a few settings I wished were possible, like using volume buttons as modifier keys in Emacs (I’ve heard about this in other apps), but mostly it works fine.
The risk is that publishers might then start opposing the publication of manuscripts that have been shared as preprints on arXiv, if they start perceiving it as a competitor and not a supplement to their "service". But I concur, arXiv with social media features would be nice.
I get regular "crashes" on the newest Fedora KDE on a new Thinkpad X1 (from this year). I say "crashes" because it’s not the window manager or Wayland session crashing but some non-essential component of the Plasma desktop (don’t remember which one right now), so it doesn’t affect my work at all. From my point of view it basically just causes a crash report popup every 1-2 hours and says whatever service crashed has been restarted.
As an academic, I used to work 11am-8pm many days when I was younger thanks to flexible working hours, and I wasn’t the only one working late but not early. I realize this is probably more rare in corporate settings, but keep in mind if the place has flexible hours you might see more people at 6pm despite people not doing 996.
reply