Biggest hurdle: torn between having boobs and missing an arm. I swear some people are under the assumption the brain is in the arm.

I am fully capable of building your network, resolving your outage due to your faulty code, can even tell you how many users your database can support at once. I don't need arms for that. Nor do my boobs distract me that badly.

"but men are going to make your life so hard" yup. And that's true no matter where i go

"all that typing with one arm can't be good for your back" welp. Find me a job that doesn't require a computer. Or manual labor. If you think typing will fuck me up, that's DEFINITELY out of the equation

"you're too pretty, there's no way this can make sense" dafuq you just say?!?!

"why don't you just stay home on disability, I'm sure you qualify, you wouldn't need to work" I'd rather be a fucking trophy wife if I'm staying at home. Fuck that.

And many more.

Sometimes they're fun. Give me more dumb arguments to counter? ;)

THIS is why unit testing is important, I often see newbs scour at the idea of debugging or testing:
My high school cs project, i made a 2d game in c++. A generic top down tank game. Being my FIRST project and knowing nothing about debugging or testing and just straight up kept at it for 3 months. Used everything c++ and OOP had to offer, thinking "It works now, sure will work later"

Fast forward evaluation day i had over 5k lines of code here, and not a day of testing; ALL the bugs thought to themselves- "YOU KNOW WHAT LETS GUT THIS KID "
Now I did see some minor infractions several times but nothing too serious to make me refactor my code. But here goes

I started my game on a different system, with a low end processor about 1/4 the power of mine( fair assumption). The game crashed in loading screen. Okay lets do that again. Finally starts and tanks are going off screen, dead tanks are not being de-spawned and ended up crashing game again. Wow okay again! Backround image didn't load, can only see black background. Again! Crashed when i used a special ability. Went on for some time and i gave up.

Prof saw the pain, he'd probably seen dis shit a million times, saw all the hard work and i got a good grade anyways. But god that was embarrassing, entire class saw that and I cringe at the thought of it.
I never looked at testing the same way again.

Found the value of infinity ∞.

A bold assumption indeed

This is in one of the big 5 (not specifying which for some anonymity)

I apply for an internship.
I get an interview.
I pass the interview and get the internship.
I do great in the internship. Get an exceeds expectations.
I apply for conversion.
I ace the two interviews.
I am told that the hiring committee gave me a yes.
I enter host matching (ie to find a team to join).
...
And that's it. I never get matched (I only met 1 team that had UI focus and I had previously asked to not be put on a UI team so the TL rejected me). 1 year later I'm told sorry the offer is no longer valid.

The annoying bit is that I decided not to apply to grad school and refused all other offers under the assumption that it was a guaranteed spot.

My Perfect Day : Assumption

Woke up at 6. Went for morning walk or do yoga or some sort of stuff.

Came back at 7. Went for daily routine, like bathing and all.

Went to prepare breakfast at 7:45. Prepared some eggs and bread and coffee.

It is 8:15 now. Reading news papers or watching tv and doing breakfast.

At 9 check mails and prepare some stuff.

At 9: 30 went for office. Reached office 5 minute before 10, safe and sound.

Came back at 7 by evening. Did some rest. Prepare dine till 9. Take a bath. Complete the dine.

At 10:30 ready to sleep.

Actual Scenario :

Woke up at 8:30. No time for yoga or morning walk. No time for preparing breakfast as well. Went straight to bathroom. Came back in 20 minutes. Made a cup of coffee. No time for newspaper or tv.

Feeling lazy and tired already. At 9:10 went for office. Before reaching office stopped at fast food joints. buy some junk food. Eat them. Got traffic jam and reached office late.

Started working but feeling lazy. Boss asked twice about the project status and i am unable to think a single line of code.

However, days passed. Boss scolded me. I promised him to finish the work after reaching home.

Reached home at 7:30. Late for no reason. Went straight to bed. Sleeps a hour. But took 20 minutes to leave bed.

Started working on projects i did not complete in the office.

Time fly and it is already 1 in morning. No dinner. Tired as fuck but hungry as well. So made some eggs and eat. Wrapped the task but it is 3:30 in morning and i jumped to bed for sleep.

Loop.

Dear external developer dumbass from hell.
We bought your company under the assumption you had a borderline functioning product and/or dev team. Ideally both

For future reference expect "file path" arguments can contain backslashes and perhaps even the '.' character. It ain't that hard. Maybe try using the damn built in path parsing capabilities every halfway decent programming environment has had since before you figured out how to smash your head against the keyboard hard enough for your shitty excuse of a compiler stops arguing and gives in.

I am fixing your shit by completely removing it with one line of code calling the framework and you better not reject this.
This is not a pull request ITS A GOD DAMN PULL COMMAND.

- Is what i would _like_ to say right now... you know if i wouldn't be promptly fired for doing so :p
How's you guys friday going?

Two programmers have been arrested and currently sit in a jail cell.

Programmer 1: Hey I think we had too much too drink.
Programmer 2: I believe that is a logically assumption.
Officer: You have a phone call.
Programmer 1: Yes, it's my lawyer!

Phone: Is Steve Smith ?
Programmer 1: Yes, who is this?
Phone: Hi, this is Jane calling from Tech Hub Recruiting....
Programmer 1: HOW DID YOU FIND ME?!

Dealing with other technical professionals who cannot think outside their respective boxes.

Here is an example.

A QA (who is very good at her job) said this...

Her:
“We need to get one customer who is willing to pay us a lot of money to make the features they want!”

Me:
“But you realize we are a SaaS company and that means we need lots of customers and constant growth”

Her:
“No, we need to find a customer who is willing to pay us, like a million, to make the features they want. Then we make them for that customer. Then we do that again.”

Me:
“We sell software to small businesses, none of them have a million dollars to pay us, and even if they did then why wouldn’t they build it themselves?

Her:
“Well, when I worked for my last company this is what we did...”

Me:
“So you worked for a contracting company who built software for individual companies. We are not that type of company. We are a SaaS company.”

Her:
“It’s the same thing”

Me:
~Facepalm~

As a software developer and entrepreneur it frustrates me when everyone think everything is the same.

You’ll here things like...

“All we need is to get lucky with one big hit and then we will ride that wave to success, just like Facebook or Amazon!”

Holy fucking shit balls, how stupid can you be!

FB and AZ run thousands of tests a day to see what works. They do not get “lucky”. They dark launched FB messenger with thousands of messages and then rolled it out to their internal team first, they did not get lucky!

Honestly though, I can’t blame them. Most people just want a good job that pays. They aren’t looking to challenge their assumptions.

Personally I know I will be in situations again where my pride, my assumption, my fears are realized and crushed by the market place and I do not want to live in a world of willful ignorance.

I’d rather get it right than feel good.

I would think that in this Lord's year of 2018, dpkg would be able to install two things at once, but alas, my assumption proved to be wrong.

Most pissed off? Must have been the time I created a $10,000 hole in a marketing team's budget after trying to build a Tetris-style Facebook app game (back when FB apps were all the rage). It turned out that Tetris, which was up to that point commonly considered as public domain, had been scooped up by a patent troll who had made a convincing case that he had found and gotten agreement from the originator of the idea (a Russian dude who may or may not have been its original source). I had to scrap the whole project and explain what I did to an old-school manager who didn't even know how to operate a computer. That resulted in my losing credibility as a team member for the next 6 years. I never lived it down. I was pissed mostly at myself for following my assumption and not doing any patent research.

It's my third week in my new company doing my internship. We have daily SCRUM meetings, project briefings, weekly meetings, requirement documents and other stuff - all in French. I only understand less than 50% of what's happening during most of the meetings. There's enormous pressure during meetings where I have to focus on every syllable they utter to try and grasp what's going on. So far they're still under the assumption that I understand more than I actually do. Haven't run into any major fuckups so far. I feel like an exe file in a Linux environment.

