Normally I'd be using tools and actually doing mechanical work but the tool we built is finished so we are doing an audit report with trainers that aren't mind so I'm just watching as well.
What work appropriate websites should I use to learn some skills or job advancing lessons?
For example, I'm checking out SQL because I am considering coding for a career. Engineering is going to take too long for me to get more money.
don't forget you need to then use a screen and push the ashes thru then crush any remaining bits manually with a hammer. oh and by the way you won't get any wood or coal or coke to help. good luck!
[ - ] Jiggggg 1 point 3.9 yearsJul 24, 2021 23:27:13 ago (+1/-0)
As much as Jewgle sucks, I have heard great things about the Google certification stuff. I know a guy who did the project management one and now makes $160k "managing projects", i.e. doing virtual meetings a couple of times a day and taking naps. I'm thinking about doing it too, fuck it
a google it support tech? no thanks. project management however is where it's at. if you can keep yourself organized and can manage a team with goal sets its an easy job. easier when you're already technical but not a requirement
Disagree 100%. for 99% of websites and projects SQL will be faster to develop and solve all their database problems with more accuracy. There's only 1 situation where NoSQl takes advantage, if you have more than 10 million simultaneous users who don't need to query transactional level data. This takes us back to 99%, most people and their projects will never get within 1% of a 10 million simultaenous user requirement. Next argument for using SQL. Every fucking webhost already has it loaded and ready to use on the most basic of hosting packages. Why would you quintuple your expenses to flip to hosts like AWS to do the exact same thing with less efficiency in time spent coding and more money spent monthly with more bugs to deal with? The only argument to use NoSQL is if your SQL project exploded, is getting millions of users and you want an easier way to expand capacity by adding more servers. Theres no other reason to take that route unless you like burning money and time for every little project which will never merit nosqls cost, expense or host requirements and wasted extra time coding.
To your comment that making websites isn't programming. You're aware that websites can be more than html and css right? Have you ever looked into node.js backend or php backend programming? Big secret, they both have classes, functions, use algorithms, utilize separation of concerns, have to apply the big O notation for efficiency, and in my opinion, it's more complex than simply going to comp CS degree and learning python and C++ foundations. Learning the full stack of backend + front end + database and all the security required around it is a lot harder than just building apps in C or Python and it takes more time to learn all the involved languages & disciplines which keep changing every 2 years.
[ - ] SithEmpire 1 point 3.9 yearsJul 25, 2021 03:02:06 ago (+1/-0)*
My evaluations of how data should be stored to solve a particular problem have changed a lot over the last decade or so, particularly after watching my own C program seek/select through gigabytes of flat CSV much faster than a SQL query on a table containing the same data.
At present, I ask scrutinising questions about why a flat file isn't appropriate, then I ask whether the Linux file system itself provides enough organisation and permission options (where "find" and "grep" become your query tools), before any relational DBMS is allowed the green light.
Edit: Note that the file system approach integrates beautifully with revision control utilities.
Try making a website with 1000 simultaneous users reading and writing and editing a single csv file instead of using a SQL database and report what happened. Note how the 1000 people simultaneoulsy editing a CSV crashed and gave errors and share violations and glitch data, and began infinitely timing out waiting for another user to close session before they could open read and edit theirs, and how the SQL worked perfectly and just as fast as if you were operating by yourself. Also there's so many queries that have been optimized for sql speed by putting the whole thing in a hash table on the backend. Why would you want to manually loop through csv data to find results when SQL has already spent 30 years optimizing itself for maximum speed while maintaining integrity across many users?
If you'd read what I wrote instead of fangirling over SQL in every reply you post, you would have seen that I tried both and the text scans were faster for my particular use case / application / data set.
If you wanted to know: it has billions of lines/records, the file system provides a lovely category and permissions feature, it can be searched read-only that way by multiple users, and it only updates via a cron task.
So, no. Obviously if I needed over 9000 simultaneous transactions then it would be different, and even then the Linux file system can still be a serious contender if no highly relational aspect is needed, so fuck off with pushing a DBMS for everything and everyone.
The original topic was someone fangirling over nosql, which is the whole reason I brought the defense of the cheaper to host, faster to code, less glitches and much more documented sql into play. When you mentioned text files as an advocate, I wanted to make sure you understood the original topic which is online usage.
[ + ] Sleazy
[ - ] Sleazy 9 points 3.9 yearsJul 24, 2021 21:19:27 ago (+10/-1)
[ + ] Nosferatjew
[ - ] Nosferatjew 1 point 3.9 yearsJul 25, 2021 03:46:23 ago (+1/-0)
XD
[ + ] paul_neri
[ - ] paul_neri 1 point 3.9 yearsJul 25, 2021 04:24:08 ago (+1/-0)
[ + ] Nosferatjew
[ - ] Nosferatjew -1 points 3.9 yearsJul 25, 2021 23:11:40 ago (+0/-1)
[ + ] ToNigIsToNog
[ - ] ToNigIsToNog 0 points 3.9 yearsJul 25, 2021 11:43:03 ago (+0/-0)
[ + ] VitaminSieg
[ - ] VitaminSieg 2 points 3.9 yearsJul 24, 2021 21:13:50 ago (+2/-0)
[ + ] i_scream_trucks
[ - ] i_scream_trucks 1 point 3.9 yearsJul 25, 2021 03:06:00 ago (+1/-0)
[ + ] Jiggggg
[ - ] Jiggggg 1 point 3.9 yearsJul 24, 2021 23:27:13 ago (+1/-0)
https://grow.google/certificates/
[ + ] Bottled_Tears
[ - ] Bottled_Tears [op] 0 points 3.9 yearsJul 24, 2021 23:33:38 ago (+0/-0)
[ + ] account deleted by user
[ - ] account deleted by user 0 points 3.9 yearsJul 25, 2021 07:52:04 ago (+0/-0)
[ + ] Jiggggg
[ - ] Jiggggg 0 points 3.9 yearsJul 25, 2021 13:55:05 ago (+0/-0)
[ + ] account deleted by user
[ - ] account deleted by user 1 point 3.9 yearsJul 26, 2021 06:34:21 ago (+1/-0)
[ + ] Jiggggg
[ - ] Jiggggg 1 point 3.9 yearsJul 27, 2021 02:24:46 ago (+1/-0)
[ + ] ToNigIsToNog
[ - ] ToNigIsToNog 0 points 3.9 yearsJul 25, 2021 11:42:09 ago (+0/-0)
[ + ] vorpal85
[ - ] vorpal85 0 points 3.9 yearsJul 24, 2021 21:16:20 ago (+0/-0)
some non-programmers get started writing really cool spreadsheet code for small companies as employees.
its not programming exactly, but its productive and complex enough to be valued by the staff
in modern years sql is replaced by non-sql databases, designed with opposite strategy of sql .. , https://azure.microsoft.com/en-us/overview/nosql-database/
dozens of NoSQL databases exist and now newest web sites are probably more likely to avoid sql
[ + ] boogienight
[ - ] boogienight 2 points 3.9 yearsJul 24, 2021 23:29:42 ago (+2/-0)*
for 99% of websites and projects SQL will be faster to develop and solve all their database problems with more accuracy. There's only 1 situation where NoSQl takes advantage, if you have more than 10 million simultaneous users who don't need to query transactional level data. This takes us back to 99%, most people and their projects will never get within 1% of a 10 million simultaenous user requirement.
Next argument for using SQL. Every fucking webhost already has it loaded and ready to use on the most basic of hosting packages. Why would you quintuple your expenses to flip to hosts like AWS to do the exact same thing with less efficiency in time spent coding and more money spent monthly with more bugs to deal with? The only argument to use NoSQL is if your SQL project exploded, is getting millions of users and you want an easier way to expand capacity by adding more servers. Theres no other reason to take that route unless you like burning money and time for every little project which will never merit nosqls cost, expense or host requirements and wasted extra time coding.
[ + ] account deleted by user
[ - ] account deleted by user 0 points 3.9 yearsJul 25, 2021 07:53:22 ago (+0/-0)
[ + ] vorpal85
[ - ] vorpal85 0 points 3.9 yearsJul 25, 2021 17:55:59 ago (+0/-0)
explain sudden popularity of dozens of anti-sql databases used in recent years
you are just complaining because you only learned sql
[ + ] account deleted by user
[ - ] account deleted by user 0 points 3.9 yearsJul 26, 2021 06:31:47 ago (+0/-0)
[ + ] boogienight
[ - ] boogienight 1 point 3.9 yearsJul 26, 2021 23:03:50 ago (+1/-0)
[ + ] account deleted by user
[ - ] account deleted by user 0 points 3.9 yearsJul 27, 2021 10:32:11 ago (+0/-0)*
[ + ] SithEmpire
[ - ] SithEmpire 1 point 3.9 yearsJul 25, 2021 03:02:06 ago (+1/-0)*
At present, I ask scrutinising questions about why a flat file isn't appropriate, then I ask whether the Linux file system itself provides enough organisation and permission options (where "find" and "grep" become your query tools), before any relational DBMS is allowed the green light.
Edit: Note that the file system approach integrates beautifully with revision control utilities.
[ + ] boogienight
[ - ] boogienight 0 points 3.9 yearsJul 27, 2021 11:44:42 ago (+0/-0)*
[ + ] SithEmpire
[ - ] SithEmpire 0 points 3.9 yearsJul 27, 2021 20:54:03 ago (+0/-0)
If you wanted to know: it has billions of lines/records, the file system provides a lovely category and permissions feature, it can be searched read-only that way by multiple users, and it only updates via a cron task.
So, no. Obviously if I needed over 9000 simultaneous transactions then it would be different, and even then the Linux file system can still be a serious contender if no highly relational aspect is needed, so fuck off with pushing a DBMS for everything and everyone.
[ + ] boogienight
[ - ] boogienight 0 points 3.9 yearsJul 28, 2021 14:23:31 ago (+0/-0)
[ + ] account deleted by user
[ - ] account deleted by user -1 points 3.9 yearsJul 24, 2021 23:18:03 ago (+0/-1)