Pro Tip: You can drastically reduce keystrokes in any editor by using your brain before typing.

Some fucker installed a keylogger on my Ubuntu laptop at home and registered it as a systemd service. From Wireshark, it's sending each keystroke to a server in France using irc. Tried accessing the server but the moron shut it down immediately. It's the last time am fucking installing code from prebuilt binaries. If I can't build it from source then fuck off your sniffing cunt. I was about to log in into a database from that machine.

UPDATE: I found the actual file sending the keystrokes but it's binary. Anyone know how I can decode a binary file?

To the people saying "I need to reduce my keystrokes" when they are asked why they omit semicolon's;

It is a common delusion thinking that we spend most of our time typing, when in reality we spend most of our time gazing into the abyss thinking to ourselves "oh my god what have I done".

Anything that decreases your typing time but increases your time in the abyss is a terrible tradeoff.

- D. Crockford

Worst code review experience?

Hard to pick just one, but most were in a big meeting room with 4+ other developers not related to the project and with some playing Monday-Morning-Quarterback instead of offering productive feedback.

In one code review, the department mgr reviewed the code from a third party component library.

<brings up the code on the big screen>
Mgr: "I can't read any of this, its a mix of English and something else."
Me: "Its German."
Mgr: "Then why is 'Button' in English? This code is a mess."
Me: "I'm not exactly sure how I should respond, I mean, I didn't write any of this code."
Mgr: "Yes, but you are using it, so it's fair game for a code review."
Me: "Its not really open source, but we can make requests if you found something that needs to be addressed."
Mgr: "Oh yes, all this...whatever this is..<pointing again to the German>"
Me: "I don't think they will change their code to English just so you can read it."
Mgr: "We paid good money, you bet your ass they'll change it!"
Me: "I think the components were like $30 for the unlimited license. They'll tell us to go to hell first. Is there something about my code you want to talk about?"
Mgr: "<Ugggh>...I guess not, I couldn't get past all that German. Why didn't we go with an American company? Hell, why didn't we just write these components ourselves!?"
Me: "Because you gave a directive that if we found components that saved us time, to put in a request, and you approved the request. The company is American, they probably outsourced or hired German developers. I don't know and not sure why we care."
Mgr: "Security! What if they are sending keystrokes back to their servers!"
Me: "Did you see any http or any network access?"
Mgr: "How could I? The code is in German!"
Monday-Morning-Quarterback1: "If it were me, I would have written the components myself and moved on"
Me: "No, I don't think you could for less than $30"
Monday-Morning-Quarterback2: "Meh...we get paid anyway. Just add the time to the estimate."
Mgr: "Exactly! Why do we even have developers who can't read this mess."
Me: "Oh good Lord! Did anyone review or even look at my code for this review!?"
<silence>
Mgr: "Oh...ok...I guess we're done here. Thanks everyone."
<everyone starts to leave>
Me: "Whoa!...wait a sec..am I supposed to do something?"
Mgr: "Get that company to write their code in English so we can read it. You have their number, call em'...no...wait...give me their number. You keep working, I'll take care of this personally"

In they nicest way possible, the company did tell him to go to hell.

When the coffee you had in the morning kicks in all at once.

Now my heartbeat is faster than my keystrokes

1. Start ur day posting Good morning in #general thread.
2. Say Hello Team in the project group (slack).
3. Have a standup call with the entire team and discuss what everyone would be doing.
4. Evening 6 pm go on another call with the team explaining what you did for the day.
5. Time tracking software should always be on, so we can monitor your keystrokes.
6. Track time on Clickup tasks, as well as move them to appropriate tabs indicating their status.
7. Before u log off, post a detailed report on the group chat about what you did for the day.

Surely, this will increase productivity of the team, right?

Hell no?

Continued from previous post.

The man with hoodie walked down a dark alley. At distance, a house which looked haunted stood. As he entered the house he sighed a relief. Once inside, he descends to the basement where an old computer sat. He turned on the computer and smiled. The screen showed a prompt. With fews keystrokes, a series of scripts begin to execute. Finally at the bottom, a text blinked.
"Awaiting Connection........"

