What does your typical workflow look like?

>>59666420
Geanie and docs in my web browser

>>59666450
Geany*

>>59666420

compile debug repeat

>>59666420
write some code in text editor -> compile code -> test -> repeat

shitpost on /g/ all day then get my skilsaw out for the night

>>59666420
stack overflow
ref docs
api refs
compile
change stuff
compile
why doesnt this shit work
go to thinking bed
wow duh
compile
repeat

code
compile
debug
code
compile
debug
git commit -m "it almost works"

foreman to run all dependent apps
guard to autorun tests when I change code
vim because master race
strict tdd because not nigger
git commit card work on feature branches
desk check with QA and BA
git rebase to master
jenkins picks up my commit, builds, runs automated testing, deploys to test env
QAs manual test and add new automated tests
deployed to prod, my nigga

open visual studio
new project
code
run
code
run
code
debug

shitpost on /g/ all day
shitpost on /g/ all night

I hold down my foot pedal, Ctrl, Shift, Alt, Windows Key, press c, x, g, then watch as Emacs writes my code for me.

>Check git logs (if any)
>Check Todo / bug list
>Pick something from list
>Open terminal for vim / files in general
>Open terminal for make and other shit
>Code
>Compile
>Code
>Compile
>Mark shit as fixed in Todo file
>Git commit -m "fixes and additions"
>Repeat until shit is finished.

>>59666420
>pick up call
>talk to customer and work on issues
>write code for company in between calls
>everyone uses my stupid scripts
>get paid lower end call monkey wage
>suck it up because nothing lasts forever

I mean... you know...

>>59667272
I really want to start doing this to improve my skills and don't feel like a useless piece of shit browsing 4chan and jacking off all day, but I don't know any active, really interesting projects to contribute

>>59667534
It's not about the interesting shit. It's about the useful shit. Get some lousy tech job, script bullshit, make things easy for people, become an asset.

>>59666420
>posts gif
>not animated

Code, compile, test, if there are no errors, repeat, if there are errors, see output and debug, if I know where and what it is, change it, if not check docs, some DuckDuckGo-ing, ultimately Stack Overflow.

>Pycharm, Stackoverflow, Spotify
>fuck muh qt for a while
>repeat

>>59668077
works for me

might be time for a new computer

Browser(MSDN)
Visual Studio
Foobar

>>59666420
2 terminal windows, some hipster meme editor and a chrome tab with bbc in case I need an emergency fap

open terminal
"jupyter notebook"
Use the greatest workflow technology for anyone in science

completely fucking random every day

lol

fuck how am i ever gonna do anything

haha

>tfw barely do shit but when I do I might be doing something that will be in history books

NO BIGGIE

xD

File: secretsmug.png (696KB, 752x578px) Image search: [Google]

696KB, 752x578px

>>59668605
literally this desu

>>59666761
What programming language/s you use in this workflow?