So recently I did a lot of research into the internals of Computers and CPUs.
And i'd like to share a result of mine.

First of all, take some time to look at the code down below. You see two assembler codes and two command lines.

The Assembler code is designed to test how the instructions "enter" and "leave" compare to manually doing what they are shortened to.

Enter and leave create a new Stackframe: this means, that they create a new temporary stack. The stack is where local variables are put to by the compiler. On the right side, you can see how I create my own stack by using

push rbp
mov rbp, rsp
sub rsp, 0

(I won't get into details behind why that works).

Okay. Why is this even relevant?
Well: there is the assumption that enter and leave are very slow. This is due to raw numbers:
In some paper I saw ( I couldn't find the link, i'm sorry), enter was said to use up 12 CPU cycles, while the manual stacking would require 3 (push + mov + sub => 1 + 1 + 1).

When I compile an empty function, I get pretty much what you'd expect just from the raw numbers of CPU cycles.

HOWEVER, then I add the dummy code in the middle:

mov eax, 123
add eax, 123543
mov ebx, 234
div ebx

and magically - both sides have the same result.

Why????

For one thing, there is CPU prefetching. This is the CPU loading in ram before its done executing the current instruction (this is how anti-debugger code works, btw. Might make another rant on that). Then there is the fact that the CPU usually starts work on the next instruction while the current instruction is processing IFF the register currently involved isnt involved in the next instruction (that would cause a lot of synchronisation problems). Now notice, that the CPU can't do any of that when manually entering and leaving. It can only start doing the mov eax, 1234 while performing the sub rsp, 0.

----------------

NOW: notice that the code on the right didn't take any precautions like making sure that the stack is big enough. If you sub too much stack at once, the stack will be exhausted, thats what we call a stack overflow. enter implements checks for that, and emits an interrupt if there is a SO (take this with a grain of salt, I couldn't find a resource backing this up). There are another type of checks I don't fully get (stack level checks) so I'd rather not make a fool of myself by writing about them.

Because of all those reasons I think that compilers should start using enter and leave again.

========

This post showed very well that bare numbers can often mislead.

I work as the entire I.T. department of a small business which products are web based, so naturally, I do tech support in said website directly to our clients.

It is normal that the first time a new client access our site they run into questions, but usually they never call again since it is an easy website.

There was an unlucky client which ran into unknown problems and blamed the server.
I couldn't determine the exact cause, but my assumption was a network error for a few seconds which made the site unavailable and the user tried to navigate the site through the navbar and exited the process he was doing. It goes without saying but he was very angry.

I assured him there was nothing wrong with the site, and told him that it would not be charged for this reason. Finally i told him that if he had the same problem, to let me know instead of trying to fix it himself.

The next time he used the site I received a WhatsApp message saying:
- there is something clearly wrong with the site... It has been doing this for so long!
And attached was a 10 second video which showed that he filled a form and never pressed send (my forms have small animations and text which indicates when the form is being send and error messages when an error occurs, usually not visible because the data they send is small and the whole process is quite fast)

To which I answer
- It seems that the form has not been send that's why it looks that way
- So... What an I supposed to do?
- click send
It took a while but the client replied
- ok

To this day I wonder how much time did the client stared at the form cursing the server.

TL;DR you suck, I suck and everybody sucks, deal with it....

------------------------------------

Let me let off some steam, since I've had enough of people hating on languages "just because"

Every language has it's drawbacks and quirks, BUT they have their strengths also. Saying "I hate {language}" is just you being and ignorant prick and probably your head is so far up your ass that you look like an ass hat. With that being said, every language is either good or bad depending on the developer writing in it. Let's give you an example:

If I ware to give you a brick and ask you to put a nail in a plank, can you do it? Yes, it will be easier if you do it with a hammer, but you have a brick, so hammer is out of the question. If you hit your thumb while doing it... well... sorry, but it is not the bricks fault - it is YOU!

JavaScript, yes it has a whole lot of problems, but it works, you can do a ton of stuff and does a good job at that, it is evolving through node and typescript (and others, just a personal pref), BUT if you used js when you ware debugging that jquery (1.0) plugin written in the free time of a 13 yo, who copy pasted a bunch from SO, well, it is not js' problem - deal with it. Same goes for PHP, i've been there where you had a single `index.php` with bazillion lines of code, did a bunch of eval and it was called MVC, but it also is evolving.. thing is all languages allow you to do some dumb stuff so YOU have to be responsible to not fuck it up (which you always DO btw, we all do). Difference is PHP/JS roll with it because the assumption is that you know what you are doing, which again - newsflash - you don't.

More or less I would blame that shit on businesses which decided to go with undergrads to save money instead of investing in their product, hell, I am in a major company that does not invest that doesn't care a whole lot about dev /tech stuff and now everybody's mother is an engineer - they care about money, because investors care about money (ROI) and because clean code does not pay the bills, but money does.

If we get all of the good practices and apply them to each language every one of them has it's place, that is why there is no "The Language", even if there was, we STILL ware going to fuck it up and probably it was going to be even worse than where we are now.

Study, improve, rinse and repeat... There are SENIORS and LEADS out there that are about 25-30 and have no fucking clue about the language, because they have stuck up their heads up the ass of frameworks and refuse to take a breath of clean air and consider something different than their dogmatic framework "way" of doing things.. That is the result you are seeing. Let me give you a fresh example to illustrate where I am at atm:

Le me works with ZendFramework 2.3-2.5 (why not, which is PHP5+ running on PHP7 [fancy, eh]), and little me writes a module for said project, and tries to contain it in its own space, i.e not touching anything outside of the folder of the module so it is SELF-CONTAINED (see, practices), during 2-3-4 iterations of code review, I've had to modify 4 different modules with `if (somthing === self::SOMETHING_TYPE)` as requested by my TL, which resulted in me not covering 3 use-cases after the changes and not adding a new event (the fw is event-driven, cuz.. reasons) so I have to use a bunch of ifs in the code, to check a config value and do shit. That is the way of I am asked to do things I hate what I've done and the fact that because of CR I have lost case-coverage, a week of work and the same TL will be on my ass on monday that things are now "perfect".

The biggest things is "we care about convention and code style"... right.... That is not because of the language, not because of me, not because of the framework - it is some dude's opinion that you hate, not the language.

New stuff are better, reinventing the wheel is also good, if it wasn't you would've had a few stone circular things on your car and things ware going to be like that - we need to try and try, that is the only way we actually learn shit.

Until things change in the trade, we will be on the same boat, complaining about the same shit over and over, you and me won't be alive probably but things will not change a bit.