The CPU was recovered from rubble and brought to General's office as per his order. It was connected to a power source and it started to boot. A prompt showed up. A man in suit, suggested perhaps it expected a login. The General sat on his chair smoking a cigar thinking on what action must be taken next.

While men in suit discussed about the CPU, someone plugged in a LAN cable. The General who was lost in thought, saw this from corner of his. A moment passed. General sprang from his chair, hurling his cigar to the floor. As men in suits, looked at the General's display of athletic behavior they sensed the tension. Everyone turned to the CPU now connected to LAN now.

Far way, the screen on hooded man computer showed. "Connected".
A series of scripts started to execute.
Cold wind was all that could be heard out side the General's office building and the house, where hooded man sat in the dark.

Hears co-working typing loud repetitive keystrokes. Wants to shout out:

FOR THE LOVE ALL THINGS
HOLY WRITE A SCRIPT!

I've got a report that one of our machine-learning purpose computers broke down suddenly. I took a look and saw that the thing was stuck at the BIOS screen. The thing that was off was that it did not prompt for any keystrokes. Like, if there were a BIOS problem, there would usually be a prompt to press <F1> to ignore or something, right? But, nope! Even BIOS did not do jack s#!+.

I tinkered around the peripherals for an hour before finally finding something odd - why the f*<k does this computer have a screen hooked up via f*<king D-Sub????????

Yup, somebody hooked up a screen to the base motherboard via D-Sub when they rearranged other computers, even though that machine needed to have a screen hooked up to a GPU via HDMI.

🤦

Just a short "dafuq?" about VS Code.

I have a MacBook Pro from last year, so it's a capable machine. And there I was today, sitting on the train, coding some Python in VS Code.

Suddenly it got all laggy. Like, one second behind my typing, dropping keystrokes, stuttery scrolling... the whole deal. The system itself was perfectly responsive and the activity manager showed the CPU at 30%. After a minute or so, it magically recovered and worked as if nothing ever happened.

What the actual fuck was VS Code doing? I mean, it's a fucking text editor. In 2019 this should be a bloody solved problem! There's absolutely no reason to use around 30% CPU in the first place, and use that much and still *lag*. Holy crap, and people ask with a straight face "what's wrong with reinventing everything based on web technologies?" Fuck everything Electron-based. Make it ElectrOFF already.

*takes deep breath*

So, editor suggestions are welcome. I used Sublime Text 3 before VS Code, I'll likely return to that.

I'm sitting here at my desk, with headphones on, waiting for a colleague to "finish just one thing" while Hearing his keystrokes and looking in the void.
Why did you call me in the first place wtf

I'm doing a code review on a huge feature, basically touching every part of our authorization logic, and man... It's like my colleague writes his code to be as hard to read as possible. He's 60+ and you'd think he'd have learned how to write good and clear code, but nope. "Let's make it cool cool and I look like I'm a genius. And if I can spend 3 keystrokes less on a function I'm happy". Fuck me.

For some reason I keep over engineering stuff to the point I spend 2 hours thinking the best way to do something. I'm making the backend for a project of mine and I wanted somewhat decent error handling and useful error responses. I won't go into detail here but let's say that in any other (oo) language it would be a no-brainer to do this with OOP inheritance, but Rust does OOP by composition (and there's no way to upcast traits and downcasting is hard). I ended up wasting so much time thinking of how to do something generic enough, easily extendable and that doesn't involve any boilerplate or repeated code with no success. What I didn't realize is that my API will not be public (in the sense that the API is not the service I offer), I'm the only one who needs to figure out why I got a 400 or a 403. There's no need to return a response stating exactly which field had a wrong value or exactly what resource had it's access denied to the user. I can just look at the error code, my documentation and the request I made to infer what caused the error. If that does not work I can always take a quick look at the source code of the server to see what went wrong. So In short I ended up thrashing all the refactoring I had done and stayed with my current solution for error-handling. I have found a few places that could use some improvement, but it's nothing compared to the whole revamp I was doing of the whole thing.

This is not the first time I over engineer stuff (and probably won't be the last). I think I do it in order to be future-proof. I make my code generic enough so in case any requirements change in the future I don't have to rewrite everything, but that adds no real value to my stuff since I'm always working solo, the projects aren't super big and a rewrite wouldn't take too long. In the end I just end up wasting time, sanity and keystrokes on stuff that will just slow down my development speed further down the road without generating any benefits.

Why am I like this? Oh well, I'm just glad I figured out this wasn't necessary before putting many hours of work into it.

My first software.. Okay. So first time I ever attempted was with my father, i was around 8 or so, i remember very little from it, but in nutshell, i somehow ended up at his job having day off school or something, no idea.

Apparently he was bored, so he decided yo show me... Basic. Yep, thats right. Frking basic. Anyway, he shown me some really basic stuff in basic, and pushed the envelope really hard, just trying to force into me more and more in these 8hrs. I started with filling screen with "o" characters. Most of times he was telling me what to write with elaborate explanation why. At the end of the day, we finished with simple maze game where player was "o" and maze walls was #. Without any goal, or anything.

Next day i was at point 0, understood nothing from it except how to handle keystrokes (and belive me, that for me was huge mindblow, and even bigger mindblow that it actually made prefect sense).

I dont remember much, but later i started with father-assisted c++ and some pascal. I immidietly loved c++ but dropped learning it for (NullPointer) reason.

Thats not really project imho, so now time for my actual first project.

It was about time when ARK survival evolved was a fresh thing, i was playing it a lot. Server admin became buddy. We all complained about max level cap, but to change it in config you needed to input whole new xp curve.

At that time i had great familiarity with google and computers, some thought i was some kind of PC god (seriously I heard someone saying so about me lol) just becouse I could ressurect most cases of broken windows. And I had next to zero programming expirience. It was about to change. I made first c++ actual program, that was making xp curve for you. It took me just bearly 2 days and was series of cin, cout, one file open, some maths in loop, and done. Maths was very bad. But i pushed it into steam forums, and one guy responded how.bad my math was, so we colabed on making 2 iteration. Took around week. Than half a year passed and we wanted go big. Go gui. I had no freaking idea how making gui looks like. Community liked my cli tool, we had quite a lot of downloads, why not go GUI. And thats when I discovered QT framework. And we had few features in mind... It took us half a year to make it. From 60 lines of code i jumped into 1k lines of code. We pushed it and immidietly started working on 4th version with much greater customizability etc.

Than i finished 18 and found a job. Job in php. I got it becouse I made this project.

Now project is abandon. This project also gave me a lesson that donations will not feed you.

Edit: and before you think about my father that he was nice person to show me code, trust me, i dont know bigger dick than him.

I got many reasons to hate my old Dell Studio-1557, but if there is one thing I love about it, it is its keyboard. I don't have much technical keyboard knowledge, but it's just comfortable for me. Wide keys and short keystrokes, no gaps between them (keys are actually sloped on the edge and fit together) and most importantly, no num pad.
So now that i feel it needs to be retired after 9 yrs of loyalty, i can't find a successor for it that have my old Studio's keyboard-feel. Most of laptops in the market have small keys with orthogonal edges and lots of space wasted as gaps between them (like new Dells), a useless (for me) num pad and worst of all, small miniature arrow keys (like thinkPad) and other navigations seems to be new designers fashion.

I'd be glad if some one introduce me a laptop with a similar keyboard to mine (in the picture)
Or what do you propose, should i care about the keyboard at all? are these new designs easy to take up with? wouldn't i suffer a keyboardalgia?

edit: no macs btw :)

1. Being fast doesn't meant your smart.
2. Think thrice before you apply your idea, saves not only time but your keystrokes.
3. Google is just the last resort, if you can crack it yourself there is nothing better.
4. Cleanliness is Godliness, not that believe in God but if I see you writing shit and messed up code then you gotta do it again.
5. Useless code is important, it will help you get lost later when you come back.

