Unplugging internet for productivity

>unplugging internet for productivity
Does it work

Depends on your line of work. I have to look things up, and it's usually a lot faster to do that online.

It's about will power and getting "into the zone" for my part. It's difficult to get started, but once I have, I can work for hours on end.

Yea this
In this day and age internet is a huge resource no matter what you do. Just get good and focus on the stuff you want to get dobe istead of getting distracted.

>Just get good and focus

>come here to make productivity thread
>find your productivity thread

Unplugging the internet is kinda tough when you're programming... Gotta search up syntax and errors messages. How do you guys manage to stay focused on the internet?

>Gotta search up syntax and errors messages.
Rarely. I look up API documentation, parameter ordering etc, stuff I quickly forget.

>How do you guys manage to stay focused on the internet?
Don't go to Sup Forums, and that's about it for me.

All you need is the fucking API reference. You can download that.

>addicted to image boards
>literally wake up and start browsing before I get out of bed, waste all my free time after work browsing, and the last thing I see before I go to sleep is an image board
>block all of the IP's in my router's firewall
>end up not even using my fucking computer because I just gravitate to my phone that isn't connected to my router
>end up just removing the firewall rules so at least I can use my desktop instead of the fucking phone

Sometimes the reference alone is shit, and you need code examples.

If people programmed in 1990 without internet, I'm sure we can do it as well!

I just block distraction websites with hosts file.

You first.

stack overflow is so useful that not having it would hurt productivity more than having fewer distractions would help it

I'm pretty sure that the architectures of most modern technology stacks are infinitely more complex than they were in 1990.

Also, in the 90s people used BBSes and IRC to aid them in programming.

can't make any syntax errors if you don't have any syntax
t. Lisp programmer

Yeah I'm sure its possible but its much faster and easier to understand if you see an example when you're still learning.

>t. pajeet

>t. professional fizzbuzzer

When you're still learning a language or framework or library or whatever, that's an entirely different thing.

Normal use means that you have a rough idea what you need and how to use it, but you just need the details.

Do pajeets commonly just copy and paste blocks of code from stack overflow?

I'm seeing this meme often and they seem to be notorious for making shitty programs.

Even when you're not "still learning", you can never just rely on your own ideas because that's how backwards shitty implementations get made. Sometimes other people write genuinely better code than you, and without seeing their code and learning from it you will stagnate.

went there a couple of times to diagnose some really obscure problems with really retarded software (java and mysql were involved).
Literally no other reason to visit it unless you're a pajeet or want to learn something completely outside of your specialization area.

Yeah, except for the fact that your weak ass character makes you click 30 things on the web and spend 3 hours before getting back to work. It's like a Pandoras box, super easy to open and almost impossible to close.

everyone does (unless they're retarded/arrogant). the difference is a pajeet will just say "ok it works!" and move on. a good programmer will figure out what exactly the code does and rework it to fit their software better.

This exactly. When I stick to my own shit for too long I find my self developing shitty habits because "it works". Then when I watch some tutorial I find there is a much better way of doing something.

>I'm pretty sure that the architectures of most modern technology stacks are infinitely more complex than they were in 1990
>infinitely more complex
lmao

I never implied I didn't go on stackoverflow for examples to problems and integrate a good solution into my program.

If you know exactly what to look for and how to search, SO is gold. It's like troubleshooting for Windows, if you don't know what you're looking for you end up having to sift through retards that tell you to put your GPU in the oven so the soldering tin solidifies better.

I don't have this problem.

If anything you have it easier today. MUCH easier.

dumb javascript faggot

Maybe if you work with some high-level scripting stuff, but definitively not when you work with low-level stuff.

>implying javascript is easy
You know nothing Jon Snow

Okay autists, can we return to discussing productivity?

Do you seriously think low level coding is harder today than it was in the 90s?

You're either stupid, or inexperienced, or both.

Well, unless you did something REALLY sketchy you don't need to troubleshoot stuff. Usually. Given that your job doesn't involve some really retarded stuff like proprietary technologies or CPP-like languages...

Fuck sorry for bringing up programming, I have unleashed an autistic spurg flood upon this thread.

Let me redeem my self by bringing up the Pomodoro technique. Anyone tried it? Do you find that it works?

>Do you seriously think low level coding is harder today than it was in the 90s?
It definitively is. When I started programming, there were only one CPU and two levels of caching and you had explicit control over them. Now you have a bunch of caches, you need to consider NUMA strategies, you need to consider L3 localities, you need to consider race conditions that can occur because you're programming a multi-CPU architecture, you need to consider pipelining and microcode instruction fusioning.

A lot of stuff has been simplified, but architectural complexity has increased along with Moore's law. Primitive microcontrollers were so piss easy to program, people just programmed them using assembly because the instruction set was so small. Modern x86 machines from Intel has an instruction set that literally requires two 400 page manuals to cover.

>You're either stupid, or inexperienced, or both.
You're speaking from your ass.

>Anyone tried it?
Yes

>Do you find that it works?
It works if you use your 5 minutes to take a walk. If you use them to lurk Sup Forums, it doesn't work.

Just download wikipedia

Oh wow, a bunch of features. So hard to code stuff when your clock runs at 3,4ghz. Try programming a DOS game in 1990 that runs on 40-60mhz. Good luck writing your own audio and graphics drivers while you're at it.

Do you know a good app? I'd like to be able to customize it to work for 50min break for 10min. The one I downloaded only does 25min work and then 5min break.

And I mean a computer app (preferably browser).

>Oh wow, a bunch of features.
Those are not "bunch of features", those are architectural properties you need to care about when you implement stuff.

>So hard to code stuff when your clock runs at 3,4ghz
Speed is irrelevant here.
>Try programming a DOS game in 1990 that runs on 40-60mhz.
That's not hard at all, in fact, a bunch of DOS games relied on clock frequency for timing, which is why many early computers had a Turbo button for increasing the internal clock from 33 MHz to 66 MHz.

>Good luck writing your own audio and graphics drivers while you're at it.
Audio drivers are piss easy, user. Especially for internal piezo speakers. Seriously, you can even make one at home and program it using an Arduino. It's not freaking hard.

As for graphics driver, just writing to the VGA buffer mapped into the lower region of memory is also piss easy. You can even try it yourself, just memory map the first 10 MB of memory and write garbage data to it, you'll see that you get random pixels on your screen (your OS will also probably crash, but that's because you're not only writing to the VGA buffer but also a lot of other stuff).

Not really, I just hacked together this

#!/bin/bash

let "period = 0"

if [[ ! -z $1 ]]; then
let "period = $1"
fi

case $period in
1)
title="First pomodoro!"
message="Take a 5 min break."
;;
2)
title="Second pomodoro!"
message="Take a 5 min break."
;;
3)
title="Third pomodoro!"
message="Take a 5 min break."
;;
4)
title="Fourth pomodoro!"
message="Take a 20-30 min break."
;;
*)
title="Pomodoro!"
message="Time for a break."
;;
esac

dbus-send --print-reply --dest=org.mpris.MediaPlayer2.spotify /org/mpris/MediaPlayer2 org.mpris.MediaPlayer2.Player.Pause &> /dev/null
notify-send -u critical -i dialog-information "$title" "$message"
for (( i=0; i < 3; i=i+1 )); do
/usr/bin/mplayer --volume=100 /usr/share/sounds/freedesktop/stereo/suspend-error.oga &> /dev/null
sleep .8
done


And set Xfce keybindings to invoke it with different parameters when I press Ctrl+Alt+shift+P (for Pomodoro).

I'm not even going to respond to your bullshit.

>I have no idea about how computers work and therefore I don't know how to respond

But (You) already did.
God, you are pathetic.

>I'm the worlds best programmer, everything is super easy to me

I don't think so.
Also, anyone please post some old meme with Jackie Chan's tweet... Today is a bad day and blah-blah-blah

That's not at all what I said, I'm just saying that you don't know what you're talking about and you think modern computers are somehow simpler than older ones, because more software exists to make your life easier.

Programming modern graphic cards, for example, are infinitely more complex than just controlling pixels by writing to VGA buffer memory. Denying this is all sorts of retarded.

Just because you use some sort of LEGO game maker framework where you just drag stuff together, doesn't mean that under the hood a hell of a lot more is going on.

Here you are friend

I'm not saying that modern computers are simpler. I'm saying it took about 3 times as much effort in the past to write any workable code at all.

search in books v.s. search in google

>I'm saying it took about 3 times as much effort in the past to write any workable code at all.
That's completely relative to what kind of framework and toolchain you rely on. Of course, building a userspace application is a lot easier than it used to be. Creating a interface for a PLX-switch DMA engine requires that you consider cache-coherence and CPU location, which is more complex with today's caching strategies than it used to be.

In those days all you had was 2 books and maybe a professor to ask something if you were lucky. It was harder, no argument there.

>In those days all you had was 2 books and maybe a professor to ask something
You ordered the Intel manuals which arrived with snailmail, and you could sift through them quite quickly.

These days, the manuals are in total several thousand pages long. It was not harder back then, quite the contrary, only different.

And you could always ask on IRC or a BBS, or refer comp.c.lang on Usenet if you were absolutely stuck.

Post more motivational content Anons.

You're not alone user.