We live in a place where state is considered good, god objects necessary (can you believe it, I've got kudos for using the term 'God Object'... yep, let that sink in). If you really hate something, please, oh god I beg you, show me how you will do it better and I will shake your hand and buy you a beer, but until then, please keep your ass-hurt fanboy opinion to your self, no one gives a shit about what you think, we will die and the world will not notice...

"four million dollars"

TL;DR. Seriously, It's way too long.

That's all the management really cares about, apparently.

It all started when there were heated, war faced discussions with a major client this weekend (coonts, I tell ye) and it was decided that a stupid, out of context customisation POC had that was hacked together by the "customisation and delivery " (they know to do neither) team needed to be merged with the product (a hot, lumpy cluster fuck, made in a technology so old that even the great creators (namely Goo-fucking-gle) decided that it was their worst mistake ever and stopped supporting it (or even considering its existence at this point)).

Today morning, I my manager calls me and announces that I'm the lucky fuck who gets to do this shit.

Now being the defacto got admin to our team (after the last lead left, I was the only one with adequate experience), I suggested to my manager "boss, here's a light bulb. Why don't we just create a new branch for the fuckers and ask them to merge their shite with our shite and then all we'll have to do it build the mixed up shite to create an even smellier pile of shite and feed it to the customer".

"I agree with you mahaDev (when haven't you said that, coont), but the thing is <insert random manger talk here> so we're the ones who'll have to do it (again, when haven't you said that, coont)"

I said fine. Send me the details. He forwarded me a mail, which contained context not amounting to half a syllable of the word "context". I pinged the guy who developed the hack. He gave me nothing but a link to his code repo. I said give me details. He simply said "I've sent the repo details, what else do you require?"

1st motherfucker.

Dafuq? Dude, gimme some spice. Dafuq you done? Dafuq libraries you used? Dafuq APIs you used? Where Dafuq did you get this old ass checkout on which you've made these changes? AND DAFUQ IS THIS TOOL SUPPOSED TO DO AND HOW DOES IT AFFECT MY PRODUCT?

Anyway, since I didn't get a lot of info, I set about trying to just merge the code blindly and fix all conflicts, assuming that no new libraries/APIs have been used and the code is compatible with our master code base.

Enter delivery head. 2nd motherfucker.

This coont neither has technical knowledge nor the common sense to ask someone who knows his shit to help out with the technical stuff.

I find out that this was the half assed moron who agreed to a 3 day timeline (and our build takes around 13 hours to complete, end to end). Because fuck testing. They validated the their tool, we've tested our product. There's no way it can fail when we make a hybrid cocktail that will make the elephants foot look like a frikkin mojito!

Anywho, he comes by every half-mother fucking-hour and asks whether the build has been triggered.

Bitch. I have no clue what is going on and your people apparently don't have the time to give a fuck. How in the world do you expect me to finish this in 5 minutes?

Anyway, after I compile for the first time after merging, I see enough compilations to last a frikkin life time. I kid you not, I scrolled for a complete minute before reaching the last one.

Again, my assumption was that there are no library or dependency changes, neither did I know the fact that the dude implemented using completely different libraries altogether in some places.

Now I know it's my fault for not checking myself, but I was already having a bad day.

I then proceeded to have a little tantrum. In the middle of the floor, because I DIDN'T HAVE A CLUE WHAT CHANGES WERE MADE AND NOBODY CARED ENOUGH TO GIVE A FUCKING FUCK ABOUT THE DAMN FUCK.

Lo and behold, everyone's at my service now. I get all things clarified, takes around an hour and a half of my time (could have been done in 20 minutes had someone given me the complete info) to find out all I need to know and proceed to remove all compilation problems.

Hurrah. In my frustration, I forgot to push some changes, and because of some weird shit in our build framework, the build failed in Jenkins. Multiple times. Even though the exact same code was working on my local setup (cliche, I know).

In any case, it was sometime during sorting out this mess did I come to know that the reason why the 2nd motherfucker accepted the 3 day deadline was because the total bill being slapped to the customer is four fucking million USD.

Greed. Wow. The fucker just sacrificed everyone's day and night (his team and the next) for 4mil. And my manager and director agreed. Four fucking million dollars. I don't get to see a penny of it, I work for peanut shells, for 15 hours, you'll get bonuses and commissions, the fucking junior Dev earns more than me, but my manager says I'm the MVP of the team, all I get is a thanks and a bad rating for this hike cycle.

4mil usd, I learnt today, is enough to make you lick the smelly, hairy balls of a Neanderthal even though the money isn't truly yours.

Note to my past self:

Thank you for taking care of me and assuming that out of no fucking sudden authorization token will be required to perform an API call!
You saved me so much refactoring and modifications with your tiny little assumption of how fuckups will think :)

Just got a call from someone claiming to be from an ISP (they assumed we were with them because that ISP is one of the popular options, we weren't) they claimed that someone was using our internet illegally (which they cannot find out from what I know unless it really was an assumption), that were using too much data (we are on an unlimited plan and have fibre LOL)

The nerve of some people, my dad was the one who answered the phone and when he handed it off to me, they hung up LOL.

So in saying that i have their phone number thanks to my router's caller id, anyone want it to sell off to more scammer for some good ol' karma?

Assumption is the mother of all fuck-ups.

Never worked before so I'll talk about one of the former staff at my school.

This guy worked as IT and did some teaching in the high school. Early last year, he suddenly disappears for no reason.

Now, I'm going to go in order of what we (the students) found out, not, chronological order.

Firstly, turns out that in class he would make comments about female students. Nothing explicit, just kinda strange. I forget the examples I heard but think like the overly friendly old guy. Those types of comments from a 40-something IT guy. (Some female students knew about this for a long while but I only heard about it after the investigation)

Next, rumor got out that they found some stuff on his computer. I don't know how, but it turned out to be accurate, and we were accurate at the follow-up assumption that it was porn.

After that, the school made an announcement that we had been arrested. Up until then, we just assumed he had been sacked. He was weird sure, but we didn't think criminal.

Some other students looked into the police records, and it turns out this guy had been arrested for possession and distribution of child pornography.

Pretty sick right? Its worth pointing out now that our school has Pre-K through 12th grade students.

I gained a new level of respect for my female classmates after that. I didn't even know that was going on, really wish I could have helped out.

As you can see from the screenshot, its working.
The system is actually learning the associations between the digit sequence of semiprime hidden variables and known variables.

Training loss and value loss are super high at the moment and I'm using an absurdly small training set (10k sequence pairs). I'm running on the assumption that there is a very strong correlation between the structures (and that it isn't just all ephemeral).

This initial run is just to see if training an machine learning model is a viable approach.

Won't know for a while. Training loss could get very low (thats a good thing, indicating actual learning), only for it to spike later on, and if it does, I won't know if the sample size is too small, or if I need to do more training, or if the problem is actually intractable.

If or when that happens I'll experiment with different configurations like batch sizes, and more epochs, as well as upping the training set incrementally.

Either case, once the initial model is trained, I need to test it on samples never seen before (products I want to factor) and see if it generates some or all of the digits needed for rapid factorization.

Even partial digits would be a success here.
And I expect to create multiple training sets for each semiprime product and its unknown internal variables versus deriable known variables. The intersections of the sets, and what digits they have in common might be the best shot available for factorizing very large numbers in this approach.

Regardless, once I see that the model works at the small scale, the next step will be to increase the scope of the training data, and begin building out the distributed training platform so I can cut down the training time on a larger model.

I also want to train on random products of very large primes, just for variety and see what happens with that. But everything appears to be working. Working way better than I expected.

The model is running and learning to factorize primes from the set of identities I've been exploring for the last three fucking years.

Feels like things are paying off finally.

Will post updates specifically to this rant as they come. Probably once a day.

!dev

I have a couple of thoughts about social justice controversies from these last years.

I think it's hard to have a good opinion about these events for several reasons.

One reason is that finding good information in 2019 is very hard.

Revenue based sites (thus unneutral) dominate the search results. You search about something and you find thousands of sites basically saying the same thing (because they copy each other).

That's why the existence of a free and open search engine is so important, so it's easier to find neutral hence good information on which to base your opinions, but they are prohibitively big for small groups to build.

Another reason is that controversies generate shock and shock curtails rational thinking. Maybe that's how the primitive brain works?

I'm not much of a scholar to feel confident to say that, but it's so recurrent that it's not too much of a wild guess.

When a controversy happens, a natural reaction is to pick a side. This means that:
a) we assume that there are only 2 sides, and
b) we must pick one of them

So, maybe the human is a bad politician by nature?

Also, because of the shock controversies generate, peaceful dialogue is very rare.

I have yet to see peaceful dialogue online about what patriarchy means to feminists and a lot of other terms they use.

I don't care much about feminists that vandalize or interrupt talks (yelling over someone else is abuse in my opinion).

But for the rest of them, I think discussing their ideas would be good.

I say this because most feminist discourse I see online is not open. Or maybe there are such instances but the web is so big that it's hard to find such instances.

I think some part of the modern feminist doctrine is bullshit, and some part is true.

I for one hate when some men I know in life expect their wives to be their cooks+cleaners (unless they want to do that, willingly). Personally, I'd encourage my wife to get a job (rightfully so, not just to meet some minority quota in some company).

I don't mind either calling a trans person the pronoun she wants.

But other ideas are awful, like the idea that meritocracy is patriarchy, so you need to force minorities to meet a proportionate quota. That's terrible reasoning.

Or the excessive self appreciation culture, like saying to yourself "you are pretty, you are beautiful, you are perfect". I think that grows arrogance and black-or-white thinking.

And some other ideas as well.

I guess the same you can say about any doctrine with different degrees. Some part is bullshit, some part isn't.

Some right wing people hate everyone who isn't white by default, but some want to have more immigration control.

I sure don't like the experiment of separating children from families like the current us govt did, but I wouldn't be happy either to know that by '99 50% of gangs members in the us were hispanic.

With this, I'm not going to say "embrace everyone's ideas" like an idiot. I hate when people do that. It's a stupid and weak reaction to radicalism.

In fact I think the way you fight radicalism and bad doctrines is that you listen to them and maintain good dialogue and counterargue in a respectful but insightful manner.

Making snide remarks, insulting or trolling won't change anyone's mind. That is just throwing fire to the fire.

In fact, when someone gets harassed because of something they believe in, usually it results in even more adherence to their beliefs, because of the usual assumption that success or goodness is full of strife.

So by telling a "sjw" or kkk member that they are idiots over twitter, you are in fact making them stronger believers in their doctrine.

Think of Daryl Davis, a black guy that made 200 members leave the kkk. How? He didn't tell them they were assholes, he somehow made friends with them.

I feel bad now because I've been trolling new devrant users a lot because of how they worsen the quality of the site, but maybe I should tell them that they are ruining the site somehow in a nice way and maybe they'll listen? I dunno...

The assumption is the mother of all fuck-ups.

"Did you really buy a macbook to put ubuntu on it?"
"Wow why would you use such an overpriced piece of garbage just to put linux on it?'
"You made the worst choice of hardware to put ubuntu on"

Maybe, just maybe, I didn't fucking buy it myself and I got it from work? Maybe I didn't fucking pay a dime to get a laptop to put ubuntu on it? Ever considered that I got it for fucking free and have the privilege to do what I want with it?

Go fuck yourself if your first assumption is that I would actually buy a macbook just to erase MacOS from it

dev, ~boring

This is either a shower thought or a sober weed thought, not really sure which, but I've given some serious consideration to "team composition" and "working condition" as a facet of employment, particularly in regard to how they translate into hiring decisions and team composition.

I've put together a number of teams over the years, and in almost every case I've had to abide by an assemblage of pre-defined contexts that dictated the terms of the team working arrangement:

1. a team structure dictated to me
2. a working temporality scheme dictated to me
3. a geographic region in which I was allowed to hire
4. a headcount, position tuple I was required to abide by

I've come to regard these structures as weaknesses. It's a bit like the project management triangle in which you choose 1-2 from a list of inadequate options. Sometimes this is grounded in business reality, but more often than not it's because the people surrounding the decisions thrive on risk mitigation frameworks that become trickle down failure as they impose themselves on all aspects of the business regardless of compatibility.

At the moment, I'm in another startup that I have significantly more control over and again have found my partners discussing the imposition of structure and framework around how, where, why, who and what work people do before contact with any action. My mind is screaming at me to pull the cord, as much as I hate the expression. This stems from a single thought:

"Hierarchy and structure should arise from an understanding of a problem domain"

As engineers we develop processes based on logic; it's our job, it's what we do. Logic operates on data derived from from experiments, so in the absence of the real we perform thought experiments that attempt to reveal some fundamental fact we can use to make a determination.

In this instance we can ask ourselves the question, "what works?" The question can have a number contexts: people, effort required, time, pay, need, skills, regulation, schedule. These things in isolation all have a relative importance ( a weight ), and they can relatively expose limits of mutual exclusivity (pay > budget, skills < need, schedule < (people * time/effort)). The pre-imposed frameworks in that light are just generic attempts to abstract away those concerns based on pre-existing knowledge. There's a chance they're fine, and just generally misunderstood or misapplied; there's also a chance they're insufficient in the face of change.

Fictional entities like the "A Team," comprise a group of humans whose skills are mutually compatible, and achieve synergy by random chance. Since real life doesn't work on movie/comic book logic, it's easy to dismiss the seed of possibility there, that an organic structure can naturally evolve to function beyond its basic parts due to a natural compatibility that wasn't necessarily statistically quantifiable (par-entropic).

I'm definitely not proposing that, nor do I subscribe to the 10x ninja founders are ideal theory. Moreso, this line of reasoning leads me to the thought that team composition can be grown organically based on an acceptance of a few observed truths about shipping products:

1. demand is constant
2. skills can either be bought or developed
3. the requirement for skills grows linearly
4. hierarchy limits the potential for flexibility
5. a team's technically proficiency over time should lead to a non-linear relationship relationship between headcount and growth

Given that, I can devise a heuristic, organic framework for growing a team:

- Don't impose reporting structure before it has value (you don't have to flatten a hierarchy that doesn't exist)
- crush silos before they arise
- Identify needed skills based on objectives
- base salary projections on need, not available capital
- Hire to fill skills gap, be open to training since you have to pay for it either way
- Timelines should always account for skills gap and training efforts
- Assume churn will happen based on team dynamics
- Where someone is doesn't matter so long as it's legal. Time zones are only a problem if you make them one.
- Understand that the needs of a team are relative to a given project, so cookie cutter team composition and project management won't work in software
- Accept that failure is always a risk
- operate with the assumption that teams that are skilled, empowered and motivated are more likely to succeed.
- Culture fit is a per team thing, if the team hates each other they won't work well no matter how much time and money you throw at it

Last thing isn't derived from the train of thought, just things I feel are true:

- Training and headcount is an investment that grows linearly over time, but can have exponential value. Retain people, not services.
- "you build it, you run it" will result in happier customers, faster pivoting. Don't adopt an application maintenance strategy

/rant

Me: I've not done this before, so any guess would be pure assumption.

Client: Okay, but still, you would have some idea, right?

Me: It might get done in 3 days or may take even 30.

After 3 days:

Client: But you said that it will be done in 3 days. Now you are saying there MVP is not ready. Do you even know, your part is the most critical one in the project. We believed in you. We trusted you. This is insane. It was a wrong decision to choose you.

Me (in my head): Didn't I say, this is the first time I am trying to scrape Coles? It might take time?

Me (in actual): I understand, it is getting delayed. Am trying to get this up ASAP....

Anyone else experienced toxic clients but still didn't lose their cool?

Didn't realize buttons will submit the first form on a page, coded without this assumption, went into production without anyone noticing. Cost the client about 8 grand in work that had to be redone.

- 5 days until customer integration test. I finished my work for the test a week ago so I am relaxed. 10 days of estimated work for other team, 1 dev scheduled for this task.
I reminded of the deadline, which seemed not realistic anymore; "Don't be so pessimistic" they said, "Everything is fine", "We'll get it done".

- 2 days to go and half of the system doesn't work, the external test system rejects all data (nobody had time to read the specs -> let's call it 'assumption based development' (ABD))
I reminded of the deadline, and that I would like to have an internal test with all components beforehand; "Don't be so pessimistic" they said, "Everything is fine", "Just some minor issues".

- 1 day to go and dev from other team called in sick... (and I can really empathize this decision); "Someone else can jump in and finish the work" they said.

- An hour later the test was cancelled not even 24 hours before it should take place. We could have rescheduled the test more than a week ago, that wouldn't have been so disgusting and even save our customer some hours of preparation effort.

I hate myself when I was right from the start but wouldn't enforce my position because I'm too kind sometimes.

One of our projects migrated their file-repository to another one during a major release.

Instead of giving this task to an experienced programmer, they gave it to the head of the respective dev department due to the usual release panic.

Soo.... He wrote the migration tool. It was executed during the release. Everything seemed fine so far.

A few days later. Someone from the above project came to my team due to some "strange behaviour on the production database".
They reported that they couldn't download some of the user's documents due to unknown reasons.

After quickly analyzing the current state of the new file-repository, we concluded that the affected documents did not exist in the new repository.

Then we took a look at the so called migration tool...
Well.. After nearly 30 min. we knew the root cause for that.
They only migrated the first 4 levels of the folder structure. Due to the assumption that "we don't use deeper nesting". (Facepalm)

As the head of their department wrote it, no one seems to questioned it either. Nor did they made a code review and ended up with a tool with hard coded urls to the production db, no version control, no build tool, no ci, nothing. Breaking nearly every possible company standard.

However.. That's not it. When analyzing their migration tool we noticed another even more dangerous thing.
They mixed up the id generation of the migrated documents resulting in a random assignment between customers and documents. Which is quite bad as this contains sensitive information. E.g. passports

They offered us quite a nice amount of money to fix this until EOB. We declinded as it was simply not possible in that time, but agreed to support them with the new tool.

After some time I heard that they migrated production again. And they fucked it up again. They never talked to us after we offered them support...

The third and final migration was written by us. Not only migrated it correctly. It was also way faster. By factor 20.

In the end we haven't gained anything from this rushed project as the penalties were piling up due to this fucked up migration.
After all this time I'm not sure who is to blame. In my opinion, partly all of them.
Head of department who can't and shouldn't code.
Seniors who didn't review the code and didn't ask for help.
Release mgmt who put way too much pressure on the devs.

!dev
My rough assumptions on wtf is going on with covid changing our lives - maybe leading to some business ideas.
In theory we are indoctrinated from little child that to do something we need to go to special place to do things in community.
Name it :
- school,
- university,
- job,
- college
As a result we build world around communities:
- public transportation
- sidewalks
- 4 seated cars
- parks
- sports
- shopping malls
Now due to pandemic we’re unable to do so and from some time we start indoctrinating people to do lots of things remotely and stay at home:
- remote job
...
- shopping
etc.
Depending on how strong is our character we react to this inception differently but future generations won’t have this indoctrination of commutation deep in their minds.

Interesting 🤔

My first assumption is that robotics market will start growing exponentially.

> Assumption is the mother of all fuckups

A microwave can cook potatoes in ten minutes!? Why the fuck did nobody tell me?

A lot of workplaces only offer a microwave and no oven, and barley a kitchen to prepare stuff.

Hence, I was rarely bringing in my own food as I worked under the assumption that I had to prepare it at home and just heat it up at work. And potatoes take round about ~40 minutes the way I make them (20 min to cook, 20 min to steep).

Now, I will be using the shit out of those technical wonders and save a lot of money in the progress, as I used to go to restaurants almost daily for lunch time. Heck, I may even buy myself one for home use.

Oh, now I remember why!
This is what I get by being brought up by a somewhat esoteric mother.

"Microwave are no good, the taint the food."

No, they do not. It's science!

I fucked up...

I inadvertently fixed a bug which changed the behavior in another application. Weeks later had a seemingly unrelated issue which my initial assumption was to blame a 3rd part tool (which was wrong). I gave said assumption to my manager not thinking anything of it and putting a simple change in place.

Higher ups start asking my manager about it, he provides details...the more I thought about it the more I realized the changes I made did not make sense.

I dug deeper into it and found it was due to the change I made weeks ago. So my manager offers to cover for me but i told him I'd take full responsibility.

I'm not getting fired or any type of reprimand at all...I just hate fucking up and then it looks like we are trying to lie about it being our fault.

VSCode's file watcher doesn't fucking work though, you self-important pricks. This attitude specifically is why I hate corporate software. "This is difficult, so you should use our solution." Why is the assumption that you fuck up less than the rest of the community?

Assumptions are a terrible idea, yet I find myself making them all the time about other people. I am finding the very sobering reality about people who use technology vs people who create technology. The users have zero intellectual interest in how the technology accomplishes a task. While the creators get absorbed into the details and often relish in being able to maximize capability.

A point of frustration for me is users who are in a semi technical field yet take zero time to learn how to configure a piece of tech. They get a plug and play attitude and seek in panic when things don't work. The work is semi technical because they need to understand some of the fundamental physics involved to assess things using instrumentation. Yet when asked about a system they actively modify as to how it is normally setup they are clueless. Me, who helps write the software to control these devices, is stumped that they have zero interest (or capacity?) to understand how the system is normally configured. This is not the first time I have made assumption about what they know in technical contexts. I have run into this before with managers, but not with technicians.

How do you manage your expectations with people who won't invest any time into how their equipment actually works? How does someone operate that way to begin with? Where is their curiosity about how things work?

On the flip side, I swear at my fucking phone because I don't care how it works, but I just want it to stop doing everything besides being a phone... Fuck you, we are not the same, I think...

! rant
I started to learn Matlab today. After I learnt that arrays starting with 1 in the Matlab, I started to think about why using 0 based arrays was made popular in the first place and I realized that C arrays actually just pointers and first element of the array is just a location pointed by array name. There is no need to add number to reach to the first element. After googling it, I saw that my assumption is true. Finding it all myself made me a little bit of proud 😀😀😀 Also, this expanded my horizon 🗻🗻🗻

I’ve been self-employed for the past three years. Though I did spend my first year out of college working for a three person, now-defunct startup, I’ve never had a typical 9-5 (or more like 10-8 nowadays) and to be honest, never really wanted one. Lara Schenck, LLC is a profitable business, and every day I do work that is enjoyable and challenging. I make my own hours, take vacations when I want to, and run everything on my terms.

While that’s all awesome, what you don’t get from working independently is the team experience. I base my work on teaching technical literacy to non-technical designers and content producers so that they can better communicate with developers. The theory is that if a designer understands why it’s a bad idea to request 18 fonts, and if content producers know why it’s not trivial to edit the titles of a set of related posts, life will be easier for everyone. At least that’s my theory, and the assumption on which I’ve developed my business.

Lately though, in a bout of the good ‘ol impostor syndrome, I’ve been feeling like, wait, how can I be telling people how to work on teams if I’ve never really worked on one? I’ve always been the ‘Lead UI/UX/Visual/Web/Front-end Designer-person-thing’, and have never worked for a larger company with separate teams for product, UX, marketing, content, frontend, backend, etc.

So I felt the urge to look for a job, and a seemingly perfect one fell into my lap. It was for an awesome company, and it sounded right up my alley skill-wise. The title was ‘UX Engineer/Interaction Designer’. I usually balk at the the term “engineer” (perhaps for good reason) but considering the presence of “designer” and the nature of the job post, I wasn’t too bothered.

Lessions I learned so far from my first big node/npm project with tons of users:
1) If you didn't build something for a while, expect 3 hours of resolving version conflicts for every two weeks since the last build.
2) Even if the tests pass, run the containers on your own machine and make sure that the app doesn't randomly crash before deploying
3) Even if the app seemed to work on your own machine, run the tests again in an environment mimicking prod at most 15 minutes before replacing the running containers.
4) Even if all else indicates that the app will work, only ever deploy if you expect to be available within the 4 hours following a deployment.
5) Don't use shrinkwrap for anything other than locking every version down completely. A partial shrinkwrap will produce bugs that are dependent on the exact hour you built the app _and_ the shrinkwrap file, and therefore no one will ever have seen them other than you.
6) Avoid gyp, and generally try not to interface too much with anything that doesn't run on node. If parts of your solution use very different toolchains, your problems will be approximately proportional to the amount of code. And you'd be surprised just how much code you're running. (otherwise it's more logarithmic because the more code the less likely a new assumption is unique)
7) Do not update webpack or its plugins or anything they might call unless you absolutely need to
8) Containers are cool but the alpine ones are pretty much useless if you have even just one gyp module.
9) There's always another cache. To save yourself a lot of pain, include the build time in every file or its name that the browser can download, and compare these to a fresh build while debugging to assert that the bug is still present in the code you're reading
+1) Although it may look like it, SQLite is far from a simple solution because the code and the bindings aren't maintained. In fact, it'll probably be more time consuming than using a proper database.

"Standup" meetings are based on the assumption that standing up gets uncomfortable after a while. In our team however, the meetings are not getting any briefer, we are just getting fitter. Perhaps we should introduce some more uncomfortable position, such as jump-up-and-down daily scrums, or yoga daily scrums.

(Part 1/2?)

Ohhh my god am I furious and this one's a gem.

Also I'm gonna namespoil all of the entities in my post. If this is against rant rules I'll reframe it.

So the story starts over an year ago. Me, being in a bad place, where I couldn't do a job due to external issues, wanted to try out an internship. Thought I could pull off a 5 hour shift and then attend to my problems.

THE INTERNSHALA ARC:

I apply to a bunch of applications on Angel, Internshala and Indeed.

I was contacted by a few handful of these places. One of them was called "ARCHITECTA SOFTWARE SOLUTIONS". These guys had arranged an online aptitude test for me which I promptly took.

I looked up this company and they seemed like a pretty okay big firm from the outset but didn't have many reviews on Glassdoor and likes of such. (first red flag). Post aptitude test, I was quite sure I fucked up and wouldn't get further contact. Surprisingly, a person from the company sends me his Whatsapp number over chat and asks me to save it. The message is worded like a bulk email (Starting with Hello everyone!!) which I thought was quite odd since the interaction from these platforms has always been a person-to-person contact for me. Since Internshala showed that only around 40 people applied for the position I was quite intrigued but attributed this to my lack of exp in internship operations.

THE WHATSAPP ARC:

I was contacted by the number on WhatsApp saying that they'd be interested in moving forward and I gave them my work experience details.

The person sends me over a development assignment to complete within a few days. The assignment consists of massive scope of details. I'm talking production level concept and implementation. Asks to me implement a custom emotion detection CV model (worded as "emotion camera" lmao), generate a 3d model (specified nowhere and expects to implement a mono-ocular system for the curious) and deploy it over AWS with a website to go along with it and also host that. The website should contain a VR ("360 rotatable") view that can explore the depth-map ("not worded as depth-map") of the face. My first assumption was that they had picked this work up for outsourcing and didn't bother to chip off parts so as to create an assignment out of it (I know very optimistic).

So I shoot it at him on WhatsApp asking which parts of the assignment should I do?

Him: So, which parts CAN you do?

I thought of it as an HR thing.

Me: I could do most of it but given the time-frame of the assignment and my applied position as a web developer it is perhaps out of scope for my application.

Him: Don't worry about the assignment. You can submit when you complete the whole assignment.

I was visibly angry over the stupidity of this man.

Me: This task is a Full-Stack + CV + VR task. It will take over two months to get working. Am I supposed to work on it for that long for an assignment?

Him: Okay just do the basic functionalities like add to cart. But also try to do the camera thing before next week.

At this point I'm sure that they are having trouble handling an eager client and they're offloading work to interns. So I do only the backend and minimal frontend and submit the assignment (a 2 day job done over a weekend).

Nothing. Empty. No messages since then. I tried sending in a Whatsapp message on the application and how to proceed. Then, if I could get to know if I have been rejected. Nothing.

And all this time I can clearly see the account is active as it pushes pretentious motivational quotes over it's Whatsapp status.

I always find it funny when people fight over certain aspects of Javascript. Like how callback hell is manageable, async functions etc

Do they forget that Javascript itself is a flaming pile of shit language to begin with? The inventor literally created the language in a week, so that should be the base line assumption on how "capable" that language will come out to be.

Assuming you're not a beginner , which language would you learn right now (or) which language would you prefer to stick with provided you already know it.

*The assumption made is to prevent comments on python cause that's usually beginners choice

Personally I want to hone my skills in rust.

A lot of this might be an assumption based on not enough research on both NestJS and TypeScript, so if something here is not well put or incorrect then please feel free to provide the necessary info to correct me since I care far more about getting dat booty than I do being right on the internet :D

Sooo, a year or so ago I got a hold on the Nest JS framework. A TypeScript based stack used to build microservices for node. Sounded good enough in terms of structure, it is based on the same format that Angular uses, so if you use Angular then the module system that the application has will make sense.

I attempted (last night) to play with the framework (which I normally don't since I am not that much of a big fan of frameworks and prefer a library based approach) and found a couple of things that weird me out about their selling points, mainly, how it deals with inversion of control.

My issue: This is dependency injection for people that don't really understand the concept of dependency injection. SOLID principles seem to be thrown out of the window completely due to how coupled with one another items are. Literally, you cannot change one dependency coming from one portion to the other(i.e a service into a controller) without changing all references to it, so if you were using a service specification for a particular database, and change the database, you would have to manually edit that very same service, or define another one....AND change the hardwire of the code from the providers section all the way into the controllers that use it....this was a short example, but you get the gist. This is more of a service locator type of deal than well....actual dependency injection. Oh, and the documentation uses classes rather than interfaces WHICH is where I started noticing that the whole intention of dependency injection was weird. Then I came to realize that TypeScript interfaces are meeheed out during transpilation.

Digging into the documentation I found about custom providers that could somehowemaybekinda work through. But in the end it requires far too much and items that well, they just don't feel as natural as if I was writing this in C# or Java, or PHP (actually where I use it the most)

I still think it is a framework worth learning, but I believe that this might be a bias of mine of deriving from the norm to which I was and have been used to doing the most.

So I figure since I straight up don't care about the Ada community anymore, and my programming focus is languages and language tooling, I'd rant a bit about some stupid things the language did. Necessary disclaimer though, I still really like the language, I just take issue with defense of things that are straight up bad. Just admit at the time it was good, but in hindsight it wasn't. That's okay.

For the many of you unfamiliar, Ada is a high security / mission critical focused language designed in the 80's. So you'd expect it to be pretty damn resilient.

Inheritance is implemented through "tagged records" rather than contained in classes, but dispatching basically works as you'd expect. Only problem is, there's no sealing of these types. So you, always, have to design everything with the assumption that someone can inherit from your type and manipulate it. There's also limited accessibility modifiers and it's not granular, so if you inherit from the type you have access to _everything_ as if they were all protected/friend.

Switch/case statements are only checked that all valid values are handled. Read that carefully. All _valid_ values are handled. You don't need a "default" (what Ada calls "when others" ). Unchecked conversions, view overlays, deserialization, and more can introduce invalid values. The default case is meant to handle this, but Ada just goes "nah you're good bro, you handled everything you said would be passed to me".

Like I alluded to earlier, there's limited accessibility modifiers. It uses sections, which is fine, but not my preference. But it also only has three options and it's bizarre. One is publicly in the specification, just like "public" normally. One is in the "private" part of the specification, but this is actually just "protected/friend". And one is in the implementation, which is the actual" private". Now Ada doesn't use classes, so the accessibility blocks are in the package (namespace). So guess what? Everything in your type has exactly the same visibility! Better hope people don't modify things you wanted to keep hidden.

That brings me to another bad decision. There is no "read-only" protection. Granted this is only a compiler check and can be bypassed, but it still helps prevent a lot of errors. There is const and it works well, better than in most languages I feel. But if you want a field within a record to not be changeable? Yeah too bad.

And if you think properties could fix this? Yeah no. Transparent functions that do validation on superficial fields? Nah.

The community loves to praise the language for being highly resilient and "for serious engineers", but oh my god. These are awful decisions.

Now again there's a lot of reasons why I still like the language, but holy shit does it scare me when I see things like an auto maker switching over to it.

The leading Ada compiler is literally the buggiest compiler I've ever used in my life. The leading Ada IDE is literally the buggiest IDE I've ever used in my life. And they are written in Ada.

Side note: good resilient systems are a byproduct of knowledge, diligence, and discipline, not the tool you used.

A new development rule I've started to implement:

All backend APIs will be written with the assumption that it's gonna get distributed as an API for 3rd parties to be integrated in their systems - meaning that every API I write will have proper response status codes for appropriate scenarios (like 400, 429, 500 status codes).

No more `res.json({status: false, message: 'message'})` with 200 status code across the board.

Status: Got off hour+ long call with provider teir2 tech support because their "sync service" isn't syncing. "It's all cloud controlled" they tell me. Whatever.

It does have the ability to install a Windows service to do the needful! 🎉

However the program that does the actual syncing is the "launcher" application, and the service's only job is to tell the launcher to run. 🤦‍♂️

Their assumption is that there will be a user that gets smacked in the face with a UAC prompt when they first log in and just shrug it away. Which is the Launcher application.

The sync service is not capable of running the sync application without a desktop session I guess?

MOTHERTRUCKERS do you understand what the point of a Windows Service is?!?

I tried relating this situation to how Windows Update works: It will update whenever the fuck it wants without the user doing anything because of the Service, and you only configure the service with the Control Panel/Settings App. You don't need the Control Panel/Settings App running in order for Windows Update to work, but it's there for status info and configuration.

Anyways, this software does not do that. It apparently *requires* both the service AND the launcher program running in order to work. Not work properly, to work *at all*.

Anyways, It's installed on a computer that's not normally logged into, but is always on (where other "always needs to be running" programs live). Normally the hackaround would be to launch the program via Scheduled Task.

This program apparently does not want to run as a scheduled task, or the Task Scheduler is being stupid and can't figure out "Hey, it's time to run this program. Do it!". Naturally it runs if told manually.

The fact that I'm even doing this at all is stupid, but even more infuriating is that it's just not working unattended. You know, what the service should be doing. But no, the service runs happily all alone, doing nothing of note, while Task Scheduler sucks its stick running OneDrive installer but not the launcher program.

Pluckin' donuts...

I feel really uncomfortable about this question. The assumption seems way out of proportion😢 20% women killed by their husbands, and I'm answering this question while don't even have a girlfriend

FML, I based my parts of my small framework on a wrong assumption and now I have to rethink about 30% of it

ProTip/Common knowledge

When looking for an exhaustive answer to a problem you’re facing regarding a specific technology, instead of asking the community for help, post a rant/false assumption connected to said technology and your specific problem.

Et voilà, never before have answers been provided with such swiftness and clarity.

So I bought a new phone, I was super excited getting it, I even got to open it at work with my colleagues watching. It was really nice, the S8 is an attractive phone... Until it started crashing very very regularly. I want to go back to my old phone, that's how bad it is. Turns out this is a common experience, how can this be at the top of all the review lists if it has this problem? Is the assumption that you are going to install stock android as soon as you get it? Or is someone paying for reviews?

Question: is it common for lead software engineers to mostly do paperwork or is that just a quick of my current program?

Where I work it is very common for those titled "software leads" to be almost completely hands off the software. They deal in hiring, fielding user comments and commitments, and scheduling. I would like to be a lead but I was always under the assumption that dev leads had more of a design and/or architect role. Sort of a big picture thing rather than middle management which is what this feels like.

Do you plan the application, on which you will be working, before you actually begin to write code?

I do web development and usually begin with something rough or look at designs of other developers. Like an dashboard example, when I see an image on google search that I like, I try to make something simmilar and when I have the surface I can add the functionality and improve the design.

Sometimes I have to make changes in half of the development because at the beginning there was no assumption that there will be a need for a certain functionality or I change a implemented feature to work properly, so I have to refactor something I made as a ground on which other parts will rely, although if I had planed the application in detail, maybe it wouldn't come to such refactoring.

In school we did prototypes, used to draw flowcharts and hold on a precedence diagrams that we made, but now at work when I receive an projekt I just begin to code :-D maybe this should change, how do you do it? If you plan your project, how do you do it?

<assumption>If there are no fundamental laws constraining the existence of simulated consciousness</assumption>, I would throw in my lot in working towards developing an AGI.

Since there is infinite time to learn any skill and <assumption>it is possible to learn or invent whatever software or mathematical framework is required for such a goal</assumption>, I would get down to that, learning and creating various new forms of mathematical frameworks and required software tools.

<assumption>Engineers usually work best without another fellow human on the project</assumption>, so I will set up automation for tasks that do benefit from multiple minds on a project, in the form of low-level artificial intelligence that I have to work on as a prerequisite for the main goal.

Once the critical mass is hit where the code can keep self-improving and produce more iterations of itself that are better, I sit back and start with my long, long to-watch/to-read list and try to finish as much as I can before the AGI I created would <assumption>repurpose all of our mortal flesh for more efficient use.</assumption>

The only remnant of the existence of humanity will be the influence on the initial design of the code based sentience that exists now.
.
.
.
.
.
.
.
Just kidding, <not-an-assumption>I'd probably procrastinate right until the heat death of the universe</not-an-assumption>

I don't care about CORS, I really don't. Could it possibly be any more inconvenient and time consuming? I really don't think it could.

It's made on the assumption that everything you are doing has the same security needs as a secret military project, splendid.

Someone managed to install a virus on my class' computer. It's called amazon assistant or something like that and it keeps in opening a blank window called aa.hta as soon as you close it it opens again. It didn't change any file so idk, the only assumption i can make is that it mines cryptocurrency. But whatever is fun watching my teachers trying to close it.

To add a bit more context to my last rant.

The following situation happened today and similar situations are at the moment common as fuck.

Situation started roughly 1 1/2 months ago as a deployment failed.

Seemed to be a DNS problem for the devs, so my basic assumption was that they checked their shit.

As I was and I am currently more than swamped, told them it had to wait if it is an DNS issue...

Well.

Backstabbing product manager complained to upper management as it took so long.

Backstabbing manager even went so far to propose alternative solutions - think of switching product to work around issue and throwing away a year of development of a 5 man team...

So additional to my work I had to deescalate and prevent complete nonsense.

Today I finally found time for the problem.

After 2-3 hours of turning every stone inside the DNS setup, cloudflare, loadbalancers, etc...

Well. Devs. Don't trust them.

Turned out the devs misconfigured the environment entirely.

Its not so obvious in this product as it is rather complicated, though the devs documentation explicitly mentioned that if one overrides the configuration for e.g. several languages, one has to make sure to set two env variables for TLS mode...

There was only one set.

:(

8 fucking weeks of backstabbing and blaming others while they could have just read their own fucking documentation and fixed that shit in 5 minutes.

My project is a cloud based automated testing product. My current story is to extend a module to support multiple of a particular testcase type in one test run instead of just one. This has uncovered a rats nest of complexity because everything is designed with the assumption that there will only ever be one of these testcases.
Refactoring about 5 different classes just to get into a state where i can pass a list of testcases into a service instead of just one. Wrecking my head...

The term "technical debt" is poorly used. I hear folks of all stripes and roles proudly proclaim that they've "reduced technical debt" in some way. It's used as a catch all to describe some kind of supposedly beneficial change. I think it's just more software process word salad. Mostly because there seems to be some assumption that "Yay, that stuff that was changed is no longer a problem" when odds are that it will be changed again before too long for more "technical debt reduction". Software changes over time because the requirements change over time. I don't see the need for the phrase at all, and I think using it gives some false sense of accomplishment when really the constant change of code is the normal state.

Yay, nothing better than good ol' change request... Right?

Let's see...
Limit user's ability to do sth, if this condition is met, allow editing global parameter of this condtion, than add per action overrides, on top of that add per-user override, on top of that add per-user overrides to ignore certain overrides.

Shiit man, reading this took me 3-4 times and still Im not sure if I 100% understand

Okay, I think I got this.
setting
per-user ignore flag to setting
override to setting
per-user ignore flag to override to setting
override to override to setting
per-user ignore flag to override to override to setting

design assumption: automatic system that can make life easier
me: designed system to be fully automatic
every single change request: be less automatic, require more user manual and more attention to work

I went to an interview a few days ago, just out of curiousity, even though i was sure that i won't be getting any "android developer jobs" there . it was a mega job fair. in one company, me and my friend neil(fake name) went. the interviewer guy was willing to give neil a package upto 10LPA (its a great offer for freshers in my country) based on his current skills of php js, react,angular, ... web stuff .
I had this assumption( and neil did too , we both kind off had the same mindset) that a company teaches us things, we just have to be a little famous/accomplished. So i thought why not? i am accomplished. i got 2 apps on playstore, i am an AAD certified Android dev and know a lot of android stuff, i am quite famous. i am equally as deserving as neil.

But what happenned was something different. When my turn came, the interviewer said " If you have no knowledge of phy/js/node/angular, why are you sitting here?" to which i said " i presumed company would teach me, since i bring some level of expertise from other fields"

so he told me some hard truths **"Companies are fast paced. they don't have time to train you in everything. we seek for candidates having some level of knowledge in the domain, so that we could brush up your skills, increase your knowledge to current requirement and push you to production engineer asap, so that you could be worthy of your salary"**

This is completely correct. i have stuck myself in such a career that its very difficult to sell myself for other job profiles. And from what i have seen, companies seek a very high level of proficiency in this field and rarely recruit freshers( or even if they do, salaries will be aweful)

. Now i am so unsure about what to do next:

A.) keep learning more and more of android and look for job in it. And even if am getting an aweful job offer, just sulk and take it
B.) do open source work/gsoc work?( its a good way to earn more recognition/stipend/knowledge and sometimes even job offers)
C.) learn web dev, data sciences, blockchain, cloud or other stuff that i don't yet know
D.) go back to ds algo / competitive? (because having good competitive knowledge is a safe zone. you are assumed as apure fresher with 0 level of practical knowledge but good level of mathemetics)

