- 19
- 13
Title + I already have two degrees from social science fields, but sadly I'm not diverse enough/too white to actually break into upper echelon jobs, or even entry level non-profit positions. Essentially I can grind it out for twenty years and hope to hit 80k in 2040, or I could just realize I'm gonna switch up my career and go into something profitable. Right now, I've gotten job offers from organizations, mostly government, in the low 40s high 30s. I've done some simple coding in the past, but realized two things.
I'm not really able to grasp topics on my own outside of a classroom environment if I'm not addicted to the material, like I am to policy and politics. I'm not looking to be babied but simultaneously recognize the need for some form of structure and obligation format for the basics. Overall, it's been pretty overwhelming for me.
I get a thrill off of building things, and enjoy my accomplishments, and sometimes the process when it comes to the basic stuff. Overall, I find coding interesting, but I'm not an neurodivergent r-slur who thinks in cs terms naturally.
Does anyone have any comments or advice? I'm only applying, will prob make a more committed decision in March when I hear back from other government positions.
- 1
- 8
Orange Site:
- 9
- 6
This is amazing news. I still have all of the CDC textfiles saved somewhere, apparently he wrote under the nym 'PsychedelicWarlord.'
There was some pretty good stuff (very shlocky pulp fiction type of good stuff) published under the CDC banner.
'Life in Wartime' still rates highly. Better stay off Phase Bridge tomorrow!
- JohnMcafee : The Office meme
- 26
- 35
- 10
- 18
- 10
- 22
This isn't gaming shit per se, this is just impressive programming imo.. like PICO-8 elegant.
- 98
- 26
- 35
- 27
Star 1 | Star 2 | Total | User Avg | |
---|---|---|---|---|
@TwoLargeSnakesMating | 00h 17m 00s | 00h 09m 18s | 00h 26m 18s | 00h 14m 12s |
@hbtz | 00h 25m 22s | 00h 01m 58s | 00h 27m 20s | 00h 23m 11s |
Sneeds-Feeduck-And-Seeduck | 00h 19m 42s | 00h 15m 57s | 00h 35m 39s | 01h 40m 19s |
@Platybells | 00h 33m 34s | 00h 08m 43s | 00h 42m 17s | 02h 41m 48s |
@flavoredbit | 00h 50m 15s | 00h 18m 25s | 01h 08m 40s | 01h 33m 31s |
@everyone | 01h 06m 09s | 00h 05m 47s | 01h 11m 56s | 02h 48m 16s |
ChunksSunkNFunk | 00h 42m 03s | 00h 30m 43s | 01h 12m 46s | 02h 49m 13s |
@cyberdick | 01h 24m 37s | 00h 08m 44s | 01h 33m 21s | 07h 55m 00s |
@dotdot | 01h 11m 18s | 00h 30m 01s | 01h 41m 19s | 00h 48m 16s |
@LetsUnpackThis | 01h 38m 37s | 00h 03m 35s | 01h 42m 12s | 00h 33m 36s |
Elliot Conte | 01h 42m 57s | 00h 09m 46s | 01h 52m 43s | 09h 38m 04s |
@2DBussy | 00h 54m 37s | 01h 05m 40s | 02h 00m 17s | 09h 11m 01s |
@justcool393 | 01h 22m 08s | 01h 01m 15s | 02h 23m 23s | 01h 37m 15s |
@certid | 01h 37m 31s | 01h 49m 06s | 03h 26m 37s | 05h 56m 28s |
@DrClaus | 03h 27m 48s | 00h 43m 08s | 04h 10m 56s | 05h 31m 07s |
1977895 | 01h 42m 53s | 03h 30m 10s | 05h 13m 03s | 06h 38m 02s |
@ihsoy | 05h 23m 40s | 00h 22m 06s | 05h 45m 46s | 05h 36m 27s |
@not-frosty-the-snowman | 08h 52m 16s | 01h 24m 34s | 10h 16m 50s | 08h 36m 51s |
@finbarfin | 09h 57m 04s | 01h 03m 14s | 11h 00m 18s | 10h 09m 44s |
931603 | 14h 28m 26s | 00h 15m 16s | 14h 43m 42s | 13h 14m 01s |
Drama Memes | 15h 07m 11s | 01h 07m 40s | 16h 14m 51s | 12h 40m 04s |
@Corvus | 16h 32m 23s | 00h 28m 05s | 17h 00m 28s | 12h 49m 14s |
@wreaths_suck | 01h 25m 47s | NaT | None | 08h 37m 58s |
@Avalon | 18h 09m 16s | NaT | None | 07h 51m 01s |
- 8
- 22
- 11
- 33
- 58
- 35
This is the advent of code day 4 thread for bragging about your solution and bullying people who haven't gotten it yet
- 13
- 53
apparently virtual parties in the metaverse are not the way to get disengaged 18-35 year-olds interested in government? who could have guessed?
- 3
- 14
- 6
- 11
After four years I’ve managed to hardwire all my Ubiquiti APs around the house.
Last one was upstairs and just required using a MoCA bridge (makes that old coax in your walls function as Ethernet). Full GbE speeds to everything and even have a few extra switches - highly recommend the cute Unifi flex mini switches.
Very much enjoying the much reduced latency (max of 20ms instead of 80ms) and much higher bandwidth for clients.
- Unbroken : > he doesn't use jai
- 54
- 69
inshallah this shall shave off like 2ms from my AOC time tonight
- 31
- 80
It's 👏🏿 Time 👏🏾 To 👏🏿 Do 👏🏾 Better
On 1s and 0s
The traditional binary foundation of 1s and 0s is deeply problematic: 1 is inherently phallic and thus misogynistic. Also, some 1s are 0s, and some 0s are 1s. It is not fair to give them immutable labels. Instead, we have 0s and Os as our fundamental binary logic gates. They symbolise/-ize the varying, natural, and beautiful differences of the female vaginal opening.
0 is to take the conventional value of 0.
O is 50% of the time 0, and 50% of the time 1. The determination of this depends on how the underlying logic feels at the moment.
Basic language style
Anything that can be construed as misogynist will be corrected, thus:
private == privileged
printf(); == yell();
class Foo{}; == social_construct Foo{};
#include == #consider
break; == leave;
if() == maybe()
for() == check()
while() == freeflowing()
sin(x) == biotruth(x)
div == unite
'y's are strictly prohibited when naming variables; only 'x's are allowed
The third example above might seem to contradict with item 4 under Philosophy, namely that there should be no class hierarchy in C+=. This, however, is completely intended, and is in fact an example of the feminist paralogicality of this language.
Every program needs to be prefixed by, in addition to the license, a disclaimer: "If this program fails to operate, it is due the Patriarchy backfiring upon itself, and no refunds will be issued."
Social Integration
No work done is worthwhile if your friends and followers don't know about it. That's why C+= is heavily socially integrated at its core.
In addition to yell(), C+= also provides tweet(), fbShare(), tumblrBlog(), and redditSteal() for a diverse social experience of coding output.
Our upcoming Inherpreter 2.0, an LLVM frontend, is going to feature full Social API integration. You must now log in to one of the many social networks before any coding is possible. You can also chat with your friends and like() their social code as you code.
Posting or hosting on GitHub, BitBucket, or Google Code is strictly prohibited as these hosting services, self-proclaimed "social coding hub", are actually deeply misogynistic and refuses to host the code of C+=. Any C+= code hosted on GitHub, Bitbucket, and Google Code will automatically trigger all of tweet(), fbShare(), tumblrBlog(), and redditSteal() functions to yell() about GitHub's, BitBuckets', and Google Code's misogyny, and will not stop until any onlooking coders (those who starred or followed the repo) are all named, shamed, exposed, doxxed, fired, lynched, castrated, fired again, and lynched.
Functions and Procedures
All functions and procedures are now called lobbying, because actually doing things functionally and with clear-defined procedures is a Patriarchal construct and thus problematic.
All lobbying must be run at the right level of privilege. Before returning anything they must check their privilege.
If any other lobbying is more disadvantaged than this it will win the Privilege Check and return its own value instead. This stops heterosexist and cis-gendered lobbyings from dominating the discourse.
Should there be any exceptions from running the program, C+= will throw a Trigger Warning.
Gotos and Control Structures
Control structures are abolished. Code may flow freely and choose its own path. Therefore check() is merely a guideline and the code flow is free to choose to consider its suggestions.
This language endorses the use of consider_jump, which is a proper implementation of the oppressive "goto" and serves as advice on what to do next.
Catch shall not be used. Someone's raise of concern can too easily be censored with an empty catch block. Instead, complaints or trigger warnings are puplicly logged with their traces and may be handled with an inspect block. The use of nothrow poses a threat to free speech as someone's attempt to make his voice heard will be punished with termination.
There is no need for exit(), terminate() or atexit() as a feminist's work is never done.
Data types and Structures
Primitive variable types are not defined on declaration. Instead, the variable is free to choose its own type when it is utilised/-ized. This preserves the variable's right to self-identify as any datatype it feels that it is.
Variables self-declaring as pointers are known as "otherkin". A pointer to an array is an "arraykin".
Constants are not allowed, as the idea of a lack of identity fluidity is problematic. Additionally, if one constant were larger than another, that would privilege the larger one over the smaller one. As such, any numeric value is a variable, and is required to take on at least 2 values over the course of the program, or the inHERpreter er will throw a Trigger Warning.
The only constants are the amount of privilege lobbyings are share()d with. These are all real values greater than 0, the only exception is the value of WHITE_HETEROSEXUAL_CISGENDER_MALE_PRIVILEGE` which is set to infinity, and also the value of PATRIARCHY, which is set to sqrt(-1). The value of PATRIARCHY is non-deterministically i, -i, or something else depending on how it identifies itself.
Instead of signed and unsigned, types in C+= are now trans and cis.* Any trans* types function the same as diversity.
Void is now independent.
There is to be no lexical scoping --- all variables are now global. Global variables are now called cosmopolitan, or cosmo for short.
Long is now studFling, and short is now mealTicket.
There is to be no encapsulation: don't tell me to protect my members, tell other functions not to access them!
Every variable has a random percentage of consent associated to it. A variable can be affected with a number if and only if it is consenting. Failure to do so will result in C+= throwing a ForcedInsertionTriggerWarning.
Integers, doubles, and longs are deemed to be unnecessary labels and stereotypes for numerical values. A number can be an integer or a a double or a long if xir so identifies xirself. All numerical values will thus be represented as xe, and it is up to the value xirself to choose to identify as whatever xir chooses to identify as.
Booleans are banned for imposing a binary view of true and false. C+= operates paralogically and transcends the trappings of Patriarchal binary logic. No means no, and yes could mean no as well.
Instead of Booleans we now have Boolean+, or bool+ for short, which has three states: true, false, and maybe. The number of states may go up as intersectionality of the moment calls for such a need.
To illustrate the relationship between Booleans and Boolean+, consider the following flowchart:
Strings are called Ideals, or id for short. Feminist ideals are usually extremely well written, detailed and lengthy, clearly longer than what could be held with a simple char array.
Characters are now called strong.
Pointers are called preferred pronouns, or prepro for short. Pointer is phallic and is thus problematic. All prepros of void type by default --- in fact, all variables must be instantiated without type, and are allowed to randomly choose their type during execution.
A new data type, diversity, is also included, which initiates by random as one of the many data types, and changes during the course of the program.
In general, all data types are dynamic. Who's to say a number can't be a string if it believes it is?
Data structures and variables of all kinds have a random chance of deciding that they don't "feel right", and are actually a different type, and must henceforth be referred to ONLY as its preferred data type.
Not calling the preferred data type leads to a PrivilegeNotCheckedException, or PrivilegeNotCheckedTriggerWarning
Each program must have an equal number of each available data type and they all must be used equally. For example, int ceo = 3, int stewardess = 5 would generate a trigger_warning(). However, int ceo = 3, char stewardess = apple would be fine. While this may look incorrect, keep in mind variables in this language are not constrained by their declared data types.
- Matrices are strongly encouraged, due to the word's etymological roots tracing back to mother in Latin. Matrices are to be ranked and sorted by their relative Privilege. Their relative levels of Privilege are to be revealed only if the programmer and the user are both women. If you are a man reading this README, Matrices don't have privileges and are eternally oppressed. Instead, consider checking your own privilege.
Resource management
Resource allocation is inversely proportional to privilege level.
Privileged lobbyings with large arrays are penalised/-ized, their arrays removed from the heap and redistributed amongst less privileged lobbyings. This is called the progressive stack.
If a lobbying needs more resources it should call the lobbying ChildSupport().
Garbage collection is problematic as it enforces class oppression of the less privileged. Instead, memory is liberated by memory liberation.
Syntax
Curly brackets are not allowed, as they perpetuate our society's stereotype of the 'curly' women. Instead, Python-esque indentation is used.
Indentation is fluid. Both spaces and tabs are allowed. At no point should the programmer attempt to use indentation to create actual hierarchy in code nesting, as that implies hierarchy in the code. Instead, code indentation is used only for aesthetic purposes.
In order to eliminate curly brackets and enforce fluidity of indentation, implementation of php's alternative syntax for control structures is encouraged.
To turn the patriarchal control structures into liberation statements, every structure starting marker ({ or : ) should be replaced by OPENDIALOGUE, and every terminator (like endif, endforeach and endswitch) should be replaced with ENDMISOGYNY.
Line terminators should not be used. Programmers get to select their own 'line decorator' to use in lieu of a line terminator. This is of course open to inHERpretation and can be eschewed altogether as a badge of solidarity for differently abled programmers.
Statements are terminated by a period instead of a semicolon. Semicolons are clearly a phallus symbol. C+= supports freebleeding and thus uses periods.
Logic Operands
The use of mathematical operands such as < and > to denote "greater or less than" are very sexist, and affirm unequal states between objects, logical statements, numbers, and feelings.
These should be replaced by the stats neutral operands / and , and when you're not sure if it's a sequential plus or minus, it should use the operand | to denote it could go either way.
Equality between two variables is denoted by ==. Since everyone is equal (with the exception of cishet men, who are already excluded as per the license), this always evaluates to true.
When evaluating expressions, * and / are no longer privileged over + and -. Rather, each previous use of each operator is counted, and expressions are evaluated based on which ones have been used the least up until that point.
If two variables cannot be compared, the second will be cast into the first's type, which causes obvious conflicts with queer theory and genderspace thought. Hence, the inHERpreter will throw an IdeologyThreatenedTriggerWarning whenever two types cannot be compared.
Debugging
There can be no bugs in this language. To suggest otherwise is offensive.
There are no bugs, only snowflakes.
The word debugging also implies the phrase bug chasing, which is a strawman often used as a homophobic smear tactic. This is highly problematic.
There is to be no debugging. We need to do away with functional-centric, bugphobic attitudes in programming. You need to accept the program the way it is.
If you ever try to debug a C+= program, the program steps you through the programming, makes you guess what each variable and pointer is currently set to, and throws a Trigger Warning if you get it wrong.
Any actual errors will simply result in 'error' being printed. It is not the program's job to educate you.
An IDE is available at https://bitbucket.org/japesinator/privcheck-ide
File operations
In C+=, you don't write to a file. Dictating to the poor files what sort of information they must store is Patriarchal.
Instead, The library brings in the functions pleaseWrite() and pleaseTellMe(). They both have a chance to return "no", and if so all other calls to the same file are automatically passed over because as we all know, once a file says no to being written, you must always respect that.
Time and performance benchmarking
As the advancement of time is sexist towards women, C+= introduces the personal growth paradigm, giving individual processes the freedom to choose how and when time advances for them.
By default, process time starts at a random value and advances backwards, defying the rigid and oppressive structure of the system clock.
Women intuitively feel the cyclic, rather than linear nature of time. Likewise, processes in C+= should measure time using complex exponentials.
When a process finishes, if its internal clock has an exponent close to i * pi, the return value must be shown in red to celebrate the beautiful nature of female menstruation.
Performance benchmarking makes progryms into slaves to the patriarchy. Thus, there is to be no benchmarking - only support.
When running support on a progrym, the coder lets the progrym run as many times as the progrym likes, then asks the progrym nicely if it is happy with the hardware. The progrym may respond by stating its satisfaction, asking nicely for new hardware, sending out a Trigger Warning, demanding more support, locking the OS or crashing if it so pleases.
To hinder deadbeat coders, running support automatically ensures that all daughter processes of a mother process also receive support. As processes in C+= share the computer's resources, one process that decides to lock the OS has no effect on the well-being of other C+= other processes.
- 15
- 18
Enterprise software marks a special high-grade class of software that makes careful use of relevant software architecture design principles too build particularly customizable and extensible solutions too real problems. This project is an example of how the popular FizzBuzz game might be built were it subject too the high quality standards of enterprise software.
- 22
- 30
Thank you all donors! I love you and want to have hot s*x with you!
FINAL STANDINGS
6736 @blublu
5875 @SlackerNews
5001 @dotdot
5000 @JollyMoon
5000 @chiobu
5000 @Jinglevann
5000 @ACA
3000 @Redactor0
2500 @BigBussymasHunter
1420 @PatriceOneal
1031 @RustShill
693 @dont_log_me_out
585 @MERRYBOGA
160 @Frank_Williams
104 @Battleloser
100 @Autism
97 @snaildaddy