Holy fucking shit!
I am not a google fanboy but I just witnessed what is called a pre-launch report on my playstore app!

The app is installed on a dozen of different dummy devices and tested by crawlers automatically! And that's not it : You also get a screen recording of your app being tested on all these devices! Oh my fucking dawg!!
That is cool and useful as hell!

I was in second year of university, and one of my teachers had a company, so he hired me.
The project was for our Lebanese army, the department where they monitor news.

What's required was to create a desktop application that records a UDP stream carrying over a 100 tv channels. And at the same time display them in a grid on the main screen, where the user can select which channels to watch, also which one to hear + fullscreen capability + scheduling a recording + being able to reverse through this live feed

I had little knowledge in multimedia streaming and multiplexing (the art of cramming multiple videos in one stream). So I had to read a lot, and learn how that works, in order to write a decoder, a recorder, and the application. Also the stream itself had issues, the audio would break up, some channels had translations, weird encodings, etc... Plus the pc they were running all of these on was very bad. Multimedia encoding and decoding is really hard on a cpu, so I had to work around that...

After a few weeks I pulled it off, and my boss was happy as fuck, since 2 people before me have tried and failed miserably. But the captain I was developing this for was a pain in the ass. Requirement changes started pouring in like rain + they had technical issues with their signal, which affected the quality of the stream beyond what software can fix.

Fast forward, my boss eventually got fed up with the bs, and as always, decided to blame it on me. I wasn't paid 2 months, and he worked towards making me fail university, which I didn't cause I'm a lot smarter than 90% of those motherfuckers. But he did lay a lot of obstacles since he had high reach in there.

To this day, after 6 years, I still think this was my craziest project. And although that guy was an asshole. I'm pretty sure it's that project that made me who I am today.

When I know a website runs Hotjar or some other screen recording/mouse tracking tools I draw at least one dick per visit.

Online tutorial pet peeves
————————————

My top 10 points of unsolicited ranting/advice to those making video tutorials:

1. Avoid lots of pauses, saying “umm” too much, or other unnecessary redundancy in speech (listen to yourself in a recording)

2. If I can’t understand you at 1.5 - 2x playback speed and you don’t already speak relatively quickly and clearly, I’m probably not going to watch for long (mumbling, inconsistent microphone volume, and background noise/music are frequent culprits)

3. It’s ok to make mistakes in a tutorial, so long as you also fix them in the tutorial (e.g., the code that is missing a semicolon that all of a sudden has one after it compiles correctly — but no mention of fixing it or the compiler error that would have been received the first time). With that said, it’s fine to fix mistakes pertinent to the topic being taught, but don’t make me watch you troubleshoot your non-relevant computer issues or problems created by your specific preferences (e.g., IDE functionality not working as expected when no specific IDE was prescribed for the tutorial)

4. Don’t make me wait on your slow computer to do something in silence—either teach me something while it’s working or edit the video to remove the lull

5. You knew you were recording your screen. Close your email, chat, and other applications that create notifications before recording. Or at least please don’t check them and respond while recording and not edit it out of the video

6. Stay on topic. I’m watching your video to learn about something specific. A little personality is good, but excessive tangents are often a waste of my time

7. [Specific to YouTube] Don’t block my view of important content with annotations (and ads, if within your control)

8. If you aren’t uploading quality HD recordings, enlarge your font! Don’t make me have to guess what character you typed

9. Have a game plan (i.e., objectives) before hitting the record button

10. Remember that it’s easier to rant and complain than to do something constructive. Thank you for spending your time making tutorial videos. It’s better for you to make videos and commit all my pet peeves listed above than to not make videos at all—don’t let one guy’s rant stop you from sharing your knowledge and experience (but if it helps you, you’re welcome—and you just might gain a new viewer!)

"You should record video tutorials of how to do stuff", people say to me.

#1 - I suck on camera. I have a really annoying nasally voice that I just can't stand to hear in my own head, let alone on video.
#2 - I look like every stupid a--hole fat old ugly white guy people love to hate. Nobody wants to see that.
#3 - I suck at remembering what the f$$# I was going to say to begin the video, to show the thing I was going to show, and how to end it without sounding like a complete #@#%@# moron.
#4 - %@%$#@ QuickTime! And any other video screen recording software that NEVER $%#@#$% WORKS for me!! I'll be in the middle of a very complex process I'm demonstrating and BAM! The whole recording crashes. Six takes and six more crashes later and I'm @#%#@# done with trying to do this #@$@#%.

Screenshots and text it is and always will be.

What is the point of disabling the fullscreen button on a youtube video embed?

And funnily enough, I seem to find this on a lot of sites for software, that have a demo video embedded the page or some shit, like a screen recording in this tiny little frame where I can't read anything because it's in this 400 pixel wide box, that I can't fullscreen. I don't understand it at all! What purpose does it serve? You're actually encouraging me to leave your stupid site to view the damn video on youtube.com so I can actually read the text in your stupid ass video.

Why does youtube even give you the option to remove the fullscreen button in your embeds in the first place? They even recently removed some of the "modest branding" features, like hiding the title, or removing the recommended videos at the end, but they thought that this feature was valuable enough to keep?

This may seem irrational to complain about, but I'm confused and befuddled more than anything else? If I'm embedding a video on a website, the last thought I have in my mind is "Oh, I really don't want people to see my video fullscreen. Better make sure I disable that!"

!rant

This is a major part of my workflow, and I wanted people to see it. So I went an inch-deep on quicktime screen recording and ffmpeg flags to produce this low-quality gif.

I pop open the alfred text window with cmd-space, and have it set to use DDG as my default search provider fallback. In this way, I'm able to execute bang-searches without having to load any urls, or even move the pointer.

