7 ms·

Python for the code, Postgres for the backend, Markdown for the frontend. Because I am too lazy to reinvent the wheel, and most of that is good enough. I would

by 1996 8y ago

Python for the code, Postgres for the backend, Markdown for the frontend. Because I am too lazy to reinvent the wheel, and most of that is good enough. I would have much preferred to use Perl, R, dotnet, or just about anything else, but there was an already made library in Python that was good enough for 90% of my needs, and 100% with some elbow grease, so my lazyness made me learn Python instead! But wait- it gets dirtier than this! The code is done is Vi, with no care in the world about version control (rsync does most of what I need: backups), and deployed to servers by manual SCP, with no automatic tests, no care about CD or automatization - yet: as I need more and more servers, I realize I have to spend time learning say ansible to provision them faster than a copy paste of bash (I have low standards but I won't do curl|bash, just... no) but I am delaying that as much as possible to concentate on implementation. The servers are on Debian VMs on Azure, just because they gave me free credits and do not perform as bad as AWS. When the free credits run out, I will move to DO. Then I will see what else I can use, and that will be the right time to care about ansible or whatever. It is as ugly as I can get away with to get my MVP out, using tech from 1996 lol.

paulddraper 8y ago
> with no care in the world about version control (rsync does most of what I need: backups) I get the simplicity...but using git/hg/svn is just so easy. And you can easily rewind, diff, view changelogs for a file, etc.
- 1996 8y ago
  git takes typing more commands and bothering about the repo. rsync is run by cron.
  - darpa_escapee 8y ago
    If you want to do something dirty, you could schedule commits with cron.
- nlowell 8y ago
  I am not convinced that git is easy... I believe it's very powerful if you put the time into learning it, but anything with 50,000 separate guides on the internet must be somewhat unintuitive, right?
  - dvfjsdhgfv 8y ago
    Not necessarily, you can also use it just like CVS in the old days, with 2-4 commands, should be enough for your needs.
  - castlecrasher2 8y ago
    Eh I couldn't rebase to save my life but basic git is fairly easy to grok and useful.
    - jondwillis 8y ago
      It’s exactly like merging but you have to resolve any conflicts commit-by-commit instead of all at once in a merge commit. Useful for if you’ve been working on a feature and want to pull in changes your colleagues have made on the develop or master branch without muddying up your history with merge commits. Having clean history makes diffing easier for code reviews. I’ll admit even after years of rebasing, I still screw it up from time to time.
  - spiritcat 8y ago
    Definitely are way more intricacies to the cli than I'll ever learn, but 99.7% (estimated) of my git usage is running the same 4-5 commands all day, which I have aliased to convenient acronyms. Don't even have to think about it. The other stuff is there if you need it though.
  - nwatson 8y ago
    Use a GUI like SourceTree from Atlassian, makes dealing with "git" so much easier.
    - jondwillis 8y ago
kjeetgill 8y ago
I agree with you 95%. If you're running something basic with less than 5 people this is reasonable with one minor caveat: I'd still use git. Hell even on my own I frequently use git for single file shell script. Commit a working copy. Tweak it to add a feature. Decide it's unmaintainable. Revert to before I fucked it up. Also, theres a decent half-step between ssh and Ansible: mssh. You can run ssh across a set of hosts quite trivially. It working on the order of a few dozen machines just fine.
- 1996 8y ago
  my personal take on mssh is: for host in host1 host2 host3 ; do...
  - kjeetgill 8y ago
    True, that works too. I'm good with bash but I find many aren't. I actually work with bigger setups (think thousand machines) that have range set up which is a big value add with mssh but not in the kinds of small setups we're discussing.
brett40324 8y ago
Im confused why Python, Postgres, Markdown is 1996 tech? Im really confused by your entire post, actually.
- 1996 8y ago
  I meant all this is super old school and super dirty, except markdown that is somehow recent (2004) Yet markdown is not essentially different from running sed to render something into html, which I would have totally done if I hadn't also needed some other features like basic math that would have been too tedious in sed
  - brett40324 8y ago
    I mean yea, but it is like saying, "I respond to server requests with HTML, it's soo 1994". I do like the sed idea, btw :)
    - 1996 8y ago
      lol yes I would not have used anything else if I could have gotten away with sed! Speaking of HTML, I do my HTML sites all static, with no external scripts or resources! It is so 1994.. or so 2018??
