This action will delete this post on this instance and on all federated instances, and it cannot be undone. Are you certain you want to delete this post?
I wish I could reach the correct audience to suggest to that, if you are going to work full time remote, especially for a mostly remote company for the first time, it is absolutely crucial that you learn how people communicate and actively participate in it. Not just how work information is disseminated. Join your “random” and hobby Teams or Slack channels. Meet people not on your direct team. Join a social group if your company sponsors one you find interesting. It indeed takes effort as an introvert - but while working remote you are not building relationships organically like in an office, at all. Those work relationships are important to getting stuff done in business, being noticed when opportunities come up, emotionally feeling part of a team and mission, and staying mentally healthy. We spend a big chunk of our lives working!
Over the last 5 years of working and managing a team FT remote, this social interactivity is one of the top indicators I’ve observed of whether someone will succeed and be balanced and happy, long term - or whether they will burn out and be left behind. The people who often vanish the fastest never chatted except when prompted to do so for business, never turned their camera on, nor set a profile image.
I’m not telling you to step way outside your comfort zone. I’m not saying there aren’t situations where it’s necessary to turn off the camera. I’m not saying you’ll automatically fail if you never socialize. I’m just giving you some advice based on hard life lessons of watching people thrive versus be unhappy.
Todd Sundsted postedDec 5, 2022
Todd Sundsted postedDec 4, 2022
Today's release of code fixes things that have been annoying me for a while:
- Commits c01e797 to b21a97a ensure that bulk assignment raises an error when the type of an argument value does not match that of the corresponding property being assigned to. In the past, attempts were silently ignored. As you'd expect, adding the check and raising the error was easy—cleaning up all the places I'd carelessly passed in
niland other garbage was not. Lesson learned? We'll see... - While I'm in there, commits 1ac498e to 3d45ece ensure that bulk assignment raises an error when attempting to assign a property defined only by a
getter(which is, effectively, a read-only property). Previously, this code wouldn't even compile, thereby unintentionally coupling database persistence and bulk assignability. - Finally, commits 5c2ec70 to 99dca65 clean up a few small defects in presentation: wide blocks of code no longer blow out the width of the parent container, image attachments present at ratios closer to what Mastodon uses (the presumption being that's what people optimize for if they optimize for anything) (this should also fix issue #53), and figure captions get a little breathing room. I'm no good at CSS, so this kind of thing takes me forever.
Todd Sundsted postedDec 1, 2022
i built @relistan 's branch this morning and tried out ktistec support for mastodon profile metadata. the attachment shows profile metadata pulled from the ruby.social mastodon instance, as well as @relistan 's own personal ktistec instance. this is something i've wanted for a long time!
a shoutout is due both these two (the owners of the two profiles shown in the attachment): @alexanderadam has been posting encouragement about ktistec all year long, and maybe before—an intangible that's immensely valuable when you're banging away on open source software—and @relistan is the first person besides me to contribute major feature functionality to the project—which takes a huge leap of faith.
thanks!
Todd Sundsted postedNov 29, 2022
elon needs to learn that freedom of speech isn't measured in decibels.
Todd Sundsted postedNov 28, 2022
i’m setting up an old mac laptop (2019) for dev work… docker or podman?
Todd Sundsted postedNov 28, 2022
in nyc, hoping to score a raspberry pi zero 2 w
Todd Sundsted postedNov 26, 2022
i added some in-process data collection to ktistec in order to better understand how it uses memory.
the chart shows the accumulated total requested memory (blue) over time. as expected, it grows monotonically and almost linearly. in theory, i guess, if i posted something engaging, you'd see the effect of the engagement (likes, shares, follows, etc. etc. etc.) on memory usage. in any case, the heap (red) remains flat.
i think it would be great to have this chart on the metrics page. when time permits, i'll add it. in the meantime, if you're running a (very) recent build, you're collecting data.
Todd Sundsted postedNov 25, 2022
sometimes positive sounding things—like effective altruism—become justification instead of motivation.