Originally posted by Sophie
Wait wut. I mean, Bash can get complex for sure but i've never really experienced learning it or at least getting into it and progressing to the level where i am at now as particularly difficult. I'm by no means an expert but you can accomplish quite a bit with some knowledge of the general syntax like if/then/else and a decent grasp of shell commands.
It's definitely possible to hack things together but there's a lot of really awkward constructs in the language. One of the most famous is that "FOO=42" is not the same as "FOO = 42" although neither will throw an error or do anything to instruct you on which one you want. In general spaces work in ways you wouldn't expect because a lot of the language is designed around this "everything's a process or builtin" notion. There's like 3 conflicting string literal escaping schemes, the loop and conditional syntax just weird, functions don't have named arguments although they inherited C's func def syntax. The general ontology of the system is, despite trying oh so hard to be elegant, just a hot mess.
But it's easy because everyone knows how to type commands into the shell, everyone has bash installed, and you _think_ it's portable because of that fact (until you try and send your shell script to someone who doesn't have GNU coreutils as part of their system).
Shell scripting is useful, but as an exercise in language design it's pretty much a list of things not to do.
The following users say it would be alright if the author of this
post didn't die in a fire!
Originally posted by -SpectraL
Do they actually still block certain ports/service running off your ISP, or do they let you and then bitch at you later?
a lot of phone service providers provide 'internet access' through an upstream proxy so that only certain protocols will work, and they can cache popular static content (ie. layout items for facebook, youpube etc.) to free up bandwidth and give the illusion of speed
The following users say it would be alright if the author of this
post didn't die in a fire!
No bananas, no sausages, nothing. Even on pizza, he won't eat sausage. Carrots and cucumbers even. His imagination is large and in charge. Is he on the right rope? Or is he crusin for a brusin in that closet of his? Find out next week on the new DRAGONBALL Z
The following users say it would be alright if the author of this
post didn't die in a fire!
Originally posted by SBTlauien
How long were the training courses at the call centers you worked at? Its like a seven week course where I work.
It was 4 or 5 weeks in all of the ones I worked at. In one of those they made us do dumbass shit like dancing or presentations like it was elementary school during training.
The following users say it would be alright if the author of this
post didn't die in a fire!
i'm currently doing something very similar, setting up a website for a business. we're going with paid protonmail accounts which will enable us to put the company web domain as the @protonmail.com part and keeping all the smtp shit very simple indeed. i can't remember how much it was now for the protonmail accounts but it was fucking cheap. like $6 a month or summing silly.
anyway, i'd be interested with which solution you put in place, and when i put the company website up i will be more than happy to let you know what we decided to go with and why. ours is simple like yours, no ecommerce solutions or anything. just giving the company a simple web presence for now. you know, so they don't look like fucking amateurs and that.
.
The following users say it would be alright if the author of this
post didn't die in a fire!
It doesn't really matter what you start with, just that you stick with it.
Learning to program and learning a programming language are two different things but it's a hard thing to see when you're doing both at the same time (as everybody does). Learning a language is easy, learning how to program is slow and painful. There's no reason to sweat learning multiple languages since all the pain and suffering you're about to go through will only happen once regardless of which language you pick out.
Python is a good choice IMO. If you feel a particular inclination to learn Java or Javascript or anything else then go for it.
If your interest is purely monetary javascript and associated ecosystem is probably the lowest time-to-making-money language you can pick up but it's not the simplest and who knows if that's going to be true in a few years.
The following users say it would be alright if the author of this
post didn't die in a fire!
Originally posted by SBTlauien
"Never stole no CC's but I got plenty accounts And I'll sell them to you for the right amount I got lists for days too many records, deads too And I get advanced paid, no investment to recoup"
Nigga, you get escrow at best.
The following users say it would be alright if the author of this
post didn't die in a fire!
May god have mercy on your soul. FI call centers (well all call centers, but even more so here) have one of the highest rates of turnover of any job ever. You don't even get stuff that's particularly exploitable like CNs/PINs, you're always recorded, and work on a timer.
Having seen how these places operate I think it's the very last place I would want to work. Being an Indian sewer cleaner would be pretty bad but at least there you don't have someone breathing down your neck all day.
Get out while you still can.
The following users say it would be alright if the author of this
post didn't die in a fire!
The following users say it would be alright if the author of this post didn't die in a fire!