I know i am going suck in all of the above except maybe (A) or (B) because (C) is something that am unsure would grab my interest (and even if it did, i am sure i need another 1-2 years to be somewhat good at it) and (D) is something i myself know am uncapable of , i am an average shit in maths(but might mug it all up if i pull all nighters for 1 year)

My experience was very recent. I was working on my game engine, Pillar3D, and realized that the setup allowed it to be automatically multithreaded with little to no concern about deadlock or race conditions. All based on the assumption that individual levels don't talk to each other, and that moving entities between levels could be done between frames. I can even track about how much work each thread has to do and use that to distribute levels among the threads. Now I can do things like force UI trees to exist in their own level and get fantastic multithreading.

Worst dev sin? Perpetuating the assumption that we'll build your site for free.
In my defense, my portfolio was lacking.

As a dev I never gave the possibility of someone using my notebook, PC or phone to snap a photo of me much thought because I just assumed that whoever made the camera module was smart enough to make it so that whenever the CCD/CMOS sensor receives power an LED wired to the same rail lights up - letting you know the camera is on... BUT! That is an assumption I made, has anyone looked how are webcams wired up? Can anyone confirm my assumption?

In Postgres, parallel query works by having multiple workers....

As such, depending on workers available, queries can run theoretically fast (workers available) or slow (workers not available) - right?

Question is: are there more optimizations like this... And is my assumption correct?

It seems like a major pain in the ass... Scalability and reliability wise. (?!)

One of the worst practices in programming is misusing exceptions to send messages.

This from the node manual for example:

> fsPromises.access(path[, mode])

> fsPromises.access('/etc/passwd', fs.constants.R_OK | fs.constants.W_OK)
> .then(() => console.log('can access'))
> .catch(() => console.error('cannot access'));

I keep seeing people doing this and it's exceptionally bad API design, excusing the pun.

This spec makes assumptions that not being able to access something is an error condition.

This is a mistaken assumption. It should return either true or false unless a genuine IO exception occurred.

It's using an exception to return a result. This is commonly seen with booleans and things that may or may not exist (using an exception instead of null or undefined).

If it returned a boolean then it would be up to me whether or not to throw an exception. They could also add a wrapper such as requireAccess for consistent error exceptions.

If I want to check that a file isn't accessible, for example for security then I need to wrap what would be a simple if statement with try catch all over the place. If I turn on my debugger and try to track any throw exception then they are false positives everywhere.

If I want to check ten files and only fail if none of them are accessible then again this function isn't suited.

I see this everywhere although it coming from a major library is a bit sad.

This may be because the underlying libraries are C which is a bit funky with error handling, there's at least a reason to sometimes squash errors and results together (IE, optimisation). I suspect the exception is being used because under the hood error codes are also used and it's trying to use throwing an exception to give the different codes but doesn't exist and bad permissions might not be an error condition or one requiring an exception.

Yet this is still the bane of my existence. Bad error handling everywhere including the other way around (things that should always be errors being warnings), in legacy code it's horrendous.

learning golang. so they have optional feature called `vendor`. so basically they reinvent the `node_modules`.

the weird thing is that it supposed to work by committing dependencies to git. but unlike node_modules, vendor directory wouldn't be massive since they come with assumption that the community wouldn't fuck up the libraries ecosystem.

huh?

Assumption. Screens are wider and wider, bigger and bigger.
Solution 1: Make more one-page layout sites like there is no space on sides.
Solution 2 support solution 1: Make everything 2-3 times bigger so there can't be space on sides.
Solution 3 support solution 2: If there is some free space, call it neccessary white space.

It's a trend i see around me. Sometimes i don't get it. More than 1 year i have no side menu in designes what i coded.

is it a wrong assumption that start ups don't provide enough design problems to back end developers?

Another day and I’m wondering if that female is 35 and I’m 56 but I’m having difficulty with that assumption because I guessed that before

The chick who bent over and posed retains her nice legs however

Wtf to do ? Can’t remember all the things I tried till I’m close and I don’t want to give up this phone because it’s useful Jesus

Seriously what group of idiots traded real life in this country for this shit ?

Instead of balancing the grand economic equation by creating semi pampered slaves we could have just improved and cleaned up things and had a shared labor pool for the jobs that everyone hated that we didn’t have enough felons to fill

Course so far as I can tell the country is brimming over with felons doing all the crap jobs and not suffering to the level those jobs should cause them too if that’s the system we’re supposedly embracing

When you have a service that makes you a £1000 a month that you become completely obsessed with in the assumption you will be making £10,000 a month in 40 years time if you keep going you invest your life into it and ridiculous amounts of time because it's yours and your not making someone else rich and building their dream just someone's bitch. Even tho you can make £400 a day contracting.