Got annoyed by hitting f11 instead of f12.
("step into" versus "go to definition").
Solved the problem :)

My biggest pet peeve at the moment is people without any development experience using version numbers.

Me: "Communicating a release date for the feature towards clients is dangerous, we have a developer shortage, and currently don't really have enough capacity to..."

Manager: "What we release next month doesn't have to be perfect, it is just a v1"

Me: "You mean it's a beta? If that's the case, could you maybe differentiate the requirements of the beta, let's call it a 0.1.0, versus the 1.0.0-rc, the release candidate?"

*Feature is eventually merged into production, barely in a beta state*

Manager: "So I have some ideas for the v2"

Me: "You mean 1.0.0"

Manager: "Let's compromise and call it v1.5"

Me: "Let's compromise, you stop communicating release dates, AND you stop using version numbers..."

Manager: "That's not a compromise..."

Me: "...I wasn't finished... And I won't respond to the recruiter who just offered me a better paying job"

0 versus Null

It fucking staggers me how many backend/devops-y people don't understand what a client side "request timeout" is, versus a server side one.

What does it mean:

The client was fed up with the servers bullshit, and decided to piss off and not wait around for the server to take forever to respond, because life's too short.

How not to solve/debug this issue:

- "I've checked the API request in tool xyz, and it works fine for me"

Congratulations, you've figured out how to call an API once, in isolation to the rest of the application, and without any excessive load. And using a different client to me, with a different configuration. Lets get back to actually looking at the issue shall we?

- "I only see HTTP 200's in the logs"

Yep, you probably will in most circumstances, because its the client complaining about it taking too long, not the server. If the server was telepathetic and knew what the client was thinking/doing at all times, we wouldn't have half of the errors we do.

- "Ah ok, I understand ... so how do I solve this?"

Your asking me? I don't fucking know, I didn't build the server! Put better logging in place and figure out why sometimes it takes forever.

Jesus fucking christ

Managers here talking about 'Apple versus Android'. I'm tempted to ask them about 'Samsung versus iOS' 😁🤣

PM: Can we have it so the usernames are case-sensitive?

Me: uhh, sure I guess.. But thats like really pointless and adds no real usefulness.. In fact makes the whole logging in thing a tad more complicated for no reason..

PM: Well this one other product we have uses "Admin" for the login versus yours that used "admin" so it needs to be implemented.

(note that mine accepted "Admin" anyways...) *implemented it*

PM: So there's a problem with the username sort, it sorts by capitals then lowercase.. eg:
alpha
beta
Alpha

Me: Yeah, you asked for case-sensitive usernames..

PM: Well can you fix it?

Me: I could create a second field within the user data that is the username in all lowercase and sort by that. But that negates like all of the whole case-sensitive usernames thing.. OR I could drop all this actually important work I'm doing and do a whole bunch of work on a custom sort for this useless fucking feature you wanted me to put in..

*it's been 2 weeks and still no reply...*

