Waiting for this day....

Well, they're'nt lying

#include <helpme>

Ok guys I kinda need your help. I have to write a python project for my school in 3 days and instead of saving everything in files I want to have a database. So my question is can you suggest the most simplest and easiest db to create and connect to Python for a few simple tables. Also the easiest to set up on another computer since my professor will probably want to try it at home.

Also I have to learn Python in 3 days, since I already know a couple of languages, I'm confident I can pull it off. Why I'm asking for help is I need to document it all, that will probably take a chunk out of these 3 days.

FYI. Copied from my FB stalked list.

Web developer roadmap 2018

Common: Git, HTTP, SSH, Data structures & Algorithms, Encoding
------
Front-end: HTML, CSS, JavaScript > ES6, NPM, React, Webpack, Responsive Web, Bootstrap
------
Back-end: PHP, Composer, Laravel > Nginx, REST, JWT, OAuth2, Docker > MariaDB, MemCached, Redis > Design Patterns, PSRs
------
DevOps: Linux, AWS, Travis-CI, Puppet/Chef, New Relic > Docker, Kubernetes > Apache, Nginx > CLI, Vim > Proxy, Firewall, LoadBalancer
------
https://github.com/kamranahmedse/...

Good news: my department is great and furnishes the developers with a special dark space to work with big monitors in a small, quiet room.

Bad news: someone from sales is camped out in here and the glare from the all-white word documents they have open is causing my oh-so-perfect screen (in dark mode, of course) to be unreadable.

As an added perk, they brought in a laptop and are using that almost exclusively. There are dedicated laptop chairs away from my workstation they could use instead.

Also, the entire room smells like their body spray. My only salvation is that it's almost five and maybe they'll leave soon.

Front-end vs backend

When good developers are afraid of refactoring and adding new classes is something to be feared, you need to rethink your architecture.

In fact, if there's ever that "dark corner" of code that no-one likes to work with, you've got to fix it.

It's like continuous deployment. We do it often because it's hard and having to deploy regularly forces us to make it easier.

Fun fact: The word "sudo" in Spanish means "I sweat", which, in colloquial speech, can also mean "I don't give a fuck"

Sometimes i fucking hate my job.

Fuck

The S in Intel stands for Security.

So I just wanted to log back into windows. Typed in the password. Wrong password...
Then I tried being super accurate while typing and also checked keyboard layout, etc. Still, wrong password.
Then I noticed that the letter p is not working. Shit, keyboard seems to be broken.
On screen keyboard -> p is not working...

What the hell? What kind of error is this?

NT Kernel code has to be something like this:
if(timeSinceLastError > someValue)
keyboard.p.enable = false;

I guess you could also replace the keyboard error with some random error.

If you encounter this, restart Windows.

Just wrote a Python script to generate me a JSON file.

I forgot the 0th command line argument is the file you're running...

On first test it overwrote itself.

During highschool years I was using Ubuntu for the 1st time and saw this strange looking icon named vim....had to reboot PC to close vim 😅
Not my proudest moment.

I can't work because someone else broke the build and they're in meetings all day.

That's how you know it's real Enterprise development.