openIce 8y ago
How can you people even call yourselves hackers if you are too lazy to learn Git?
LinuxBender 8y ago
For my hobby stuff I am similar. Perl and either SQLite or Text files. Sometimes Postgres, but I rarely find it is needed, even for fairly popular anonymous boards. I use vi. I do use git locally, but I don't trust it, so I also use rsnapshot, probably similar to your rsync. You might want to try rsnapshot some time if you have not. It uses less disk space by hard linking dupes using a perl script.
eagsalazar2 8y ago
People saying they wouldn't use git don't know git. I admit it does take investment to learn but once you are over the hump it is insanely easy and useful (yes even easier than rsync and 10x more useful). Especially when you consider that using rsync precludes your from collaborating even with one other person which is crazy easy if you use github (for example). People not using git: get over the hump, it is worth it, even on little side projects.
- 87 8y ago
  Recently I've seen a friend collaborate with teammate by sending each other zips. Using Skype! And as far as I can tell they're pretty productive. Dedication and hard work generally tends to produce results regardless. When you use git you still need to use it right. How many times have you cloned a repo just to find out it won't build/run/compile without help? Personally, with small projects - more often than not. And I have a habit of asking if they do know for a fact it's going to build without assistance. It doesn't help. I like git as a glorified change-log, slack commit messages especially. I try to keep everything tidy and build-able as much as anybody. But I'll still give people an archive (with .git included). And ironically this keeps git tidier as you don't obsess over whether or not to commit certain things.
  - existencebox 8y ago
    When I first started learning how to program, I didn't know git existed. When I eventually learned a year later, I was already well acquainted with sending myself zips by email, and using email as "history". Git was quite scary to me at the time, (merges and reset/revert as I recall) so for a good year or two more I just kept using emails. It certainly wasn't pretty, but it required almost 0 mental cycles, worked without question, and actually gave some really nice features comparatively. (searching for a "commit" using complex queries) We were eventually forced to use git/hg/svn for some courses over that time, so I became comfortable out of necessity and now vc for anything serious; had to unfortunately even use TFS for a while. (guilty secret, for many toy projects, I absolutely just have a folder on my fileserver and rely on its backup/replication, zipping the folder if I want to "snapshot".)
ecdavis 8y ago
Pretty much the same except that I use `git push` to deploy instead of `scp`. If I ever need to move beyond a single server that'll be an issue but for now it's fine.
ekovarski 8y ago
Curious as to why you'd prefer Perl? Is it because of a technical reason or just because of familiarity? Thx

by 1996 8y ago

paulddraper 8y ago

> with no care in the world about version control (rsync does most of what I need: backups) I get the simplicity...but using git/hg/svn is just so easy. And you can easily rewind, diff, view changelogs for a file, etc.

1996 8y ago
git takes typing more commands and bothering about the repo. rsync is run by cron.
- darpa_escapee 8y ago
  If you want to do something dirty, you could schedule commits with cron.
nlowell 8y ago
I am not convinced that git is easy... I believe it's very powerful if you put the time into learning it, but anything with 50,000 separate guides on the internet must be somewhat unintuitive, right?
- dvfjsdhgfv 8y ago
  Not necessarily, you can also use it just like CVS in the old days, with 2-4 commands, should be enough for your needs.
- castlecrasher2 8y ago
  Eh I couldn't rebase to save my life but basic git is fairly easy to grok and useful.
  - jondwillis 8y ago
    It’s exactly like merging but you have to resolve any conflicts commit-by-commit instead of all at once in a merge commit. Useful for if you’ve been working on a feature and want to pull in changes your colleagues have made on the develop or master branch without muddying up your history with merge commits. Having clean history makes diffing easier for code reviews. I’ll admit even after years of rebasing, I still screw it up from time to time.
- spiritcat 8y ago
  Definitely are way more intricacies to the cli than I'll ever learn, but 99.7% (estimated) of my git usage is running the same 4-5 commands all day, which I have aliased to convenient acronyms. Don't even have to think about it. The other stuff is there if you need it though.