And most importantly, LISTEN.

I'm starting to get annoyed with Android Studio. I generally enjoy it as far as an ide goes, but why does it need to update so often??? Seriously it feels like every time I open it I get a notification saying to update something or other.

On a somewhat related note but not actually Android Studio's fault, I have decided that IdeaVim sucks. It's good sometimes, but it can't keep up with my keystrokes, so I end up with random characters in my code because even though I hit "jj" (remapped to ESC) then start typing other commands, I end up with the next command being read as still in insert mode, then it catches up with the escape and pops me back to normal mode. It drives me crazy because then I have to go back and undo the extra characters, then redo my command and it kills my flow. I'm not even that fast of a typist, it shouldn't be that hard to keep up...

Currently the only 3rd party tokenization VSCode supports is a massive pile of RegEx. There's a whole discussion about how procedural tokenization could be supported without running extension code in the UI thread. The central argument against delegating this to an external worker is that if the reply doesn't arrive fast enough it might interfere with characters typed later.

1. Any computer that can run VSCode can execute somewhere in the order of a _billion_ instructions per second. To a program, the delay between keystrokes is an eternity. The only way to run out of time here is if either the dev isn't aware that the request is time sensitive, or the framework communicates to the OS that the task isn't urgent and an arbitrary amount of work is scheduled before it.

2. Chromium is the pinnacle of cybersecurity and its primary job is to sandbox untrusted user code. You don't need another thread to do it.

3. This use case fits squarely in the original design objectives of Webassembly.

Whenever someone would like to look up something on my laptop I take a deep, dark pleasure in watching them first struggle to move the mouse with the broken track pad, then drowning in desperation after they realise it's a Linux system with i3-wm.
But alas, I am a generous God and help them with 3 lightning fast keystrokes to open my installed browser - which is eLinks.
That usually does them in 😬

When you pull the drives out (or change boot order) because fast boot on that (New, clever) motherboard seems to ignore bios keystrokes on boot... only to have the system blinking saying no boot drive found...
Why didn't you just take me to the bios?!?
<reboot>

The customer service dept at Koss Headphones sent me an adapter gratis for my Pro 4/AA headphones so I could listen to loud rock and roll on my pc. I've been using Koss exclusively since I rec'd a pair for Christmas in 1971. Despite the natural deterioration in sound quality on a PC, I found I could hear more on certain Rolling Stones soundboards [the ones in question are Philadelphia 1972 and New York City a week later]. So I penned a rather whimsical email to Michael Koss, who actually replied with a letter, the kind we used to lick stamps for and put in a mailbox.
OK, that PC died. And the HP I have somehow has a really loose jack so the whole mechanism will slide out if you move the least little bit. It happened so often I became shell shocked about listen to loud music on my headphones at night when my nabes were sleeping because I didn't want to wake anybody up.
Finally, after too much jiggling, the end bit of the adapter got stuck in the headphone jack. Koss sent me another adapter gratis. Last night, I got out my headphones, removed the new adapter from its envelope, and inserted tweezers into the jack to pull the broken off bit out.
Except the broken off bit slid deeper into the jack. On my own, I have been able to rig the pc so I can use the speakers. And a friend who can remove the bit of the jack stuck in the jack will be over in a couple of days.
I went online and googled the methods others have used to remove broken off bits. That was worth the keystrokes!
In any case, I just wanted to say something about the irony of expecting the problem to be over and then having a few days more to live with the broken bit.

Q: Is there a software which can record my keystrokes and clicks and then translate that into a Power shell or Python or any script?

A prayer from a colleague:

Our silicone god which art in the SSD
Italic be thy name
Thy computing come
Thy bus be done
On the screen
As it is on the hdd
Give us this day our daily blue screen
And forgive us our keystrokes, as we
forgive our keyboards.
And lead us not into restarts, but
deliver us from memory leaks: For thine is the
memory, and the cpu, and the
bus, for ever. Amen

Beautiful is it not :)

!rant
Any tips on fixing a mechanical kb that registers certain keystrokes twice or even more?