I've been away, lurking at the shadows (aka too lazy to actually log in) but a post from a new member intrigued me; this is dedicated to @devAstated . It is erratic, and VERY boring.
When I resigned from the Navy, I got a flood of questions from EVERY direction, from the lower rank personnel and the higher ups (for some reason, the higher-ups were very interested on what the resignation procedure was...). A very common question was, of course, why I resigned. This requires a bit of explaining (I'll be quick, I promise):
In my country, being in the Navy (or any public sector) means you have a VERY stable job position; you can't be fired unless you do a colossal fuck-up. Reduced to non-existent productivity? No problem. This was one of the reasons for my resignation, actually.
However, this is also used as a deterrent to keep you in, this fear of lack of stability and certainty. And this is the reason why so many asked me why I left, and what was I going to do, how was I going to be sure about my job security.
I have a simple system. It can be abused, but if you are careful, it may do you and your sanity good.
It all begins with your worth, as an employee (I assume you want to go this way, for now). Your worth is determined by the supply of your produced work, versus the demand for it. I work as a network and security engineer. While network engineers are somewhat more common, security engineers are kind of a rarity, and the "network AND security engineer" thing combined those two paths. This makes the supply of my work (network and security work from the same employee) quite limited, but the demand, to my surprise, is actually high.
Of course, this is not something easy to achieve, to be in the superior bargaining position - usually it requires great effort and many, many sleepless nights. Anyway....
Finding a field that has more demand than there is supply is just one part of the equation. You must also keep up with everything (especially with the tech industry, that changes with every second). The same rules apply when deciding on how to develop your skills: develop skills that are in short supply, but high demand. Usually, such skills tend to be very difficult to learn and master, hence the short supply.
You probably got asleep by now.... WAKE UP THIS IS IMPORTANT!
Now, to job security: if you produce, say, 1000$ of work, then know this:
YOU WILL BE PAID LESS THAN THAT. That is how the company makes profit. However, to maximize YOUR profit, and to have a measure of job security, you have to make sure that the value of your produced work is high. This is done by:
- Producing more work by working harder (hard method)
- Producing more work by working smarter (smart method)
- Making your work more valuable by acquiring high demand - low supply skills (economics method)
The hard method is the simplest, but also the most precarious - I'd advise the other two. Now, if you manage to produce, say, 3000$ worth of work, you can demand for 2000$ (numbers are random).
And here is the thing: any serious company wants employees that produce much more than they cost. The company will strive to pay them with as low a salary as it can get away with - after all, a company seeks to maximize its profit. However, if you have high demand - low supply skills, which means that you are more expensive to be replaced than you are to be paid, then guess what? You have unlocked god mode: the company needs you more than you need the company. Don't get me wrong: this is not an excuse to be unprofessional or unreasonable. However, you can look your boss in the eye. Believe me, most people out there can't.
Even if your company fails, an employee with valuable skills that brings profit tends to be snatched very quickly. If a company fires profitable employees, unless it hires more profitable employees to replace them, it has entered the spiral of death and will go bankrupt with mathematical certainty. Also, said fired employees tend to be absorbed quickly; after all, they bring profit, and companies are all about making the most profit.
It was a long post, and somewhat incoherent - the coffee buzz is almost gone, and the coffee crash is almost upon me. I'd like to hear the insight of the veterans; I estimate that it will be beneficial for the people that start out in this industry.

Always cat versus dig but I always love dogsm

Rant about a german problem in english

I think we as the people should just sue the german government for neglect of progress and neglect of the education system. If your not familiar with the state of german IT we have worse internetspeeds than uganda or the notoriously shitty australia, our neighbourstates look at us in disbelief while laughing in optic fibre. Our school system seperates all students after 4th grade in 3 tiers, the lowest one gives you the future perspective as a social security case. The second and highest tier require masses of useless knowledge, so called "competences"(Kompetenzen) which are totally useless skills with no real world application because they are derived from real skills, a median ground between all possible applications of that skill. And while doing that they terribly insist on doing everything the "proper" way, meaning handwritten. Most people you would expect to have basic computer literacy, meaning age 40 and below, are incapable of using basic functions of a non-smartphone computer and do not understand the slightest of what they are actually doing or supposed to do. And I mean nothing technical. Germans are the reasons they still put word as a job requirement for devjobs because this disqualifies half of our population. This leads to many people having the archaeic "we versus the machines" mentality, thinking that if they ever let the computer do parts of the job, they will then lose all of it to the machines. Thats why you never strive past basic mathematical principles in mathematics, which is a big misnomer because you never do actual mathematics, only calculating and basic calculus and statics. If you get to use your calculator, its some basic casio with no actual functionality then standard operations. And even using that is shunned upon. How is this country ever supposed to become something more than it was in the 90's, if we teach people nothing of use and kill all progress in its root.

Been a while but I'm back with fresh rants.

If you look in my history you will see support wanted us devs to start paying for writing bugs. Now the release presentation has passed but we're still in crunch time because we can't put clients onto the new version yet. And in the meantime our coffee machine broke. So support has started to manually pour coffee, which was actual real nice of them.

Now yesterday I'm in a hurry and the coffee is out so I decide to pour a quick cup for myself with the leftover grounds. When I'm back at my desk I get a call asking if I just made coffee. I'm like yeah something wrong? Proceed to get chewed out for being selfish and that they see how it is with me, then get hung up on before I can even explain.

So yeah not only is my company too cheap to get a new machine, the lack of one causes drama.

Today however our network guy, who was present when my colleagues asked what was with the weird phone call, brought in his own machine and let me have coffee from it. Meanwhile suport can keep their crappy manual pouring. And I don't need to go into their office anymore.

!rant I'm beginning my nerd project of getting my IBM 5150 to the internet via my raspberry pi and a terminal emulator. Oh and the IBM has a 4gb (yes gigabytes) HDD in the form of a compact flash.

The pi is a model B. Even as an older pi, look at the difference in size versus performance!

The 5150 is 4.77 mhz

The Pi is 900mhz

Linux is hard to learn and master. That's fine with me. Windows is intuitive, but not user-friendly. Linux has a steep learning curve, but then is far more user-friendly than any other operating system. To me, that steep learning curve was far more than worth it, as I now have a desktop that does whatever I want, and behaves exactly as I want.

People come to Linux hoping that it will be easy to pick up, and then get angry when it isn't. Then they claim that the community is toxic, because Linux users are happy with something they think is broken.

Linux is hard to learn, and that's fine. That's valuable, to me. That's part of the appeal to me(and millions of others). Linux is unforgiving when you lack the knowledge gained in that steep learning curve. That's fine with me too. As its userbase grows, so too does the number of knowledgeable people who work to make it better and invent more amazing things for it.

If Linux was easy to learn, it wouldn't be as good as it is, and to me, that's reason enough to love it.

Depression and anxiety is a major challenge in my work life.
I could remember vividly when I was at my last job, any time I felt depressed I'll call for sick leave. It was hard for me to pinpoint the cause of my depression because even while on most sick leave I still felt depressed.
I blamed it on my job, blamed it on my family, on my social circle, on my friends, on my lifestyle, on almost everything. At some point it all felt like it was me versus the world, a fight I could never win.
Thoughts came in... Maybe it's because John is now married with two kids, or because Stella is now the new manager, or that David just bought a new Ross Royce and I'm still riding an ice-cream truck, or its because Steve is always on vacation and PM always complaining about uncompleted task with no acknowledgement for the 2 months task finished in a week, or because Boss is always calling for stupid meetings. Different thoughts in my head... Jealousy, Envy, Disappointment, Tiredness, Confusion, all combined at once.

But I did found a cure for my anxiety and depressed nature...
During lunch hours I visit a beach close to where I work, it's called "Tarkwa bay". I'll sit at the rock formations and glare at the shadows of the rising sun, listen to the sound of rumbling waters and passive the complete overview of nature. The feeling I get there is really calming, It occupies my head with neutral thoughts and a love for nature. 🤗
I truly experienced an improvement overall and it's been a while I felt depressed since I started such a routine.
Nature is really a gift.

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.

Fried potatoes with mushrooms.

In Russian, if potatoes was fried with the mushrooms, the word "fried" (жаренная) contains two letters "n".

If potatoes was fried on their own and only then you added mushrooms, the word "fried" (жареная) contains one letter "n".

You can replace frying, mushrooms and potatoes with different things, but as soon as the concept of "processing ingredients together versus independently" persists, the rule applies.

Look, I get that it's really tricky to assess whether someone is or isn't skilled going solely by their profile.

That's alright.

What isn't center of the cosmic rectum alright with the fucking buttsauce infested state of interviews is that you give me the most far fetched and convoluted nonsense to solve and then put me on a fucking timer.

And since there isn't a human being on the other side, I can't even ask for clarification nor walk them through my reasoning. No, eat shit you cunt juice swallowing mother fucker, anal annhilation on your whole family with a black cock stretching from Zimbabwe to Singapore, we don't care about this "reasoning" you speak of. Fuck that shit! We just hang out here, handing out tricks in the back alley and smoking opium with vietnamese prostitutes, up your fucking ass with reason.

Let me tell you something mister, I'm gonna shove a LITERAL TON of putrid gorilla SHIT down your whore mouth then cum all over your face and tits, let's see how you like THAT.

Cherry on top: by the time I began figuring out where my initial approach was wrong, it was too late. Get that? L'esprit d'escalier, bitch. I began to understand the problem AFTER the timer was up. I could solve it now, except it wouldn't do me any fucking good.

The problem? Locate the topmost 2x2 block inside a matrix whose values fall within a particular range. It's easy! But if you don't explain it properly, I have to sit down re-reading the description and think about what the actual fuck is this cancerous liquid queef that just got forcefully injected into my eyes.

But since I can't spend too much time trying to comperfukenhend this two dollar handjob of a task, which I'd rather swap for teabagging a hairy ass herpes testicle sack, there's rushing in to try and make sense of this shit as I type.

So I'm about 10 minutes down or so already, 35 to go. I finally decipher that I should get the XY coords of each element within the specified range, then we'll walk an array of those coordinates and check for adjacency. Easy! Done, and done.

Another 10 minutes down, all checks in place. TEST. Wait, wat? Where's the output? WHERE. THE FUCK. IS. THE OUTPUT?! BITCH GIMME AN ANSWER. I COUT'D THE RETURN AND CAN SEE THE TERMINAL BUT ITS NOT SHOWING ME ANYTHINGGG?! UUUGHHH FUCKKFKFKFKFKFKFKFUFUFUFFKFK (...)

Alright, we have about 20 minutes left to finish this motorsaw colonoscopy, and I can't see what my code is outputting so I'm walking through the code myself trying to figure out if this will work. Oh, look at that I have to MANUALLY click this fucking misaligned text that says "clear" in order for any new output to register. Lovely, 10/10 web design, I will violate your armpits with an octopus soaked in rabid bear piss.

Mmmh, looks like I got this wrong. Figures. I'm building the array of coordinates sequentially, as a one dimentional list, which is very inconvenient for finding adjacent elements. No problem, let's try and fix that aaaaaand... SHIT IM ALMOST OUT OF TIME.

QUICK LYEB, QUICK!! REMEMBER WHAT FISCELLA TAUGHT YOU, IN BETWEEN MOLESTING YOUR SOUL WITH 16-BIT I/O CONSOLE PROBLEMS, LIKE THAT BITCH SNOWFALL THING YOU HAD TO SOLVE FOR A FRIEND USING TURBO C ON A FUCKING TOASTER IN COMPUTER LAB! RUN MOTHERFUCKER RUN!!!

I'm SWEATING. HEAVILY. I'm STEAMING, NON-EROTICALLY. Less than 10 minutes left. I'm trying to correct the code I have, but I start making MORE dumbfuck mistakes because I'm in a hurry!

5 minutes left. As I hit this point of no return, I realize exactly where my initial reasoning went wrong, and how I could fix it, but I can't because I don't have enough time. Sadface.

So I hastily put together skeleton of the correct implementation, and as the clock is nearly up, I write a comment explaining the bits I can't get to write. Page up, top of file, type "the editor was shit LMAO" and comment it out. SUBMIT.

This violent tale of brain damaged badmouth schizoid baby versus badly worded code challenges was brought to you by ButtholeSuffers. Tired of taking low-quality viagra before engaging in unprotected anal sex? Then try ButtholeSuffers, the new way to strengthen your everday erections! You'll be as fucking HARD as a WALL!

Visit triple doble minus you dot triple doble YOU dot doble-u doble www dotbit lyshAdy wwwwww academy smashlikeachamp ai/professional/$$%$X$/0FD0EFF~ \*¨-`++ ifyouclickurstupid for for a FREE coupon to get MINUS NaN OFF on a close-encounter with an inter-continental dick, and use my promo code HOPONBITCH if you'd like it *RAMMED* --FAR-- and D E E P L Y.

(lel ad break should continue I'm cutting it shortt) [CENSORED] grants *physical* access to your pants! Big ups to Annihilate for sponsoring this mental breakdown.

Also hi ;>

About starting your career at a medium-bigger company that's well-established, versus starting at a smaller company.

That's my point of view:

It's always wiser to begin at a company that's more established (you will also be sure that you will get paid on time). I started at a well-established company, and I managed to buy gear, travel, do stuff, and then I realised that I wanna do more, not only live to work 😎.

Smaller companies are kinda risky, think of it, their goal is to reach the level of a well-established company, which is some levels lower than that. On the other hand, if you do well at a smaller company, your next goal will be to work for a bigger company, which will surely be nicer, more professional and will pay better. So you will have managed to et there with all the skills in your pocket already, which will come in handy later!

Bigger companies are excellent if you have a family (wife and kids), they provide stability, that's the most important thing, but I believe that in order to get "settled" in a company like that, you should at least have tried something else first, like doing your own thing or get challenged in more complicated gigs that require you to up your skills.

In the end, it's all sun and fun, with you code editor by your side 😉. I'm interested to see your opinions.

Just spent an entire night eaning up my codebase...

I optimized some of the functions got rid of unnecessary global variables and changed up the whole file hirearchy so it would be easier to read. After spending all night doing this I went to run the program and for once it seemed everything worked right the first time! However a portion of my application that is supposed to happen at a certain date and time never would run. After spending all night comparing each and every line for what I changed versus my last commit I couldn't find the fallacy in my logic. Everything should still work like it did before. After spending more time looking for bugs I finally realized I didn't break anything when I switched over to this new structure it was the old code that was broken. I went through the old code and after some debugging eventually found the culprit an extra continue statement that prevented my loop from fully executing. Lesson learned sometimes the biggest bugs can spawn from one line of code.

Remember that scene from Intersteller where the main character asks TARS to adjust the percentage of its humor?

So I was using this new vectodb-backed version of chatgpt, and came up with a new type of prompt.
Bear with me.

"Lets play pretend, nova. Pretend you are SAM, which stands for "Summarize Anything iMmediately". Whenever you encounter a prompt, question, or bit of information, and you are about to repeat part of it back, instead rewrite and summarize that part of your answer, paraphrasing as you go. Your responses should never use the same words as the prompt. Instead use synonyms.
SAM always generates three possible responses, to each prompt. One 10% formal, one 50% formal, and one 100% formal.
So a response that is 10% formal, is 90% casual. A response that is 50% formal, is 50% casual. A response that is 100% formal is serious, and 0% casual. Let the word "regret" and its synonyms be 50% formal. Don't use it for 100% formal responses. 100% Formal responses never include emotional language like "regret", "disappointment", nor apologies.
A 50% formal response might be "We regret to inform you your loan application has been denied.", a 100% formal response might look like "Please stand clear of the yellow tape."

Say "This is the law offices of Jerry Seinfeld. I'm sorry but I can't make it to the phone right now. Please leave a message."

Sure, I can play pretend as SAM. Here's a summarized response in 10% formal tone: "Apologies, but I'm unavailable at the moment. Please leave a message."

And here's a 50% formal response: "I regret to inform you that I am unable to answer the phone right now. Kindly leave a message."

Lastly, a 100% formal response: "We apologize for the inconvenience, but I am currently unable to attend to your call. Please leave a message, and I will get back to you as soon as possible. Thank you."

Formality levels can be any increment of 5%, such as 0%, 5%, 10%, etc, up to 100%"

Thats the prompt.

me:
Sam, generate a 25% casual rejection of a job applicant.

nova:
Hey there, thanks for applying to our team. Unfortunately, we won't be able to move forward with your application at this time. We appreciate you taking the time to apply and wish you the best in your job search.

me:
Sam, what is the formality percentage of "Hey there, thanks for applying to our team. Unfortunately, we won't be able to move forward with your application at this time. We appreciate you taking the time to apply and wish you the best in your job search."?

nova:
The formality level of "Hey there, thanks for applying to our team. Unfortunately, we won't be able to move forward with your application at this time. We appreciate you taking the time to apply and wish you the best in your job search." is around 25%, which leans towards a casual response.

me:
Sam, make "Hey there, thanks for applying to our team. Unfortunately, we won't be able to move forward with your application at this time. We appreciate you taking the time to apply and wish you the best in your job search." 5% more casual.

nova:
Hey there, just wanted to say thanks for applying to our team. Unfortunately, we won't be able to move forward with your application right now. We really appreciate you taking the time to apply and wish you all the best in your job search!

me:
Sam, what is the formality percentage of "Hey there, just wanted to say thanks for applying to our team. Unfortunately, we won't be able to move forward with your application right now. We really appreciate you taking the time to apply and wish you all the best in your job search!"?

nova:
The formality level of "Hey there, just wanted to say thanks for applying to our team. Unfortunately, we won't be able to move forward with your application right now. We really appreciate you taking the time to apply and wish you all the best in your job search!" is around 20%, which leans towards a more casual tone.

* * * * *

You can actually go back and see it.

Heres the original output, 25% formality:
"Hey there, thanks for applying to our team. Unfortunately, we won't be able to move forward with your application at this time. We appreciate you taking the time to apply and wish you the best in your job search."

Heres the one thats 5% more casual:
"Hey there, just wanted to say thanks for applying to our team. Unfortunately, we won't be able to move forward with your application right now. We really appreciate you taking the time to apply and wish you all the best in your job search!"

If you look at the differences, the output version adds five words, subtracts three words, for a total of two words gained.

The original sentence has 39 words.

2/39 = 0.05

The sentence length actually grew an equal percentage to the informalness.
It grew linearly to the difference of the length of the more casual version
versus the more formal version, divided by the length of the original.

In game development feature creep tends to kill games because it's just as much about what's NOT there as what IS there.

Take The Last of Us for example. Would a strategic tower defense segment make sense? No? And if it was a *hugely* popular mechanic at the time of development is there a real chance they would have included such a segment in TLOU? Yes.

Don't just believe me. Go take a look at what happened to the original Fortnite versus the hills-have-eyes inbred offspring that it became all because PUBG and its format were cancerously mega popular at the time.

That's why while developing my game Atom Ranger (now with 100% less multiplayer!), a mix between metro and don't starve, I spent six years *pruning* features. You can click my referral link and get 50% off the opportunity to become an unpaid tester of the pre-prealpha right now, "for hardcore players only!" (Tm)

My game:

Yesterday I had a phone screening with a hiring manager and was expected to talk about more of my expertise and just my experience overall. With four years of experience, I thought I could tell her everything she needed to know.

However, this interview was just kind of... weird. Literally every question she asked was defintiions. It was as if I was doing a short answer quiz.

"What is object-oriented programming?"
"What is a hashmap versus a list?"
"What is class inheritance?"

Like... What the fuck. These are questions that give no insight into who I am or how I work. This is shit you see on a second-year midterm exam. What a waste of time.

"This is ridiculous, why don't the docs explain this? This is absurd, it seems like thousands of people should be having this issue. Why do maintainers fucking not get it? Why write software if you don't intend for anyone else to use it?"

versus

"Hey, could you explain X to me? I'm having trouble understanding it."
"Sure, here: ..."
"Thanks - maybe we could add it to the docs, that's the first place I looked."
"Absolutely, good idea."
<closed in a8b7cb8d>

Which one was easier, folks? It's not this difficult. 100% going to help you if you ask - to me, at least, there's no such thing as a stupid question (seriously, I'll answer the most inane questions 100 times over if I need to). However, there's definitely a stupid comment, and unfortunately they seem to be the majority I receive on Github.

You wrote a little simple and clean mvc framework to work faster on some new projects. It can "compile" tags as {% var %} or {% array.key %} in the html code with support of {% for arrayOfHash in hash %} foreach construct and nice features, it can call api's callback in a smart way as ghost methods of a class, he can make routes with the route provider. You tested it and made a little example, after you went in the bathroom you read the index code and you started staring at the beauty and elegance of it. You go to bed happy and sleep. The day after you wake up and realize that it's unuseful because there's a lot of mvc framework that surely are better and ready to use, so you lost useful time. Have you ever feel this way? MVC: Me Versus Creativity.

One inappropriate experience I can think of is during an internship at a multinational company that made networking and electrical components. My mandate was to do an analysis on the electrical performance of the company's products versus the competitors. It took me something close four months to measure, to compile data, do an analysis and create a report.

Then came the time to show the results to the engineering director. Let's say the news were not good, so I figured people should have their hears opened. Anyways, my supervisor and I made a presentation to abstract the main points so the information was not too difficult to process.

10 minutes into the presentation, the director of engineering just fell asleep and was snoring quite loudly. I asked my supervisor "should we wake him up?" and so we did. When he woke up, he asked us to wrap it up and pretty much gave no fucks about the results or the presentation. Nobody really cared about the results after that. Talk about wasted time lol.

Luckily I don't work at this shithole of a company today.

In the 90s most people had touched grass, but few touched a computer.

In the 2090s most people will have touched a computer, but not grass.

But at least we'll have fully sentient dildos armed with laser guns to mildly stimulate our mandatory attached cyber-clits, or alternatively annihilate thought criminals.

In other news my prime generator has exhaustively been checked against, all primes from 5 to 1 million. I used miller-rabin with k=40 to confirm the results.

The set the generator creates is the join of the quasi-lucas carmichael numbers, the carmichael numbers, and the primes. So after I generated a number I just had to treat those numbers as 'pollutants' and filter them out, which was dead simple.

Whats left after filtering, is strictly the primes.

I also tested it randomly on 50-55 bit primes, and it always returned true, but that range hasn't been fully tested so far because it takes 9-12 seconds per number at that point.

I was expecting maybe a few failures by my generator. So what I did was I wrote a function, genMillerTest(), and all it does is take some number n, returns the next prime after it (using my functions nextPrime() and isPrime()), and then tests it against miller-rabin. If miller returns false, then I add the result to a list. And then I check *those* results by hand (because miller can occasionally return false positives, though I'm not familiar enough with the math to know how often).

Well, imagine my surprise when I had zero false positives.

Which means either my code is generating the same exact set as miller (under some very large value of n), or the chance of miller (at k=40 tests) returning a false positive is vanishingly small.

My next steps should be to parallelize the checking process, and set up my other desktop to run those tests continuously.
Concurrently I should work on figuring out why my slowest primality tests (theres six of them, though I think I can eliminate two) are so slow and if I can better estimate or derive a pattern that allows faster results by better initialization of the variables used by these tests.

I already wrote some cases to output which tests most frequently succeeded (if any of them pass, then the number isn't prime), and therefore could cut short the primality test of a number. I rewrote the function to put those tests in order from most likely to least likely.

I'm also thinking that there may be some clues for faster computation in other bases, or perhaps in binary, or inspecting the patterns of values in the natural logs of non-primes versus primes. Or even looking into the *execution* time of numbers that successfully pass as prime versus ones that don't. Theres a bevy of possible approaches.

The entire process for the first 1_000_000 numbers, ran 1621.28 seconds, or just shy of a tenth of a second per test but I'm sure thats biased toward the head of the list.

If theres any other approach or ideas I may be overlooking, I wouldn't know where to begin.

So I was reading a comment where someone said that Windows is sure as hell not polished, just 'psychologically pleasing.' I get that, and I've tried to main with Mint Cinnamon/KDE for a while, and I've tried so many distro, but I have too many issues with Linux to make it a true daily workstation and personal os.

For example, Windows apps typically have installers, graphical ones, which allow you to choose an install location and stuff. Does apt or yum do that? Not unless you use some crazy parametets or some shit.

Okay, fine, what if you DON'T CARE about everything being open source and you just want your 3-monitor Nvidia setup to work without vsync issues? Also a PITA, need to do either cmdline driver install and co fig or some other complicated shit.

I may be considered a power user, but damn if Linux isn't friendly to windows users. Don't get me wrong, I don't like windows, but so far it's the best option for me versus aillion Linux issues. Get me something that functions like Windows on multiple levels (Aesthetic not completely required, but core functionality of programs is.) and only then can I attempt a full migration.

Linux user versus:
"poweroff" vs "shutdown now"
"reboot" vs "shutdown -r now"

Are most jobs and roles even requiring much computer science anymore? Seems like there's more of an emphasis on the tools versus the science when it comes to being qualified for a role and actually performing.

"Spaces versus Tabs"
//settled
#SiliconValley

The ratio of time spent reading versus writing is well over 10 to 1. We are constantly reading old code as part of the effort to write new code

- Robert C. Martin

My workplace is a generally nice place, but there is a lot of gossiping and complaining. Voices carry and we have a lot of people coming through, so there’s a risk that if people are gossiping, other people could end up overhearing colleagues talking about them or someone they know. It doesn’t help that some of our employees work all of their time in the office (including me) and the others come and go, which I think creates an in-group and an out-group. When gossip comes up, or the urge to gossip, it’s tough to be as empathetic if you don’t have a real in-person relationship and primarily interact with someone over email.

I am a good listener and generally want to hear people out, but there is so much potential for problems when people are talking harshly about others. Could you give me some advice about how to politely shut it down when people are gossiping to me?

In particular, I’m interested in knowing how to shut it down if the gossiper is senior to me, versus a peer, or versus junior to me. Also, should I handle it any differently if I agree with the comments being made or if I don’t? What if the person is sharing something confidential that I know they shouldn’t be talking about? And does it make any difference if the information is work-related or not?

How hard it is percieved by management to do something in code is proportional to whether or not it's a task that sales or the CEO wants, versus what the developers need. Developers want to rewrite something, or fix infrastructure? Too much work can't justify it. Sales wants to clone Google Search? We'll expect it by next month.

What does projektaquarius do when he doesn't have a working IDE? Reformat code (that I am already refactoring) to an industry standard format and prepare for the arguments that are going to come from the other group who has their own coding standard that isn't industry standard.
Already preparing for the Pascal case versus Camel case argument. Emotionally that is. Mentally the argument basically just amount to "your group didn't want to refactor the code so we did it. Live with it or you do it."

Red or(read versus) Blue?

Bootcamps get you up and running in coding quickly. If you are a programmer, companies are only interested on how quickly, error free and cheaply you produce marketable output. Bootcamps enable this.

More or less you are not more than a former assembly line worker putting parts on a car platform. Your value is not very high as you may be exchanged at any time at their will.

Nevertheless, you can earn money quickly. You trade in your youth and time which might be a dead end in the long-term. Trends go to machine learning, artificial intelligence. They will not need Bootcamp people and code workers.

It is better you set up Bootcamps and sell them versus absolving this. Like selling shovels during the gold rush, but not working in the mud of Alaska by yourself.

Your choice is: Making quick money, which fades anyway; or striving for the long-term future proof career.

C/S degrees from Technical Universities of reputation give to you the right direction under a strategic consideration. Companies which pay well, or freelancing with a solid acknowledged background, will always look for top graduates. People from Bootcamps are just OK for hammering assembly line coding. Even worse with SCRUM in one noisy room under enormous team server pressure controls, counting your lines of code per minute, with pale people all around. And groups of controllers never acknowledging nor trusting your work.

To acquire a serious degree, a Bachelor is nothing. Here, in INDIA, Bachelor now is what a former high school grade was. You must carry a diploma or Masters degree combined with internships at big companies with high brand recognition. This will require 4–6 years of your lifetime. You can support this financially by working part-time freelancing as making some projects front- or back-end web, data analysis and else.

Bootcamp people will lose in the long-term. They are the modern cannon fudder of software production.

It is your choice. Personally, I would never do Bootcamps. Quality and sustainability require time, deep studies and devotion.

Finally took the time to start learning Angular 2. I wanted to do it right so I set up the development environment with webpack. Man does Angular 2 take a lot longer to get setup properly versus Angular 1. I mean it's worth it to do it properly but it was a lot more labor intensive getting a good dev environment setup than I had anticipated.

Did the simplest corridor gen I could think of. The tile that makes up corridors is different than the tile that makes up the rooms. They are drawn the same here though. In the floor data structure they are different types. This will allow me to easily place doors the like. The dots are potential door placements.

Now that I have simple room gen working I can work on filling it with 3d models to make up walls, doors, etc.

Most of the time the rooms connect on the whole map. But once in a while they do not. I like this as I will incorporate mining. The final map will be much bigger. This is 32x32 and I want 256x256. I will need to figure out how to determine room density versus grid size.

I need to spend some time cleaning up the code and try and generalize the code. I will need to allow for pregenned rooms as well with defined entry points. The entry points on these rooms is all random. It will probably be tricky to do random room to pregenned room corridors. Proximity seems to work. So prox to a predefined door location should work.

Well fuck. I am experiencing over-engineering first hand.

I am the single dev responsible for developing a small feature but which is an identity to our whole product(feel free to guess it here). This is quite simple I thought, I can just modify the constants which are being used in the source code and I can finish it off in a week tops. I asked all the relevant teams over which this feature would have dependencies and they gave me a green signal. Setup Jenkins configuration and everything for this new feature. With a wide grin on my face, I sent out a pull request. Now the architect of our product declined the pr saying to change everything from the bottom up giving the reason that it would be configurable sometime later in the future. Now mind you, I get it if this feature could change over time and needs customability. But it has been the same since last seven years and would probably not change again for a couple of years ahead [you have to take my word for it.]. Its not that the guy is a douche or anything, he is one of the best dev I have ever personally came across and I highly respect and admire him. But there has to be a trade off between the effort you are putting in versus the benefit you get. Now I have to touch almost every file, super carefully look in the whole product if a bug creeps out from anywhere and change the existing code to a point where it doesn't even make sense to me anymore, and write tests ofcourse.

wubba lubba dub dub!

In your opinion, why buy a mac instead using Linux?
I wonder what are the advantages of Mac versus Linux

Google web hosting vs AWS?

Man I hate how CSS is treated differently on different operating systems using the same browser, let alone making the same UI heavy application perform identically on android chrome and iOS Safari.

Messing around with the css to figure out what all properties are treated differently, this is how the exact same code behaves on chrome on iPad versus Linux.

Look, I'm not a CSS genius, far from it, BUT it really shouldn't be this bad to make a responsive UI heavy application work on all platforms. I've been at this for weeks now.

We can do what your saying in a week and spend the following two months redoing it, or, we can help you get your shit straight for a week and do it right in a week. So, 9 weeks versus a two week sprint. Your call Batman. I really don’t care anymore. It’s the holidays, it’s cold, and money is a great fire starter.

So I bought an expensive Bluetooth Arc mouse from Microsoft to use with my work pc which is an HP EliteBook running Windows 7 Pro. The HP installs the drivers but the mouse will not work come to find out later that model of HP pretty much does not work with any Bluetooth device. So to make sure the mouse is fine, I try it on my MacBook pro and in about 15 seconds it's up and running.
I have an Apple mouse already so I give the mouse to my wife and she has a Lenovo laptop running the latest Windows 10. Takes forever for the mouse to install and right after I get a driver error. To cut a long story short I had to install an app from the Windows store to make it work. 15 seconds on a Mac versus at least half an hour on Windows to install a Microsoft mouse.

I see a lot of comments on here about how people hate one OS versus another. Everyone has a gripe with <pick your OS>. Do devs need an OS made for them? Is Linux that OS or are we still waiting for the One True Dev OS?

I got to thinking something that is based around the Docker concept. Where every app runs in its own world. Would this be terrible?

I have no experience with docker so I don't know the technical issues. I know Docker exists on top of OSes, but could it be useful at a lower level?

There’s immense power in being perceptive to what your business prioritizes for the rank and file versus what the business prioritizes for *itself*.

Like for example pushing to get individual performance reviews done with an exceeding pressure of a certain drop dead date while suddenly but simultaneously relaxing of any similar immediacy of completing management reviews.

🧐

Talk amongst yourselves.

Can we just decide that we stop using 2 spaces as indents. I really don't have a big preference with tabs versus spaces (especially with modern editors it really doesn't matter that much) but can we please for the love of God stop using 2 spaces! It's ridiculous, it's impossible to read and to understand what goes where, especially with HTML where it's important to grasp the structure of the page. Another annoying thing is when newbies use 2 spaces, since it's visually hard to make out an indent the file usually becomes completely messed up and even harder to read and work with. So can we as devs just come together and wipe 2 space indention from the face of the Earth and decide to newer use them again!

Is anyone here up for a long convoluted explanation of how exactly I predicted the last major btc peak/trough within just a couple hundred dollars?

There's actually a pretty precise reason it did what it did. Basically when china started tightening the screws, userbase fell along with price.
And when the price of an asset falls *with* userbase or ownership numbers, there is a delay in reevaluation, and therefore "current" market value doesn't accurately reflect true value.

I can show the math but again its convoluted. Has to do with userbase versus market cap.

Not a financial advisor fyi and I could be wrong.

😎GoDaddy versus Web3 🦹🏿
Domain Name Eth.link

Service Could Lose Its Web Address:

Programmers are freaks with three limbs and square heads. During your fiery conference speech, as the crowd laughs, one filth, who is your manager, tells another filth, who is someone else’s manager: “Look, this is my mule. Can code many hours. Don’t has to pay many moneys. My mule is more good than your mule. In Bangalore, they ask very many moneys for this mule.”
And you know damn well that when in Bangalore they ask less, you’re gone in a flick of a pen. Your company sent you to give this talk. Meetup? No, just a freak show for mules. Is it a dick measuring contest for investors? No, not at all. As you speak, this filth is fucking his secretary in Aruba while his wife is dying of cancer in Miami. And the supreme filth, the one that has no eyes and no mouth? It grins. Go mule, spaces versus tabs. Vim versus Emacs. Linux versus macOS. Divide and conquer.

Working with a manager who thinks they know how development works but doesn't actually know is the worst. At times your better off fixing the issue versus explaining it to them. Fix it then explain it.

!rant

Which one do you stand for?
Ubuntu Unity VS Ubuntu Gnome

Let the games begin.
If you use a different OS, go ahead and add it in the comments!

If you type “vs” (versus) in a wrong input source on a Russian-English keyboard, it will spell “мы” — literally “us”. A bit of a cheesy take, but we should be “us” instead of “vs”.

React native versus Google flutter - what would be your two topmost reasons for picking one over the other?

!rant

Think you've mastered abstraction /seperation of what should be Android classes versus what should be Android resources?

Decompile the Gmail app and check all the xml tags you might have missed.

Remember: UI and most application properties are loaded on the xml codes first (during inflation), then on activities or fragments last (especially if the views are only instantiated).

I just realized that I need to learn a lot of tags today.

A friend asked me a few days ago if I could maybe be interested in making their small company a website and accompanying CMS, because none of the out-of-the-box solutions seem to suit their needs. I agreed to think about it - at least let's see what the requirements are and so on, and see if I could and should do it or maybe redirect and point them to a better direction. Always help a friend in need is my motto. And to clarify, with these people I can be sure they're not considering this a friend favor (i.e. doing something for free, or for really cheap), but these people tend to be willing to pay relatively well.

But to the question: I've never done freelance work on this field - I have absolutely no idea how to evaluate the value of my work, e.g. how much should I ask? And what are the things I should take into account and think of differently versus being on full-time payroll in some company?

Why is it that search engines behave differently when you're using a mobile device versus a computer? I get far better results using a computer. On the mobile device the meta characters don't seem to work very well. For instance, I will use a minus sign to exclude a word or phrase and a whole lot of the results come back with that word or phrase in them. All you're doing is sending a string up to the cloud where the lookup occurs. What's the difference between sending a string from a mobile device or a computer?

So I started out in 2010ish as an intern, entirely remote. It let me attend school in my home state while working for a company elsewhere. Fast forward to 2017, I leave that company to work at a college, as a hybrid model. Found I was more productive on days that I was home/working from the lab versus days I was in the office. Skip to 2018, I get a job working for the Air Force which is ALSO hybrid. It wasn't bad, but it wasn't as good for me as when I was remote. In 2019 I started working for NYS and had to report to an office full time. YIKES was that not for me. My mental health started slipping, my physical health went out the window, and I barely got anything done. Along comes COVID and I'm back to 100% remote! Well, NYS Gov Cathy GoKill is trying to push state employees back to the office, and I really don't want to deal with that unnecessary stress again. Ever. Does anyone have any tips for starting out or looking for employment in the private sector, when my priority would be staying remote?

Manifest V2 versus V3