Boss: we need high precision volume control
Me: say no more...

I'm at my seat during the regular morning routine of checking emails, planning the things I need to complete/study when my phone rings.

HR: Good Morning, can you come over to the conference room please ?

Me: Sure

I enter the conference room and on the other side of the table, I see a group of 3 HR Managers (not a very nice feeling), especially when it was 10 months into my first job as a Trainee Software Developer.

HR: The company hasn't been performing as expected. For this reason, we've been told to cut down our staff. We're sorry but we have to let you go. You've been doing a great job all along. Thank you.

Me: ---- (seriously ?!)

The security-in-chief 'escorts' me out of the premises and I hand over the badge. I'm not allowed to return to my desk.

This happened about 16 years ago. But it stuck with me throughout my programming career.

A couple of Lessons Learnt which may help some of the developers today :

- You're not as important as you think, no matter what you do and how well you do it.
- Working hard is one thing, working smart is another. You'll understand the difference when your appraisals comes around each year.
- Focus on your work but always keep an eye on your company's health.
- Be patient with your Manager; if you're having a rough time, its likely he/she is suffering more.
- Programming solo is great fun. However it takes other skills that are not so interesting, to earn a living.
- You may think the Clients sounds stupid, talks silly and demands the stars; ever wonder what they think about you.
- When faced with a tough problem, try to 'fix' the Client first, then look for a solution.
- If you hate making code changes, don't curse the Client or your Manager - we coders collectively created a world of infinite possibilities. No point blaming them.
- Sharing your ideas matter.
- Software Development is a really long chain of ever-growing links that you may grok rather late in your career. But its still worth all the effort if you enjoy it.

I like to think of programming as a pursuit that combines mathematical precision and artistic randomness to create some pretty amazing stuff.

Thanks for reading.

Precision 😂

Try not to use floating point numbers in places where precision is important. Like for instance, money. Always store the base value where it makes the most sense

Some milk. 😇😀

I used to work in a role that was basically tech support for engineers. Folks would call, we'd look at their code and see where things were going wrong.
One customer calls in, they're having timing problems with a satellite control system.
I dig down through their code, and buried in one of the modules is a comment to the effect of:
"Once we upgrade to Windows 98, we'll need to change this call to the precision counter"

They never did.

This system was running XP.
Somehow, they'd avoided destroying satellites despite having the code run on Win98, and ME without fixing that call. It wasn't until they upgraded to a multi core system and XP that their gyros stopped responding correctly.

Holy shit.

Mountain climbing. Increases social skills, teamwork and trust.

Building a house. Increases spatial visualization and planning skills.

Electronics. Increases mathematical and problem solving skills.

Chemistry. Increases precision and analytical reasoning skills.

Psychedelic drugs. Increases imagination, inspiration and abstraction skills.

I feel the need to take a different approach to this week's rant. I think someone needs to defend teachers, for a number of reasons. Obviously this is probably out of place on devRant but it is a kind of rant against those who think they know everything and have nothing to learn.

1) Teachers are not industry specialists. They do not spend their lives keeping on top of the latest framework or project management methodology or code management tool. They are educators and that brings its own set of out of hours challenges and training exercises.

2) They have a course to teach and have probably used the same one for quite some time. Years probably. They (should) teach the fundamentals of programming not a particular language or syntax or quirk. Those fundamentals don't really change. Logic, problem solving, precision, structures, etc.

3) They need to provide a course which will cater for different skill levels. There are always class members who are bored because it's too easy and others who struggle in any subject.

4) Teaching is like any profession - there are really, really good ones, OK ones and there are shit ones.

5) They have probably never developed a detailed project or solution in their lives. They don't know the pitfalls and challenges that teams face in this kind of environment. Should they - maybe. But the probably don't.

I think that's all... I'm not a teacher (although I did fancy the idea at a time) but just feel they get a rough ride sometimes (particularly on here).

Found this on discord.
Could be copypasta but I decided to share it anyway.

"I use Linux as my operating system," I state proudly to the unkempt, bearded man. He swivels around in his desk chair with a devilish gleam in his eyes, ready to mansplain with extreme precision. "Actually", he says with a grin, "Linux is just the kernel. You use GNU+Linux!' I don't miss a beat and reply with a smirk, "I use Alpine, a distro that doesn't include the GNU coreutils, or any other GNU code. It's Linux, but it's not GNU+Linux."

The smile quickly drops from the man's face. His body begins convulsing and he foams at the mouth and drops to the floor with a sickly thud. As he writhes around he screams "I-IT WAS COMPILED WITH GCC! THAT MEANS IT'S STILL GNU!" Coolly, I reply "If windows was compiled with gcc, would that make it GNU?" I interrupt his response with "-and work is being made on the kernel to make it more compiler-agnostic. Even you were correct, you wont be for long."

With a sickly wheeze, the last of the man's life is ejected from his body. He lies on the floor, cold and limp. I've womansplained him to death.

Recently buyed some toilet paper.

Now i just want to have an intense discussion about floating point precision with the idiot who developed the cutting machine...

Also, please stop printing cars or birds there. Thanks.

My first AI program in the 1985 on Apple IIe (64kb ram computer) was answering simple questions with yes and no. Everyone were shocked with precision of about 100% when I was typing and 70-80% when others were typing. My parents were scared and skeptical. How it works? Store the time between the first key pressure and the following, when it is larger than 1 second the answer is yes, otherwise no. They say the question, you know the answer and type accordingly. When they want to write the question themselves, you try to force their typing speed if possible. I was 12 years old and it was very funny.

POSTMORTEM

"4096 bit ~ 96 hours is what he said.

IDK why, but when he took the challenge, he posted that it'd take 36 hours"

As @cbsa wrote, and nitwhiz wrote "but the statement was that op's i3 did it in 11 hours. So there must be a result already, which can be verified?"

I added time because I was in the middle of a port involving ArbFloat so I could get arbitrary precision. I had a crude desmos graph doing projections on what I'd already factored in order to get an idea of how long it'd take to do larger
bit lengths

@p100sch speculated on the walked back time, and overstating the rig capabilities. Instead I spent a lot of time trying to get it 'just-so'.
Worse, because I had to resort to "Decimal" in python (and am currently experimenting with the same in Julia), both of which are immutable types, the GC was taking > 25% of the cpu time.

Performancewise, the numbers I cited in the actual thread, as of this time:
largest product factored was 32bit, 1855526741 * 2163967087, took 1116.111s in python.
Julia build used a slightly different method, & managed to factor a 27 bit number, 103147223 * 88789957 in 20.9s,
but this wasn't typical.

What surprised me was the variability. One bit length could take 100s or a couple thousand seconds even, and a product that was 1-2 bits longer could return a result in under a minute, sometimes in seconds.

This started cropping up, ironically, right after I posted the thread, whats a man to do?

So I started trying a bunch of things, some of which worked. Shameless as I am, I accepted the challenge. Things weren't perfect but it was going well enough. At that point I hadn't slept in 30~ hours so when I thought I had it I let it run and went to bed. 5 AM comes, I check the program. Still calculating, and way overshot. Fuuuuuuccc...
So here we are now and it's say to safe the worlds not gonna burn if I explain it seeing as it doesn't work, or at least only some of the time.

Others people, much smarter than me, mentioned it may be a means of finding more secure pairs, and maybe so, I'm not familiar enough to know.

For everyone that followed, commented, those who contributed, even the doubters who kept a sanity check on this without whom this would have been an even bigger embarassement, and the people with their pins and tactical dots, thanks.

So here it is.
A few assumptions first.
Assuming p = the product,
a = some prime,
b = another prime,
and r = a/b (where a is smaller than b)
w = 1/sqrt(p)
(also experimented with w = 1/sqrt(p)*2 but I kept overshooting my a very small margin)

x = a/p
y = b/p

1. for every two numbers, there is a ratio (r) that you can search for among the decimals, starting at 1.0, counting down. You can use this to find the original factors e.x. p*r=n, p/n=m (assuming the product has only two factors), instead of having to do a sieve.

2. You don't need the first number you find to be the precise value of a factor (we're doing floating point math), a large subset of decimal values for the value of a or b will naturally 'fall' into the value of a (or b) + some fractional number, which is lost. Some of you will object, "But if thats wrong, your result will be wrong!" but hear me out.

3. You round for the first factor 'found', and from there, you take the result and do p/a to get b. If 'a' is actually a factor of p, then mod(b, 1) == 0, and then naturally, a*b SHOULD equal p.
If not, you throw out both numbers, rinse and repeat.

Now I knew this this could be faster. Realized the finer the representation, the less important the fractional digits further right in the number were, it was just a matter of how much precision I could AFFORD to lose and still get an accurate result for r*p=a.

Fast forward, lot of experimentation, was hitting a lot of worst case time complexities, where the most significant digits had a bunch of zeroes in front of them so starting at 1.0 was a no go in many situations. Started looking and realized
I didn't NEED the ratio of a/b, I just needed the ratio of a to p.

Intuitively it made sense, but starting at 1.0 was blowing up the calculation time, and this made it so much worse.

I realized if I could start at r=1/sqrt(p) instead, and that because of certain properties, the fractional result of this, r, would ALWAYS be 1. close to one of the factors fractional value of n/p, and 2. it looked like it was guaranteed that r=1/sqrt(p) would ALWAYS be less than at least one of the primes, putting a bound on worst case.

The final result in executable pseudo code (python lol) looks something like the above variables plus

while w >= 0.0:
if (p / round(w*p)) % 1 == 0:
x = round(w*p)
y = p / round(w*p)
if x*y == p:
print("factors found!")
print(x)
print(y)
break
w = w + i

Still working but if anyone sees obvious problems I'd LOVE to hear about it.

Fuck Firefox's CSS engine! Why is it so fucking buggy?

I needed to position some elements in a circle, so I used Math.cos(Math.PI / 2) to calculate their x positions. So, mathematically speaking, that should return 0, right? Turns out in JS it doesn't (because fuck precision). It actually returns 6.123233995736766e-17 and I was using that in the style, like top: offset + that.

In chrome it was working perfectly, but in Firefox all hell broke loose. All animations stopped working, scripts stopped working, demons were eating people alive.

And I lost hours hunting that down. My fault because I should have tested it immediately on other browsers, but fuck!

Today on forgotten games – Ballance.

The game is absolutely outstanding. Graphics is absolutely amazing even though the game was developed in 2004. The sound effects are perfect, I can literally feel the wooden ball rolling on steel rails. The background music is also amazing, we're talking Alexander Brandon level here.

The game is about rolling the ball through the levels trying not to fall off. There are three balls: the stone one, the wooden one and the paper one, different in weight, velocity and momentum.

I admire the clever level design. It uses in-game map features in multi-purpose way, for example some levels use ball transformers (the things that transform the ball from one kind to another) as a trap for your ball to lose momentum. It even seems like that levels were designed by some crazy modders for advanced players, but they weren't, and traveling through them feels like you're a pro gamer playing custom levels.

Even though levels seem simple at first glance, they allow non-linear gameplay and different gaming styles.

The gameplay itself is pure meditation. But even though the concept seem straightforward – just follow the level and don't fall – it's not. You have to use all three ball types: there are air vents to fly above upon, which only paper ball can do, there are obstacles to push, which only stone ball can do, and so on.

For additional sonic satisfaction the levels even feature some metal domes that serve no purpose but to be bumped into just for making amazing gong sound.

I like it that when you get cocky and think like that's easy, I got this, the game quickly puts you into place. It basically says nigga you ain't shit, you got nothing on me.

Overall it's basically a mesmerizing travel through cleverly designed levels surrounded by relaxing music and outstanding graphics.

Definitely a must-have for mechanical keyboard gamers, it's a pure satisfaction playing this game with a great level of precision and control mechanical keyboard allows.

Search for "ballance widescreen fix" for modern displays support.

I seriously do not understand the rants against Windows.

I love Windows 10 (got as free upgrade from MS), and have no issues with MacOS or Linux OS. I use them as well but do all serious work on Windows.

All my life, I have worked on business / commercial side and picked up Web development in last couple of years. I started using computers on DOS in 1992, and shifted to Windows 3.0 in 1995. There was no Mac or MacOS back then.

For serious work, I purchased a old Dell Precision M4700 workstation grade laptop with quad-core i7, at throwaway price, got 32GB RAM, 2.4TB (1x2 TB + 400gb) of SSD on super sale online, and installed it myself. It easily supports dual 4k monitors.

Git-bash on windows allows all the necessary linux command line on windows. Though not tried, Windows 10 allows embedded Ubunutu with linux terminal. Web development tools like - VSCode, git, github / bitbucket clients, NVM/Node, React / Redux / Webpack / Gatsby / Jest, REST clients, GraphQL client and server, Graph Server, Chrome PWA / Chrome Dev Tools, http/Websocket/WebRTC interception, Google Firebase SDKs, AWS sdks, cloud utilities, CI/CD tools work flawlessly. Windows even has its own package manager for applications.

Fuck Apple sideways! (Wait for it, the original part begins)

HOW can a company that keeps on boasting about UX, to the point that last WDC they took more time speaking about a fucking kaleidoscope animation for their watch then about the whole changes to their MacBook's hardware, even consider putting that turd of a remote on market.

If you have an Apple Store in reach, I invite you to get up, flush, and go there. Try that atrocity that is the AppleTV, and laugh at how incredibly bad it is. Then do your best to refrain from burning the place down in your inevitable rage, that might cause you legal issues.

The previous AppleTV was fine, it was practically useless, but usable. But for some reason they decided a touchpad with low precision and no gestures was a good idea to put on a remote to a thing that will, due to its target audience, most likely be plugged into a fancy TV that has a 300ms lag due to fancy image processing. That thing gives no feedback, appart from visual, has so little precision that in a movie, the smallest step I've achieved was 5 fucking minutes, while being really fucking careful not to spoil the movie.

21:30, sysadmin, chatting with my colleagues, when one posts a screenshot of a message he just received from a dev :
"Hello, sorry for bothering you this late but we have a demo tomorrow morning and the app is completely stalled. It fails with the message 'cannot write to <file>, no space left on device'"

I say "I bet that they somehow managed to make their DB grow uncontrollably".

Colleague asks which server hosts the app, Dev answers "one of ours", then adds after a few seconds "wait, do you need the IP of the server? Dev2 should be able to provide it", before finally adding "we use a scheme in <other project> DB actually".

Finally, Dev2 declares that the bug is solved: "There was a loop that caused a DB view to grow constantly and it filled the filesystem".

Me: "Called it".

They cleaned the view: 41GB freed.

Hey I got reminded of a funny story.

A friend of mine and me were in internships in the same company. The company was specialized in territory resources management (managing water for agriculture, money to build industrial zones...). He got the interesting internship (water predictory modeling) and I got... The repairs of a reference sheet manager that never happened to work. It was in C# and ASP.NET and I was in second year of CS. I expected the code to be nice and clear since it was made by a just graduated engineer with +5years of studies.

I was very wrong.

This guy may never have touched a web server in his life, used static variables to keep sessions instead of... well... sessions, did code everything in the pages event handlers (even LinQ stuff et al) and I was told to make it maintainable, efficient and functional in 2 months. There were files with +32k LoC.

After 1week of immense despair, I decided I will refactor all the code. Make nice classes, mapping layer, something close to a MVC... So I lost time and got scoled for not being able to make all the modifications as fast as in a cleanly designed code...

After 4 weeks, everything was refactored and I got to wait for the design sheets to change some crystal report views.

At this moment I began to understand were was the problem in this company.

My friend next door got asked to stop his modeling stuff for an emergency project. He had to make an XML converter for our clients to be able to send decentralized electrics bills, and if it was not completed within a week, they would no longer be able to pay until it is done.

This XML converter was a project scheduled 5 years before that. Nobody wanted to do it.

At the same time, I was waiting for the Com Department to give me the design views.

I never saw the design views. Spent one month implementing a golden ratio calculator with arbitrary precision because they ain't give me anything to do until the design were implemented.

Ended with a poor grade because "the work wasn't finished".

My Dell Precision M4700 is going to complete 6 years of faultless service, still my main workstation.

It arrived with 3rd gen core i7, 8gb RAM and 750gb 7200rpm hard drive with Windows 7. It gradually transformed into 32gb RAM, 3tb of ssd and Ubuntu 18.04. This dude still runs for days without a problem.

Genuine respect!!

p.s.: If I have to change my next machine, it would be "Dell Precision 7730".

Float point precision done right :-P

@OmerFlame wanted to see more of Soviet pirate stuff, so there you go buddy. This is an example of Samizdat (“self-publishing”) — Soviet people made books of dissident literature that was forbidden in the Soviet Union.

This very book was made by my grandma, with lace fabric cover and sheets cut evenly with care and precision. Everything was typed on a typewriter, yes, the thing that renders the whole page useless with one mistype, as there is no backspace key.

This book dated 1975, the poetry of Nikolay Gumilyov.

When your programming skills give you godly precision skills. I guarantee you I never touched it.

I just love the love the perfect pixel precision that apple allows on their 'perfect' designs.

*packing for a school-hosted graduation celebration with friends*
let's see, first rule of packing for a trip, count on every slim chance happening...

List of things now in backpack:
3 changes of clothes (1-night trip for an all night party in <100-MILE-AWAY MAJOR CITY>)
Laptop
3DS
3x 4-port USB Hubs
10-port power strip (not fully in bag, but mostly so.)
Extra pair of shoes
3.5" external floppy drive
First aid kit
SAK
precision driver set
soldering set
multitool
pliers (1x farmer's, 1x bent needlenose)
multimeter
empty laptop HDD (250GB)
magnet in Altoids tin (can't have it trashing the HDD!)
VGA to RGB (Composite ends) adapter
Composite/S-VIDEO USB capture card
Portable USB chargers (1x 30k mAh 2-port, 1x superslim 3k mAh 1-port)
Enough phone chargers to replace all chargers within 30 miles
Smelling salts
2x 16GB thumbdrives
Boot disc set
$200
School IDs (for bag's ID slot)
3 pairs of decent earbuds (no el cheapo $1 ones because they break trying to get them out of the package)
Serial to USB adapter
Rehydration salts
Magnesium fire striker
Plenty of pens and pencils
Emergency radio locator beacon
Emergency cellular locator beacon
SD/eMMC/CF/TF/MCP(D) USB reader
external HDD reader (2.5" IDE/3.5" IDE/SATA, external power)

am i missing anything?

float version = 1.8f
if (version >= 1.8f)
{
/*
Do nothing because you forgot
about floating point precision
you tool...
*/
}

I.. I'm sorry... I'll sacrifice some virtual chickens to appease the Gods.

Already have it.
CNC operator.
I wanted to be cnc programmer but for now I'll have to work with the machines.
And I love it...
Making steel pieces with a 0.01mm precision...
Preparing the tools...
Operating the machine...
That's why I'm doing my own... For over 3 years (no money to finish yet hehe).
Also, got unemployed so I made a 3D drawing formation.
Now I can design, program and machine a full mold.
To bad company owners in my country (Portugal) like slave work... And I'm not accepting jobs for the minimum wage or I would be employed already.

Our best dev/arch just quit.
C dev lead & a dev staying late chatting.

Lead: am building, takes long
Dev: unit testing, time taking

Ask them y they r building on their latitudes when we got them linux precision with xeons/64gb workstation 1 each ?
Both: I code on latitude.

Build/test times. (pure Java/maven)
Latitudes=an hr or more
Precision=2m to 11m
Jenkins Infra we have =10 mins with test & push. Parallel builds support.

Am suposed to help with an open mind. They now want Mac pro

FLOATING POINT PRECISION! FUCK YOU! Spent so much time trying to figure out what was wrong with an algorithm I made to calculate and correct bounding only to finally realise, after printing out every single variable and calculating everything manually to realise the value was off by 0.0001 which made it skip an if statement. Ughhhhhhhh, so much freaking time wasted

I've lost hope in my precision at this point:

We've updated our website to have X feature. The X feature was implemented, tested and even had unit tests... The worst part when I've lost hope? Both unit and the actual code had the same mistake in them. What was the mistake? Well...

if($variable = 'something') {}

Yeah... Read it carefully... We've always had the same case and only noticed it after 3 months when it was attempted to extend.

Funny enough, few users were harmed but no actual reports of an issue came to us.

Since then, I'm always triple checking that I have the correct amount of `=` to avoid further fuck-ups

Just got my first paycheck. Felt amazing tbh. Proceeded to make a little Python project to help me with high precision budgeting and budget analysis. So, any grad students here who invest and/or save half of their paycheck and use their own code to help them do it?

aaAAaaAaaAaaAaAAAAAaAaaa floating points!

I debugged my algorithm for quite a while, wondering why it sometimes gives out "Circle(Point({1.7976931348623157E308,1.7976931348623157E308}),1.7976931348623157E308)" as the smallest circle around a group of points.
Figured out that it sometimes just never found any circle defined by two or three of the points which included all points (which is mathematically impossible).
Then finally I made it print out the points it thought were not inside the circle:
"1,7,8: Circle(Point({0.6636411126185259,0.535709780023259}),0.4985310690982777)
skip, 1 not inside"
So it defined the circle with 1 being on the edge, but then thought 1 was outside. Thank you, floating point Math.

For anyone wondering about the notation: That way I can directly copy/paste it into Geogebra to have a visualisation.

When you have to get app thread dumps using tools provided to you: a rock, a hammer and a steel rod.

Fuck it. I'm building my own tools.

I'm pissed.
Step aside and let me show how it's done. And STOP GIVING TASKS "TO DEVELOP A TOOL X" TO TEAMS WHICH HAVE NO IDEA HOW THE TOOL IS TO BE USED, WHAT VARIATIONS MIGHT BE REQUIRED, WHAT PRECISION IS NEEDED, ETC.

I found this funny, or my dev-humor is just really bad :>

Friend: Ugh
Friend: Java and BlueJ.
Friend: Why you indicate relationships between classes that have no relationships.
Friend: Fu BueJ
Me: It's called a crush :wink:
Me: *badum-tssss*

Precision: As in having a crush on a person, but no relationship :)

When you’re trying to write a function to convert a base 10 integer to a base 2 integer in Javascript without using parseInt() and it takes you a while to realize that you’re used to integer division being integer division and have forgotten that JavaScript stores numbers as double precision floating point. *facepalm*

Can anyone see where this repeats predictably?

Decimal('507.724375') / Decimal('173.2336')

I set the precision to 500+ digits and I'm not seeing any repetitions at a glance.

If there isn't, this is my new favorite irrational number.

Most definitely not dev related..

Guitar tabs that contain arrangements for +5 guitars on a band with just a rythm and lead guitar are fucking annoying.

Fucking hate having to piece the fucking melody by myself. And yes. I DON'T neeed the fucking tabs since I can figure the song by ear, its just that doing it like that takes way too much fucking time.

Getting fucking bored of playing the guitar tho. Been doing it since I was very young and never really liked it. Always wanted violin and then bass.

Have been looking at a nice fender precision bass. Made in Mexico so not really expensive, sounds equally as good and is going for a good $650 bucks plus the amp.

No lie, i am way too interested on getting me that bass already. Have been learning Roundabout by Yes(because I am a progressive rock fan AND a Jojo fan) and practicing with a friends bass whenever I get the chance.

If you already play guitar and you are good with guitar then picking up the bass takes some adjustment, but it's still not as heavy as going at it with no musical training.

Man I just want a bass so bad. I am just so cheap at spending money.

Yesterday I wanted to make a small infographic. I started with photoshop, switched to illustrator, then indesign, then back to illustrator. All of them have super shitty quirks when it comes to work like that.
Next time I will just build it as a website and screenshot it. Elegance of code-based design is just unmatched. It brings reusability, consistency and precision to another level.

After reading the script for the architect scene in Matrix Reloaded I was determined to use the word 'concordantly' in a sentence. I am proud to say I have succeeded, and with reference to cloud computing no less.

I honestly hate writing code. I hate debugging off-by-one bugs. I hate debugging in general. My fingers are weary from 11 years of this shit. I've spent 1 hour designing + implementing this tool in C, only to have spent 11+ hours debugging this tiny thing.

Ultimately, I hate the precision the damn computer demands. It's a prissy little bitch I want to hate fuck.

I actually learnt this last year but here I go in case someone else steps into this shit.

Being a remote work team, every other colleague of mine had some kind of OS X device but I was working this Ubuntu machine.

Turns out we were testing some Ruby time objects up to a nanosecond precision (I think that's the language defaults since no further specification was given) and all tests were green in everyone's machine except mine. I always had some kind of inconsistency between times.

After not few hours of debugging and beating any hard enough surface with our heads, we discovered this: Ruby's time precision is up to nanoseconds on Linux (but just us on OS X) indeed but when we stored that into PostgreSQL (its time precision is up to microseconds) and retrieved it back it had already got its precision cut down; hence, when compared with a non processed value there was a difference. THIS JUST DOES NOT HAPPEN IN OS X.

We ended up relying on microseconds. You know, the production application runs on Ubuntu too. Fuck this shit.

Hope it helps :)

P.s.: I'm talking about default configs, if anyone knows another workaround to this or why is this the case please share.

I thought I found a way to compute PI, but I actually just found a super shitty way to print a variable..

const precision = 1000000

// convert degree to radians
function rad(degree){
return degree * (Math.PI/180);
}
function calculatePI(){
// [x, y]
// take first point on start of unic circle
const point1 = [Math.cos(0) , Math.sin(0)];
// take second point at 0.001 degree
const point2 = [Math.cos(rad(1/precision)), Math.sin(rad(1/precision))];

// Estimate 0.001 degree of circle
const dist = Math.sqrt((point2[0] - point1[0] ) ** 2 + (point2[1] - point1[1]) ** 2);
// Calculate full circle
const perimeter = dist * precision * 180;
return perimeter;
}
console.log(calculatePI());

Back again to the horrow show.
We start with the integration. It’s a new project, let’s see how it works. First step: authentication. From the documentation it claims to be an oAuth2. Wait..why just 2 steps to authenticate?! Nevermind, we’ll contact them later. Let’s go on for now.
They need a timestamp with microseconds precision. Here you are!
Nope. Come on! Take the damned timestamp! Nope. Let’s take a look at theirs. If it’s with milliseconds precision, WHY 7 digits after comma?!!!! We decided to contact them. And then.........their answer: we don’t know of any exact number of digits to represent milliseconds.

I see...so it’s arbitrary!!! What are you going to tell us next? One hour can be 3.14159265 minutes then?!!

Maybe I am just sensitive.. but sometimes I feel that my new manager is being a little harsh on me.

Again, he might behave the same with everyone and I am assuming that it's just me.

1.5 months in the new job and not a single good comment/feedback I recieved from him. It's not that he criticises me or my work, or calls me a dumbass.

But whenever I submit anything for review, I get a ton of feedback where he expects everything to extreme precision.

He guides me, explains me post my failure, and has specific pointers of what he wants/how he wants things.

But all I am given is a set of documents to read initially with an expectation that I have to figure things out. When I am not upto the mark, he then guides me.

Why I worry?

1. I am on probation and this place is a start-up, don't want to get fired.

2. They got me as a Sr PM (which was also my previous role where I excelled), so I fear that expectations would be high from me. Failing to deliver those might get me in trouble.

3. He isn't a micro manager and quite supportive, but his communication style isn't working for me (so far).

Somehow, as always, I am getting along well with everyone in the org and everyone is talking good about me.

But with my immediate boss, the imposter syndrome kicks in real hard and I am super insecure. Every time I have to interact with him, I get super stressed and anxious.

I know things take time, but given that I am a Sr PM (and my boss expects me to be a lead PM, a position higher than current), I feel if the expectations are not delivered then I might get fucked.

advantages of bionic systems:
- energy efficiency
- flexibility
- low friction
- compact size
- water resistance

advantages of mechanical systems:
- precision
- rotation is available
- scalability
- can change parts

!love(floating point)...

I displayed "score: 0" on the dashboard and on the review list, tester noted it as a bug stating; it should have been "score: 0.0" and not "score: 0" because the score is precision based.

You can say this is a half cup full and half cup empty scenario but I will call this silly cup full and brain cup empty!

If anyone has a moment.

curious if i'm fucking something up.

model:

self.linear_relu_stack = nn.Sequential(
nn.Linear(11, 13),
nn.ReLU(),
# nn.Linear(20, 20),
# nn.ReLU(),
nn.Linear(13,13),
nn.ReLU(),
nn.Linear(13,8),
nn.Sigmoid()
)

Inputs:

def __init__(self, targetx, targety, velocityx, velocityy, reloadtime, theta, phi, exitvelocity, maxtrackx, maxtracky,splashradius) -> None:

# map to 1 and 2
self.Target: XY = XY(targetx, targety)
# map to 3 and 4
self.TargetVel: XY = XY(velocityx, velocityy)
# TODO: this may never be necessary as targeting and firing is the primary objective
# map to 5, probably not yet needed may never be.
self.ReloadTime:float = reloadtime
# map to 6 and 7
self.TurretOrientation: Orientation = Orientation(theta, phi)
# map tp 8
self.MuzzleVelocity:float = exitvelocity
# map to 9 and 10, see i don't remember the outcome of this
# but i feel it should work. after countless bits of training data added.
# i can see how this would fuck up if exact values were off or there was a precision error
# maybe firing should be controlled by something else ?
self.MaxTrackSpeed: Orientation = Orientation(maxtrackx, maxtracky)

# these are for sigmoid output, any positive value of x will produce between 0.5 and 1.0 as return value
# from the sigmoid function.
self.OutMin = 0.5
self.OutMax = 1.0

# this is the number of meters radius that damage still occurs when a projectile lands.
# to be used for calculating where a hit will occur.
self.SplashRadius:float = splashradius

Outputs:
def __init__(self, firenow, clockwise,cclockwise,up,down,oor, hspeed, vspeed) -> None:
self.FireNow = float(firenow)
self.RotateClockWise = float(clockwise)
self.RotateCClockWise = float(cclockwise)
self.MoveUp = float(up)
self.Down = float(down)
self.OutOfRange = float(oor)
self.vspeed = float(vspeed)
self.hspeed = float(hspeed)

Anyone ever tried to fuck around with dynamic programming in machine learning?
My question is more towards rounding numbers.
Any papers on the impact of learning rate or precision that you guys know of?

*Begin rant*
I know I'm a bit late to bitch about this, but why would anyone in their right mind remove a UI/UX gesture that was loved and adored by millions and replace it with a far less intuitive gesture? I'm talking about Google's decision to fucking replace the Google Now swipe to dismiss cards gesture with a two stage tap and click to hide stories gesture! Why the fuck would you do that? The buttons are far too much of a precision action. And they are located at an area that is not natural for a single handed use. What this has effectively done is, force me to use my phone with two hands. And I fucking hate it! Can anyone here give me a valid reason for Google's design change? It's beginning to get on my nerves and my OCD compels me to hide all the cards until there is none left, so not minding it is not an option! Ughh!
*End rant*

Hi everyone,

Writing code is exercise in precision. Since there are programs like sublime text3 / emmet
Do you recommend to use those as they they generate the code?

I can't wait for the release of Snips Air sometime in 2019 so that I can stop using my Google home. It's not even the privacy concern that bugs me, it's the stupid shit like alarm management. To preface, I've had a Google home since late last year and since I got it the alarms have been nothing but trouble. More than half the time when I ask it when my next alarm is, it will respond with "You have an alarm for Friday at 7pm that is going off right now" (At the time of this response it was Tuesday). Then snoozing sometimes just doesn't work, I told it to snooze for 10 minutes, it worked just fine. Then today I made the mistake of asking it to snooze a second time which responded with "Sure, snoozing for 5 minutes", I wake up 45 minutes later, and ask "Hey Google, when's my next alarm?", it responds "You have an alarm today for 7:00 snoozed until 7:15". I have an exam today so luckily I didn't sleep in too late but againg this isn't the first occurence. To prevent this I normally just have a backup alarm on my phone and the one on my phone will wake me up in case something happens. On top of that though I've had rarer cases where it will delete all my alarms and I'll have to go command by command reminding of each alarm. That's just alarms though, I also have it control several IoT devices, and me having to use IFTTT requires the utmost precision in my phrasing otherwise it won't understand ( although this issue is mainly due to how the assistant service trigger on IFTTT is configured ). It still does much better than Siri ( at least my home can set alarms unlike my mac ), I have yet to try Alexa though. Of course my last problem is the hotword, saying "Hey Google" is much better than "Ok Google" but it's still excessive when I have to repeat it for each individual command. This is why I'm so excited for snips air, a set of devices that look pretty great, hackable, and as a bonus much more private that the current options. I realize that I could get a dev kit or set up snips on a pi but the dev kit isn't exactly visually appealing and I doubt I could get something that looks or functions half decent on the pi.

So the sigmoid function creates a limit of 1 as x approaches infinity meaning big high heapum activation value gets closer and closer to 1 ?

At a guess it only ever reaches 1 because of precision
Limitations ?

I'm just about throwing my new Dell laptop (Precision 5520) out of the window!

When I disconnect laptop from the thunderbolt dock (TB16), the laptop screen stays off until it's connected back to the dock. No matter if I put the laptop to sleep before disconnecting. Everything works just fine if I shutdown the machine and restart it without connecting to dock.

The best part is that the computer seems to be running normally, the screen is just black.

Anyone got a solution in mind? I'm running Windows 10 and I have installed all the possible updates.

Why do we still use floating-point numbers? Why not use fixed-point?

Floating-point has precision errors, and for some reason each language has a different level of error, despite all running on the same processor.

Fixed-point numbers don't have precision issues (unless you get way too big, but then you have another problem), and while they might be a bit slower, I don't think there is enough of a difference in speed to justify the (imho) stupid, continued use of floating-point numbers.

Did you know some (low power) processors don't have a floating-point processor? That effectively makes it pointless to use floating-point, it offers no advantage over fixed-point.

Please, use a type like Decimal, or suggest that your language of choice adds support for it, if it doesn't yet.

There's no need to suffer from floating-point accuracy issues.

So for a question on Codeforces, I got the basic logic right, but for one particular test case, the input is a huge number of 250 digits. But the most unsigned long long int can handle is 19 digits. So I used double instead of int, but that makes me lose precision. And I also cannot use the % operator (modulo) which is int only. How do I get around this ?

"Ensure precision and safety with our oil tank level measuring instrument. It accurately monitors and displays oil levels, preventing overflows and ensuring efficient operations.

So I remade a video today and the precision to which peoples nervous systems behave is ridiculous when it comes to reproducing willful actions when surrounded by other people recreating willful actions sigh

And here in thought I’d had a new idea
Oh well not this time
However does remind me the dirty slut bags fucked men over for no reason at all again

That I don't know it.

[The ambiguity is on purpose - actually that would hold for any computer language: that it will never have the flexibility, precision, metaphorical power, somnambulistic confidence in dealing with ambiguous constructs or meanings that natural languages have.]