Huh. Sounds just like me :D
Depth helps there. Since I started working mostly on desks with a depth of 80 cm in front of me (or 31 inches that is) it's gotten usually pretty easy to squeeze in a notebook or a paper (also hanging the monitors on the wall, so that no foot is on the desk any more, gives another extra 10 cm).
I actually have around 70 cm, but for some reason it still doesn’t feel right. Maybe removing the monitor foot is key.
After reading your comment, I tried moving the monitor as far as I could to free up space. And it’s actually better. Notebook is next to the keyboard on the right side, not sure if that’s optimal when looking back and forth
I am in the same camp. A year ago I switched over to taking notes on a Kindle Scribe, and as a voracious note taker it has been going very well. There are a few small negatives:
- twice a page of text just vanished completely, in roughly 500 pages written in the past year, due to some shenanigans with the selection tool
- Over 40/50 pages notebooks don't seem to export reliably. So for my work notes I start a new notebook every month (I average approximately 1.5 pages per workday)
- I no longer scribble as many unspoken impressions down as I did with paper (where I had known before, that small writings in the margins on some paper of mine where as save from looking in to, as the insides of my Jeans' pocket watch pocket)
Positive:
- I can send PDFs of my notes out within a minute to any email
- a lot less to carry around, I just make sure to keep it with me, nearly all the time
- organizing notes retrospectively is a big leap forward from paper - I can just select lines of text I wrote and move them around, even shrink them a little (to fit an extra line of text or two on the same page)
So far I haven't gotten used to actually extracting the notes with the Kindle application on my PC, it's always going over Amazon's servers whenever I click "share" to export my notes...
How do you go about having AI conversations with your notes?
> So you aren't breaking any laws of physics, you are just able to make much better tactical decisions.
With respect I'd like to disagree on this subtly. A lot of games have the client send their cursor position at relatively frequent updates/packages (i.e. sub-second). So the server knows pretty precisely in which direction and to which object a player is looking.
This in turn can be readily used upon when using wall-hacks, as most players, who use wall-hacks tend to almost faithfully follow objects behind walls with their cursor, which good moderators can usually spot within a few seconds, when reviewing such footage (source: I was involved in recognizing Wall-Hacks in Minecraft, where players would replace textures, to easily find and mine diamonds underground).
The biggest heuristic is that you suddenly get much more consistent. Valorant uses this to ramp up how intrusive its kernel anticheat becomes and often forcing you to turn on more intrusive features to continue playing the game
> It’s an ugly, toxic cycle that bottoms out at everyone constantly having their knowledge and competence questioned over things they know and can do, by people who don’t and can’t.
That rings so true in my head. Being too open and transparent got me quite a lot of misery already. More than once, I got the work of months discarded, because some other (shiny or new) approach was deemed to provide a better solution -- only to the effect that it was later discovered that it was the worse approach.
Apparently it is very easy to miss in the pursuit for the best solution, in unfortunate favor of one's preconceived notions.
Another prime example on the typical arrogance of this trade, of computer scientists:
My brain immediately goes like: You nitwit, base64 comes back from E-Mails, where you would work with Mail-Server's conception that your mails were all written, legible characters. Of course you should expect newlines, potentially whitespaces and tabs in it.
But that would be stupid of me. There's so much old knowledge and know-how we carry along for many decades - around 50 years in case of mail and SMTP. Unix and Linux are a specially egregious example, with so many conventions.... just ran into a long standing bug a few days ago, with some GECOS implementation (that's 62 years old stuff). We do a lot of good in throwing out the now unnecessary old stuff and separating the wheat from the chaff. Again and again.
In so far: Thanks for the pointer on that Base64 appears strange (also please do not let us talk about groff).
Surprisingly lots of good advice, especially when one got a few years of professional experience.
> Do It Scared
True. I've deep dived enough topics and technology to confidently say that pretty much everyone is just cooking with water as they say. .... The special specialist doing super professional job with X? - well they are probably just using this or that standard tool. Resolving problems with some very sound approaches (which they probably taught themselves through experimenting, through practice).
Especially with software: Just have a go at it. The worst that could probably happen is that you need to reinstall your Operating System (and please don't ask me, how I developed some kernel-patch-performance-evaluation)
I agree that most of the great technologists I’ve worked with have been like this. But it’s certainly not true of everyone. I’ve got one friend who is what I would classify as a slow learner. He doesn’t pick up new languages or technologies well and he flounders for a long time when out outside of the areas he feels confident in. What he is though is incredibly consistent within that space he is comfortable with. I can turn around amazing things during a hackathon or POC when the realities of every day development don’t get in the way, but I’m average at best at day to day delivery of the same type of work. This guy though churns out code reliably every day. Over and over again. He’s able to achieve more through attrition than I am by being able to quickly learn new things and then quickly get bored.
So I completely agree with the sentiment of “just have a go at it”. It’s what I’ve done all my life. But I also acknowledge there are many very productive developers who can’t really do that well. Consequently he has a much more difficult time landing new jobs, and he’s much more likely to hold onto jobs for way longer than I would have bailed on it. He’s a lot more difficult to hire than someone who is confident in their ability to figure things out along the way.
reply