What kinds of productivity/workflow tricks do you use?

Is it just me or do other people think those tutorials you run across on YouTube where it is just a screen recording and background music are super annoying. I would like at least a little explanation other than you typing in notepad.

))| THE BEST AND WORST WAY|((
))| TO DELETE A LINE IN BASH |((

(Think you can do better? Vote
now on your phones!)

WORST: Hold backspace until satisfied
BEST: Using a pen or other pointing device capable of causing semi or permanent damage to your screen, count how many characters the line in question consists of. Write this down on a piece of paper (after all, your terminal is occupied) and using long division, or any other means, divide this number by two, rounding as you please. Press the "right arrow" key as many times as necessary to reach the end of the line. This might be 0 - if so, congratulations, you may skip this step! Once complete, refer to your piece of paper, and taking your newly calculated number, press the "left arrow" key exactly that many times. If you have a short attention span or are worried you will lose count, take a tally or use some other primitive count recording method. Once the key has been pressed the correct number of times, hold down either control key on your keyboard and take a deep breath - there's no going back now (!) - press the "k" key (you should still be holding a control key!) and take a sigh of relief. You're halfway there! If you need a break, take one. When you're ready to finish the task, hold a control key again and take another deep breath. When you are ready to complete the task (don't hold your breath too long!) press the "w" key. Congratulations!! Your line has been deleted!! Some may call you a fucking idiot for not just pressing ctrl-w at the start, but don't listen to those people! They probably delete stuff by accident all the time! Now, take a lie down, and give a moment's silence for the poor poor line you just brutally dissected and murdered.

Think you can do better? Vote now on your phones!

my fist job... i get to edit a c++ code written by a (mind you) programming company that they teamed with for the past(mind you again) 3 years ...
now just for starters, this code was edited by self taught coders that are really good engineers(they are really good), that didnt really know how the code worked before yet they still changed it, and it worked, how ever they wanted some changes.
i get the project files, and there is not one single comment describing what is happening... only code commented out... and no documentation what so ever were done....
so below are some of my comments that i wrote after i finished adding what i had to add, and fixing what i had to fix:

/*first rule of C anything coding, no actual functions in the header, well let me introduce you to a fully functioning thread running program all in the header, enjoy*/

//used to control the thread
// i honestly dont know why, but it worked soooooo yea...

// TG uncommented // for absolutely no reason what so ever...

//used to communicate with the port

//the message to be sent to the inverter, which has a code that will handle it
//hmmmmmm...

//again not usefull since we are using radioButtons
// same ...
// same ...
// same ...
// they said they dont even use this mode, but none the less, same ...
// calculate the checksum for the message
// ....
// one of the things that work, and god forbids i touch
// used for the status displayed on screen
// used for the (censored :P) status in the message
// used for the (censored :P) status in the message
// not used at all, but the message structure contains it and i refuse to edit that abomination
// used for the (censored :P) status in the message
// used for the (censored :P) status in the message
// just dont ask and roll with it, i didnt want to touch this
// saaaaame ...
// if before true this saaaaaame ...
// value of the (censored :P)
// it pains me to say it again, but this is no use
// (censored :P) input
// (censored :P) input
// only place seen , like for real it was just defined,sooooo yea :D
// well you know how it is
// message string
// check sum string
/****below from feed back****/
// (censored :P) coming in
// (censored :P) coming in
// (censored :P) coming in
// (censored :P)
/****below is the output to the receiver ****/
//(censored :P)
// (censored :P)
// (censored :P)
// (censored :P)
//you thought we were done.... nope, no idea. it comes in the feedback
// not used, literally commented out the one time it was used
// same ...
// XD, man this is a blast, same ...
// nope ...
// used to store the port chosen for the communication
// is a static for the number of data we have recorded so far, and as a row indicator for the recording method
// used to indicate the page we are on in the excel file, as well as the point in physical point in the test
// same ... oh look at this a positive same :D
// same ...
// same ...

Any electrical engineers/tech hackers here?

I am planning to do raspberry & arduino project, basically it’s TV ambilight, but with camera recording the tv screen. Now I have a lot of stuff figured out already, will use wide angle camera connected to raspberry (so I can use it very close to the tv), it’s gonna record screen at lowest resolution which should be enough to analyze colors through opencv and has quite high bitrate. Behind the tv will have led strips around with arduino hooked, which has wifi shield connected.

Now key here is to capture image, analyze it, build array of colors and send it to the arduino to change the colors of led and everything 60 times per second (fps to match tv).

Amount of data is 0.3kb with 100 24bit leds, which is incredibly low.

I am not entirely sure how wifi works internally, but will it be handle to transfer data 60x/s, where not the size is the problem but actually the amount of transfers done? I should also take into account all other appliances using the wifi (pc, philips hue, phone...).

Or will it be more reliable to hook led’s directly to raspberry through wire (which’s also a cheaper option)?

If on windows and looking for reliable simple screen recording software just install CamStudio already and do not waste your life on the other fancy named pieces of shit that cannot even save a properly encoded video file.

So lately, I've been screen recording when I am working on my projects just for fun. I'm using Ubuntu 18.04.1 LTS (Bionic Beaver) and SimpleScreenRecorder for screen recording. I'm using VidCutter for video editing but for some reason, it's giving me some errors and not able to save my edited videos. I don't want to do heavy video editing. I just want something like Windows movie make if some of you remember that.

Our time recording software (based on SAP) triggers a blocking synchronous web service call every single time you do *anything*. Imagine having to wait 10 seconds every time you:
- put a number in a cell
- select a row
- press anything on the screen

Oh and when you lose connection nothing is saved and you have to start again (wtf was it even sending to the server)