- nwatson 8y ago
  Use a GUI like SourceTree from Atlassian, makes dealing with "git" so much easier.
  - jondwillis 8y ago

kjeetgill 8y ago

I agree with you 95%. If you're running something basic with less than 5 people this is reasonable with one minor caveat: I'd still use git. Hell even on my own I frequently use git for single file shell script. Commit a working copy. Tweak it to add a feature. Decide it's unmaintainable. Revert to before I fucked it up. Also, theres a decent half-step between ssh and Ansible: mssh. You can run ssh across a set of hosts quite trivially. It working on the order of a few dozen machines just fine.

1996 8y ago
my personal take on mssh is: for host in host1 host2 host3 ; do...
- kjeetgill 8y ago
  True, that works too. I'm good with bash but I find many aren't. I actually work with bigger setups (think thousand machines) that have range set up which is a big value add with mssh but not in the kinds of small setups we're discussing.

brett40324 8y ago

Im confused why Python, Postgres, Markdown is 1996 tech? Im really confused by your entire post, actually.

1996 8y ago
I meant all this is super old school and super dirty, except markdown that is somehow recent (2004) Yet markdown is not essentially different from running sed to render something into html, which I would have totally done if I hadn't also needed some other features like basic math that would have been too tedious in sed
- brett40324 8y ago
  I mean yea, but it is like saying, "I respond to server requests with HTML, it's soo 1994". I do like the sed idea, btw :)
  - 1996 8y ago
    lol yes I would not have used anything else if I could have gotten away with sed! Speaking of HTML, I do my HTML sites all static, with no external scripts or resources! It is so 1994.. or so 2018??

openIce 8y ago

How can you people even call yourselves hackers if you are too lazy to learn Git?

LinuxBender 8y ago

For my hobby stuff I am similar. Perl and either SQLite or Text files. Sometimes Postgres, but I rarely find it is needed, even for fairly popular anonymous boards. I use vi. I do use git locally, but I don't trust it, so I also use rsnapshot, probably similar to your rsync. You might want to try rsnapshot some time if you have not. It uses less disk space by hard linking dupes using a perl script.

eagsalazar2 8y ago

People saying they wouldn't use git don't know git. I admit it does take investment to learn but once you are over the hump it is insanely easy and useful (yes even easier than rsync and 10x more useful). Especially when you consider that using rsync precludes your from collaborating even with one other person which is crazy easy if you use github (for example). People not using git: get over the hump, it is worth it, even on little side projects.

87 8y ago
Recently I've seen a friend collaborate with teammate by sending each other zips. Using Skype! And as far as I can tell they're pretty productive. Dedication and hard work generally tends to produce results regardless. When you use git you still need to use it right. How many times have you cloned a repo just to find out it won't build/run/compile without help? Personally, with small projects - more often than not. And I have a habit of asking if they do know for a fact it's going to build without assistance. It doesn't help. I like git as a glorified change-log, slack commit messages especially. I try to keep everything tidy and build-able as much as anybody. But I'll still give people an archive (with .git included). And ironically this keeps git tidier as you don't obsess over whether or not to commit certain things.
- existencebox 8y ago
  When I first started learning how to program, I didn't know git existed. When I eventually learned a year later, I was already well acquainted with sending myself zips by email, and using email as "history". Git was quite scary to me at the time, (merges and reset/revert as I recall) so for a good year or two more I just kept using emails. It certainly wasn't pretty, but it required almost 0 mental cycles, worked without question, and actually gave some really nice features comparatively. (searching for a "commit" using complex queries) We were eventually forced to use git/hg/svn for some courses over that time, so I became comfortable out of necessity and now vc for anything serious; had to unfortunately even use TFS for a while. (guilty secret, for many toy projects, I absolutely just have a folder on my fileserver and rely on its backup/replication, zipping the folder if I want to "snapshot".)

ecdavis 8y ago

Pretty much the same except that I use `git push` to deploy instead of `scp`. If I ever need to move beyond a single server that'll be an issue but for now it's fine.

ekovarski 8y ago

Curious as to why you'd prefer Perl? Is it because of a technical reason or just because of familiarity? Thx