- Joined
- Jan 8, 2019
I tried, not one single person could even question my stack, sticker queens like @Dialtone, useless bottom-bitches like @malt ipecac.
I've found it more enjoyable to mog you fat fucks than to try and spread knowledge.
You've all been absolute UNITS with peacocking how you're hot garbage. So keep on with it bby.
Keeping the repo, not care an example of what to do, but because ya'll fit right in.
You guys can't do shit, not worth the effort, have 0 aptitude. So here's my new open source venture "Suck My Ass". And I'll open repo to you all can com and contribute to licking the shit stains off my coin-slot.
To those who did reach out, I'll keep you updated and make sure that you're in a good spot when you graduate or are retraining.
So sperg out. I changed to thread to fit you women: incompetent, lazy, no character and retarded candy ass attitude.
You are wreak of beta cum sluts too.
All the best, ladies.
HMU when you blow the sand out your vag and actually want to do something.
I've found it more enjoyable to mog you fat fucks than to try and spread knowledge.
You've all been absolute UNITS with peacocking how you're hot garbage. So keep on with it bby.
Keeping the repo, not care an example of what to do, but because ya'll fit right in.
The Glowing East German Secret Police Nervous System. Great.
Either you don't know what "facet" means or I don't.
Are you trying to grift money from the government or start a business? Do you consider a person who receives disability payments from the government to be engaged in business?
This objective seems orthogonal to your stated end goal (see below).
On which: could you rephrase this? That just doesn't make sense as it's written.
Fair enough.
I'm not asking to be a dick, but is English your first language?
As that definition states, "facet" is typically used as a synonym for "aspect" or "part". Here is what I think you're trying to communicate:
It's the connection between these two facets that isn't clear to me. Is your plan to train these veterans to build this nervous system?
- Your target customer is the DoD.
- One facet (you could also say "part" or "aspect", for example) of your plan is to provide training to veterans as an alternative to college/trade school/shitty jobs.
- Another facet (again, you could replace "facet" with "part" or "aspect") of your plan is to build this "nervous system".
If you aren't trying to deceive or trick anyone, this isn't really a grift. It would be a grift if your plan were to trick the the government into paying you by dazzling them buzzwords or to trick the government into paying you upfront and then disappearing.
I'm still not sure what you mean by this, definitionally or conceptually.
It sounds like what you're getting at is the distinction between "strategy and tactics" or "objectives and implementations", which is one I understand and agree is important. Keep in mind, however, that you should expect to have an easier time explaining this all to me than jarheads and g-men. I still don't get it.
In the spirit of FOSS, I figured I should post a text version of your ethos statement so the curious don't have to bother with DMing you.
GLOSTASI ICARIAN ETHOS
What is the ‘Icarian Ethos’?
It is a reference to the story of Icarus in Greek mythology, an allegory of the consequences of “complacency and then of hubris”. What is usually taught with the story us neither fly too or too low. General, well accepted advice for general purposes. We aren’t general. The tale of Icarus in our conceptualization of is different. Man must test the limits to push onward into the future. Flying close to the sun is the only pathway to push the limits of our reality and out ability to interact with it. We ask not if we can, rather are we willing? Challenging personal incredulity is the only way to reach new heights. Prove incapability, not accept it as fact means untested. We look to better educate by utilizing conceptualization through practical experience. Open source and project-based learning is the most effectual and long-standing method to teach. We are an apprenticeship for the modern world. We operate under the following ideas:
OUR APPROACH TO SYSTEM DEVELOPMENT AS AN ENTITY
- We are tradesmen.
- We fail upwards.
WHERE ARE WE GOING?
- We break down our problem from top down and enforce README Driven Developmentinitial stages.
- We don’t build the house if we don’t know what it looks like. To properly handle a problem, we must fully understand what the problem it. What is it? What does it mean? How will the near future impact it? Why is it a problem? Granulated detail about the Why/What/When/Where before asking ourselves: How?
- We don’t use tools If we can’t explain their necessity. Technology adaptation under the auspices of “Google is doing it” is not a sound reasoning for architectural technology choices.
- We eat our Wheaties.
- Criticism, and harsh criticism of our ideas is not an attack on the individual’s capability. It’s a gift from someone who took the time to find the holes in their idea so we can make it better. Pride and pedigree mean nothing here.. Keeping ourselves in check is ground up and top down Being a leader isn’t a title of self-importance, it is of overall importance.
- If you’re the smartest man in the room, its time to find a new room. Never aim to be the best at a singular service, always find a next challenge. Be humble and focus on the idea and not the person delineating it.
- We take breaks.
- We Learn Concepts Over Definitions
- What have wrenches, we call them wrenches. The important knowledge about the wrench it’s utility. Same for our tech stacks. We know how to use our tools and bring the right ones to the job.
- We work to engineer under the following concepts:
- Make it decoupled: Such as the wrench and the hammer are separate entities, so will the systems we build.
- Containerize it: A wrench fits a bolt. Our systems and subsystems are idealistically different wrenches to fit the bolts we fasten for the system.
- Archive all of it: When we build we in tandem document and archive our source material. We always have a paper trail for precedence and for reference,
- Make it scale: Planned obsolescence in our conceptualization is the lifetime the scale of our current system. We plan for it and code reusability is important. This is also why we don’t start until we understand what we want to accomplish,
- Make it simple: Simple and clean engineering is the best engineering. We don’t bring a skid-steer loader to garden a small plot, we don’t bring a trowel to move earth for a building. Over-engineering is bad engineering.
We are moving onward into the abyss. There is no better way to put it. We look for uncharted waters, chart them then find the next challenge. Every project we do aims to be a training path for people to learn, and more importantly be able to create. The training paths are meant to challenge, meant to take time and meant to give you the gift of knowledge through experience, not textbook. We have no NDA’s because our company secret is an open book. The environment we cultivate is what produces the best results, not our secret algorithms.
Last, we are embracing freedom of expression and are politically agnostic. Ideas can come in many forms and have different nomenclature. To police thought to impose our will over the agency and creative outlets our organization. Agency over our thoughts and ability to express them as we are is priority. Learn to handle the tides, don’t change them to fit your schedule. We build people to endure the nature of the world, not build a fortress for people to hide from is.
A. GLOWS
DRIVER OF THE STRUGGLE BUS, GLOSTASI
Thank you for the constructive criticism. I think that's what I needed: tough love. Anyway, I'm back and want to learn how to be useful, but I have a question about an edit you recently made to one of your posts.
Which state governments have you been corresponding with? And who are you talking to in the federal system?
It would be extremely impressive if this were all true, but I'm still skeptical. Could you post an example or two of this archived correspondence? Redacting names, of course.
Ok, I see what's going on here. You're breaking me down before you build me back up, stronger than before. This is just like the part of Fight Club where Tyler Durden yells at the prospective ephebe about how he isn't good enough and makes him wait outside the house.
It's okay that you're uncomfortable sharing your correspondence. We can move on to the next step when you're ready.
I can tell you're becoming frustrated with me, and that's okay. I see now that I've made an ass of myself and thrown away whatever credibility I may have had -- all because I wanted to be a fag. Makes me want to vomit.
Are you challenging me to a code-off?
Why do you edit your replies so often after you post them?
Before starting some basic tensorflow machine language transforms, I'd really like to see some proof of your government correspondence.
To those who did reach out, I'll keep you updated and make sure that you're in a good spot when you graduate or are retraining.
So sperg out. I changed to thread to fit you women: incompetent, lazy, no character and retarded candy ass attitude.
You are wreak of beta cum sluts too.
All the best, ladies.
HMU when you blow the sand out your vag and actually want to do something.
Last edited: