Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
1. Do you know why my computer is so slow?
2. What cellphone do you recommend me to buy? (They always end up buying the cheapest)
3. What do you do at work? (Answer: "I create applications". Anything more complex than that is not going to be understood or they will loose interest)
4. Something is wrong with the: [TV, Cellphone, microwave, etc.]. Could you please take a look? (Believe or not, if something works with electricoty, my family thinks I can fix it).
5. Is it true that if I send this WhatsApp message to all my contacts I will have more options?
6. I need to build an application that (pretty much The Matrix), how much time do you need and how much would cost? Don't you dare to give me wrong numbers. (We have to see the future)
7. (Continuing the previous point, a non-technical client) I don't think that would take so much time/money. (Every time)
8. I want to use the latest Front-End frameworks. I want to see all those beautiful animations in my page and that it runs smoothly... I also need that it runs in IE 5.
9. So, you have been working in the back end? If you don't have a screen to show to the client is like you didn't do anything in this sprint.
10. Why haven't you built and million dollar application? Everybody is doing that right now....
Yep, those are only a few downsides of our profession if we count family, friends and even co-workers. But I can't imagine myself doing anything else.6 -
My favorite method?
Step 1: Meet Morpheus
Step 2: Swallow red pill
Step 3: Wake up from the Matrix
Step 4: Upload needed Knowledge directly to my brain
Step 5: Go back to Matrix4 -
Being a programmer in a scientific discipline can be infuriating.
using "no one" ="almost no one"
using everyone = "almost everyone"
1. No one knows what even the very idea of good practice is. And everyone refuses to learn. 3k lines of repetitive copy pasted main. 500 lines of plotting method.
2. Raw C-style pointer based array creation. Won't use develope array libraries because what if development stops. FUCKING HAVE YOU SEEN YOUR CODE WHAT IF DEVELOPMENT ON YOUR CODE STOPS. FUCK.
3. LOOP VARIABLES DECLARED AT THE BEGINNING OF THE METHOD WHY.
4. Everyone wants to make modular, independent code. No one wants to use OOP. NOPE. ALL IN ONE FILE. WRITE C++ LIKE A FUCKING PYTHON NOTEBOOK. FUCK.
5. LIBRARIES OH MY GOD PLEASE DO NOT CODE UP YOUR MATRIX MULTIPLICATION. PLEASE DO NOT TRIPLE LOOP IT. NO. THE LINEAR ALGEBRA LIBRARY WILL STAY IN DEVELOPMENT.
6. Please realize that literally not one comment over an 1800 line file does not help anyone.
FUCKING. WHY. WHY ARE WE SCIENTISTS SO GOOD AT SCIENCE AND SO FUCKING SHIT AT THE CODE THAT MAKES OUR SCIENCE HAPPEN. WHY. FUCKING. WHY. FUCK.4 -
Gender Bending For Fun and Profit.
I love how in the 'make your avatar' area, if you select female, and then click facial hair, theres nothing to select from.
Like a massive fuck you to every gender bending "down with meritocracy" purple haired dicksniffer in sanfran.
Also I'm sorely disappoint for desk items, theres no
1. giant dildos
2. anime figures/weeb shit
3. mini monoliths (I asked the site devs about this, they replied "we can't do that dave.")
4. a shirtless option for my female avatar
5. edgy scrolling numbers and code, like in the matrix
6. hoodies. They're the modern leather jacket.
7. Big nasty gnarly biker beard which I'm currently in the process of growing. How am I supposed to intimidate other anonymous cowards and mock them over the size of their beard compared to my own avatar's e-beard size? It's quiet girthy and lengthy, I assure you!
This is completely unrelated, but I thought devducks were like quick one-off debug sessions that could be bought from other devrant users.
I was disappointed when I discovered it was just merch.
On the otherhand I'm glad as fuck it's not. Site would be flooded by broken-english speaking goat humping dickheads.
How am I supposed to show off my ability to code with completely unrelated avatar change ups when no one will allow me to emasculate my avatar?16 -
I didn't leave, I just got busy working 60 hour weeks in between studying.
I found a new method called matrix decomposition (not the known method of the same name).
Premise is that you break a semiprime down into its component numbers and magnitudes, lets say 697 for example. It becomes 600, 90, and 7.
Then you break each of those down into their prime factorizations (with exponents).
So you get something like
>>> decon(697)
offset: 3, exp: [[Decimal('2'), Decimal('3')], [Decimal('3'), Decimal('1')], [Decimal('5'), Decimal('2')]]
offset: 2, exp: [[Decimal('2'), Decimal('1')], [Decimal('3'), Decimal('2')], [Decimal('5'), Decimal('1')]]
offset: 1, exp: [[Decimal('7'), Decimal('1')]]
And it turns out that in larger numbers there are distinct patterns that act as maps at each offset (or magnitude) of the product, mapping to the respective magnitudes and digits of the factors.
For example I can pretty reliably predict from a product, where the '8's are in its factors.
Apparently theres a whole host of rules like this.
So what I've done is gone an started writing an interpreter with some pseudo-assembly I defined. This has been ongoing for maybe a month, and I've had very little time to work on it in between at my job (which I'm about to be late for here if I don't start getting ready, lol).
Anyway, long and the short of it, the plan is to generate a large data set of primes and their products, and then write a rules engine to generate sets of my custom assembly language, and then fitness test and validate them, winnowing what doesn't work.
The end product should be a function that lets me map from the digits of a product to all the digits of its factors.
It technically already works, like I've printed out a ton of products and eyeballed patterns to derive custom rules, its just not the complete set yet. And instead of spending months or years doing that I'm just gonna finish the system to automatically derive them for me. The rules I found so far have tested out successfully every time, and whether or not the engine finds those will be the test case for if the broader system is viable, but everything looks legit.
I wouldn't have persued this except when I realized the production of semiprimes *must* be non-eularian (long story), it occured to me that there must be rich internal representations mapping products to factors, that we were simply missing.
I'll go into more details in a later post, maybe not today, because I'm working till close tonight (won't be back till 3 am), but after 4 1/2 years the work is bearing fruit.
Also, its good to see you all again. I fucking missed you guys.9 -
Taking a 4 month Software Engineering course in University. Spent the last 2 months making Traceability Matrix, Component Diagrams, Deployment Diagrams, Sequence Diagram and not a single line of code was written.
Is this how it works in Industry as well? Lol.12 -
Gotta make a decision matrix like the one in the picture. It's for a recommendation report concerning whether or not to distribute laptops to the CSCE students at my university and what kind of laptop if so.
I need help determining the weights for my matrix, because my personal preferences may not reflect the majority. As a programmer, how would you weigh the following three (very broad) categories?
Power(CPU, GPU, memory, HDD, I/O, etc..)
Quality (Durability, material, aesthetics, etc..)
Comfort(Weight, size, shape, keyboard, screen-eye comfort, OS familiarity, etc..)
Please write an integer 1-10 in the following format:
Power/Quality/Comfort ex: 7/4/9
Thanks, everyone!
-The Adderall'd-up devRant Noob, Benby
15 -
!dev
Matrix 4 trailer was such a shit show.
I don’t know why, but I honestly believed that it would not be as bad as it turned out to be. I’m such a stupid prick for believing in it.
FUCK YOU LANA WACHOWSKI. I HATE YOU AND EVERYONE RELATED TO THE PRODUCTION OF THIS CANCEROUS PIECE OF SHIT.12 -
Last year, we had computers architecture class where we study about the architecture of processors like RISC, CISC, SIMD... The teacher was a nice person but didn't have much knowledge on the field. I read some of Patterson&Hennessey book (computer organisation and design iirc) and learned how to use openmp and mpi, and then in the last lab we were required to optimize matrix multiplication using 4 threads in openmp, the best students optimiseed for 4 times at best, meanwhile I made 16 times optimisation and showed the teacher how fast it was. She was really impressed lol1
-
Okay then, ex-android user there.
It started with Xperia TX - it was flagship Sony phone back then. It blew my mind when I touched it for the first time. You know, exploring android for the first time in my life was amazing.
It ran just well for about a year. Then it started to fall apart. I need to clarify that I kept it non-rooted, full stock. I'm not into that customization things.
At first, I noticed significant lags. They were everywhere. The longer I used smartphone, the more lags I encountered. I did factory reset, but lags haven't gone anywhere.
Year 2. Front camera stopped working. Battery became unreliable as fuck, going down to 40% and then instantly to zero. What?
Year 3. Camera broke. It refused to start, just giving me "Camera is not available" error.
I tried factory reset again. It helped at first, but month have passed and all that issues came back. And it also became sluggish as fuck.
Got Meizu m3s year ago. The exact same story. Long story short, in one year I got this:
1. Black spots on every picture I take. Much likely a matrix issue.
2. Camera also became slow as fuck, requiring about 10 seconds to even start.
3. Vertical stripes all along the screen. I never dropped my phone, it just appeared once and became brighter and brighter every day I used the phone.
4. Two huge yellow spots on screen. I think it happened because phone's cpu heat up the screen and it broke.
But the most important thing is that fucking lags chased me in every app, they were everywhere. Fucking tiny-ass lags. And they're not going anywhere, they're become more and more significant with time.
Don't say me about oneplus, samsungs and other top android phones. They are conceptually the same, the only different thing is hardware.
That's why I switched. IPhone has its downsides, but it's silky smooth. And my friend's iPhone 4 (not s) feels just as smooth as my brand new se.
I'm not going to jailbreak it. I don't need customizing the hell out of it.
I just needed quick and reliable phone, and SE seems to be exactly what I wanted.
Peace to android folks tho✌️17 -
https://thechoiceisyours.whatisthematrix.com/...
Check your time when the video mentions the time.
Well executed.11 -
I just spent 2-3 hours writing a python script to make it easier to format solving system of equations through Gaussian elimination easier. It takes a matrix, then allows the user to perform row operations on it, and then it formats every operation done into LaTeX.
Alternatively, I could have spent that time actually working on the assignment it was meant to help me with, and probably finished 3/4 of it.1 -
So I promised a post after work last night, discussing the new factorization technique.
As before, I use a method called decon() that takes any number, like 697 for example, and first breaks it down into the respective digits and magnitudes.
697 becomes -> 600, 90, and 7.
It then factors *those* to give a decomposition matrix that looks something like the following when printed out:
offset: 3, exp: [[Decimal('2'), Decimal('3')], [Decimal('3'), Decimal('1')], [Decimal('5'), Decimal('2')]]
offset: 2, exp: [[Decimal('2'), Decimal('1')], [Decimal('3'), Decimal('2')], [Decimal('5'), Decimal('1')]]
offset: 1, exp: [[Decimal('7'), Decimal('1')]]
Each entry is a pair of numbers representing a prime base and an exponent.
Now the idea was that, in theory, at each magnitude of a product, we could actually search through the *range* of the product of these exponents.
So for offset three (600) here, we're looking at
2^3 * 3 ^ 1 * 5 ^ 2.
But actually we're searching
2^3 * 3 ^ 1 * 5 ^ 2.
2^3 * 3 ^ 1 * 5 ^ 1
2^3 * 3 ^ 1 * 5 ^ 0
2^3 * 3 ^ 0 * 5 ^ 2.
2^3 * 3 ^ 1 * 5 ^ 1
etc..
On the basis that whatever it generates may be the digits of another magnitude in one of our target product's factors.
And the first optimization or filter we can apply is to notice that assuming our factors pq=n,
and where p <= q, it will always be more efficient to search for the digits of p (because its under n^0.5 or the square root), than the larger factor q.
So by implication we can filter out any product of this exponent search that is greater than the square root of n.
Writing this code was a bit of a headache because I had to deal with potentially very large lists of bases and exponents, so I couldn't just use loops within loops.
Instead I resorted to writing a three state state machine that 'counted down' across these exponents, and it just works.
And now, in practice this doesn't immediately give us anything useful. And I had hoped this would at least give us *upperbounds* to start our search from, for any particular digit of a product's factors at a given magnitude. So the 12 digit (or pick a magnitude out of a hat) of an example product might give us an upperbound on the 2's exponent for that same digit in our lowest factor q of n.
It didn't work out that way. Sometimes there would be 'inversions', where the exponent of a factor on a magnitude of n, would be *lower* than the exponent of that factor on the same digit of q.
But when I started tearing into examples and generating test data I started to see certain patterns emerge, and immediately I found a way to not just pin down these inversions, but get *tight* bounds on the 2's exponents in the corresponding digit for our product's factor itself. It was like the complications I initially saw actually became a means to *tighten* the bounds.
For example, for one particular semiprime n=pq, this was some of the data:
n - offset: 6, exp: [[Decimal('2'), Decimal('5')], [Decimal('5'), Decimal('5')]]
q - offset: 6, exp: [[Decimal('2'), Decimal('6')], [Decimal('3'), Decimal('1')], [Decimal('5'), Decimal('5')]]
It's almost like the base 3 exponent in [n:7] gives away the presence of 3^1 in [q:6], even
though theres no subsequent presence of 3^n in [n:6] itself.
And I found this rule held each time I tested it.
Other rules, not so much, and other rules still would fail in the presence of yet other rules, almost like a giant switchboard.
I immediately realized the implications: rules had precedence, acted predictable when in isolated instances, and changed in specific instances in combination with other rules.
This was ripe for a decision tree generated through random search.
Another product n=pq, with mroe data
q(4)
offset: 4, exp: [[Decimal('2'), Decimal('4')], [Decimal('5'), Decimal('3')]]
n(4)
offset: 4, exp: [[Decimal('2'), Decimal('3')], [Decimal('3'), Decimal('2')], [Decimal('5'), Decimal('3')]]
Suggesting that a nontrivial base 3 exponent (**2 rather than **1) suggests the exponent on the 2 in the relevant
digit of [n], is one less than the same base 2 digital exponent at the same digit on [q]
And so it was clear from the get go that this approach held promise.
From there I discovered a bunch more rules and made some observations.
The bulk of the patterns, regardless of how large the product grows, should be present in the smaller bases (some bound of primes, say the first dozen), because the bulk of exponents for the factorization of any magnitude of a number, overwhelming lean heavily in the lower prime bases.
It was if the entire vulnerability was hiding in plain sight for four+ years, and we'd been approaching factorization all wrong from the beginning, by trying to factor a number, and all its digits at all its magnitudes, all at once, when like addition or multiplication, factorization could be done piecemeal if we knew the patterns to look for.7 -
1. Come home from matrix job at 5pm
2. Eat 45 mins
3. Take a break 15 mins for brain to breathe
4. Now its 6pm
5. Blink
6. Now its 10pm and time for bed to continue slaving my life to matrix job
6 -
Working in an expanding business is mostly fun, can be kind of challenging (for those who don't like to step in and do what's needed). One thing in particular you need to do a lot - is interviews. Lot's of them.
There are alsways two sides of the coin, for sure. But, just a little tip/hint to everyone looking for a job - please, please, please make sure your CV and letter at least makes sense for the position you're trying to get.
This (screenshot) is just one example of things in a CV which really makes me want to shout and kick people out.
It's part of the front page of a CV, for someone who is looking for a position as front-end developer / UX specialist. This person claims to be very interested in UX, and has done wome work already in this field.
Can ANYONE explain to med WHAT THE F*CK this actually means?
1) How many stars can a row have? 10, 6, 8?
2) What does it mean to have 4 starss in PHP knowledge? What's lacking to get 5?
3) What's the scale based on, at all?
And you want me to hire to to do UX of loyalty communication (e-mail, mobile apps, websites/landing pages) for our customers - who in turn have millions of customers/prospects?!?
ARE YOU F*CKING KIDDING ME?
If you can't even make a visualization of your _own_ knowledge which can be interpreted into some sort of competence matrix, but you just use something you think looks cool... Damn, you could at least have tried.
1 -
!rant
Electronics
Just got a pack of 50 ULN2003A (for 4€).
https://en.wikipedia.org/wiki/...
Any Ideas?
I want to do a led matrix with them... But can't find tutorials online, help?2 -
you might have watched The Matrix 1, 2,3 & 4 how do you feel the concept and the story to be applied to our existing life?16
Top Tags
Weekly Rant
View