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
Search - "uniform"
-
Oh boy its actually embarassing...
I was in a cosplay event, when I realized I only have 30 minutes till I check in for my first day in the job as a support agent.
I never had the time to change because of traffic and I was commuting so I spent the next 9 hours in side the company premises wearing a japanese schoolgirl uniform.
...I got quite everyone's attention, even the HR... ( well at least the HR just reprimanded me about that >_<)
Note to self: remember to give yourself 30 minutes more of allowance....31 -
Trying to explain to my 6 year old daughter why she has to wear school uniform and why mummy has to wear a work uniform, yet I work in jeans and at shirt7
-
Laravel is the worst framework ever.
Everything has to be made convenient and easy. That sounds amazing, because developers want to save time, worry less about boilerplate code, right? No more constructors, no more dependency injection, fuck all the tedious OOP shit... RIGHT?
It does one thing well: Make PHP syntax uniform and concise through easily integrated libraries such as Collection and Carbon. But those are actually not really part of the framework... just commonly integrated and associated with Laravel.
The framework itself is completely derailed: You can define code in a callback in the routes file. You can define a controller in the routes file. You can define middleware as a parameter to the route, as a fluent method to the route, you can stack them up in a service provider. Validators can be made in controllers, Request objects, service providers, etc. You can send mail inline, through Mailable objects, through Notification objects, etc.
Everything is macroable, injectable, and definable in a million different places. Ultimate freedom!
Guess what happens when you give 50 developers of various seniority a swiss army knife?
One hammers in a screw with a nail file, the other clips the head from the screw using scissors, and you end up with an unworkable mess and blunt tools.
And don't get me started about Eloquent, the Active Record ORM. It's cute for the simple blog/article/author/comment queries, but starts choking when you want more selective and performant queries or more complex aggregates, and provides such an opaque apple-esque interface which lets people think everything is OK, when in reality it's forcing the SQL server to slowly commit suicide.50 -
Why is the contributing manual of your open source project more thoughtfully cultivated than your code style guide and testing procedure?
Why the fuck do you care about the message in my PR, or even merge vs rebase of commits, when your spaghetti-tomatosource is so richly saturated with critically minced bugmeat?
Why are you standing there, shouting at me about your convoluted rules, in your little brown uniform? Why do I feel like the enemy when I contribute a useful fix, something which makes the code work better?
You know what, fuck all of you, you jilted acetous neckbeards, I will deploy my secret weapon, I will bypass the power you hold over your tiny fascist digital dominions.
If you play it like this, I will summon the nefarious vile side of Open Source. I will usurp your throne. I will stab out your crying eyes, rip out your conceited tongue, impale your lonely heart.
Tremble before me! I wield the almighty, legendary Fork!
The king is dead, long live the king!5 -
I'm hereby quitting as a dev and decide to become a maid in a maid cafe cos I just witnessed someone break my code with their hacky fix
seriously, fuck him. Now excuse me, I gotta don a maid uniform and chant cute noises3 -
The facial hair devRant provides in it's profile builder are either well maintained thick growth of beard or a neatly trimmed uniform beard.
And here I am with my abomination of a beard that looks like a herd of cattle trampled over a sparse field of grass.
The struggle is real.7 -
And once again:
18:00: *writing a Mandelbrot algo in glsl for the GPU*
19:00: "This should be working now..."
22:00: "why isn't it working??!"
22:30: "Oh my uniform vectors become zero when they arrive on the GPU"
01:00: "Oh. I uploaded them as matrices..."
I wasted about 4 fucking hours because I suck dick.5 -
Not really a fired moment because it was a university project.
A colleague of mine decided it'd be nice to set placeholder images to Hitler wearing a hello Kitty Nazi uniform. Oh without telling anyone, of course.
I go into the lab that a couple lecturers share, one of them was interested in the project we were working on and to our surprise the placeholder images pop up. I immediately say sorry, I didn't set that image and the guy looks at me with judging eyes.
Same guy has to take meds daily otherwise he acts up, not sure what it was he had, may have been ADHD, anyways we were staying late and he forgot his meds, and while our client is in the same room this guy starts doing the macarana behind the room separator, while we're supposed to give him a live preview of what we had accomplished in three months of work. Needless to say he didn't see him dancing like a moron but wow :/ learn to control yourself.
Same guy also never commented his code and used the two letter variable principal because it's such a great idea >.> Me and the other guy spent 6 hours rewriting his code, which should have been less time but he wasn't there to help nor was he available to yell.. I mean ask for help.
I hate University group projects....2 -
Found a Gameboy mostly-buried on the side of the interstate. Hadn't been long as it's uniform color and part of it was unburied, but it works, so i'm keeping it. Who the fuck takes the time to bury a DMG next to an interstate and why???14
-
During a code review I was told that
if(x and y){
if(z){}
}
Will be slower to run than
if(x and y and z){}
I mean if you want to talk about programming practices and uniform code yes absolutely but any compiler will treat these identically, not to mention the assembly being identical. She was a superior though so I just went along with it.10 -
Men in plaid: Look like programmers.
Me in plaid: Look like farmer.
I hate fashion. I hate picking out clothing. Where is my easy uniform-thats-not-actually-a-uniform? The men folk don't have to spend brain cells devoted to clothing, if they don't want, and still look sufficiently appropriate. Whereas I'm sitting here on a Friday night, wondering what precautions need to be made before washing a professional shirt which is for some reason bedecked with rhinestones.17 -
I wonder how come we don't have a developers' "uniform" in the avatar builder's "shirt" list...
developer's uniform == hoodie14 -
Not sure if it's the worst code review but it's a recent one.
We don't really do code reviews where I work unfortunately but my coworker used my framework for the first time (build some nice composer libraries for cmdline projects) and asked if I could make them do autoloading.
He never used namespaces before so I was glad to help him out.
What I saw was a dreadful mess. His project was called "scripts" so good luck picking a namespace...
Than it was all lose functions in the executable file. All those functions are however called by a class in another file (if they where not calling eachother as a cascading mess). That class was extending an abstract class from my library as instructed. However I never imagined my lib being raped like that.
The functions themselves are a horrible mess. Nothing uniform completely different style (our documentation states PSR's should be used).
Parameters counts higher than 5.
Variable names like Object and Dobject (in calling function Dobject is Object but it needs a fresh one.
If statements on parameters that need basically split it in two (should simply be to functions)
If else statement with return of same variable as a single line (sane people use ternary for that)
Note that I said functions. All of it should have been OO and methods. Would have saved at least some of the parameter hell.
I could go on and on. Do I think the programmer is bad yes (does not even grasp interfaces, dep injection, foreach loops). Is this his best work no. He said that for a one of script like this it just has to work. Not going to be used elsewhere. I disagree as it is a few thousand lines of code that others have to read too.2 -
The problem with Windows Store apps is that they are not uniform. They are all layed out differently from each other. Their navigation sucks. They use too much mystery meat icons. Some waste space. The interface is like zoomed in. Just my personal opinion though.2
-
After listening to the deadmau5 plane crash story on h3h3 this exact thought play went on in my mind.
The universe wants to be uniform. Everything is the same, nothing reacts anymore.
Humans like the complete opposite. We like complexity and entropy. We create and we destroy.
But we are part of the universe.
So if you break this down into absolute math statements, they are contradicting.
So are we breaking the equasion?
Or are we part of the equasion?
...Are we the universe's self made antidote to itself?2 -
"What is going on... this should work?!
Is my maths wrong?
My maths is wrong...
Oh no!
It's a model view projection matrix?!
I'm shit if I'm failing at this, it's 3D dev 101!
I got a first class degree... I don't deserve any of this or this job!!"
<2 seconds later>
uniforms.viewMatrix.set(camera.matrixWorldInverse.elements);
uniforms.viewMatrix.set(camera.projectionMatrix.elements);
"You set the same uniform twice you tool, due to copy and paste..."
Imposter syndrome in my early days put myself into a roller coaster of emotions. I always compared myself to others to the detriment of myself.
Thankfully overcame that working with some great guys.
But yeah, coding has impacted life for the best though. The challenge, creativity and constant learning is beautiful. -
Can we please normalise using JSON bodies for GET requests? Makes life way more easy to just have one uniform way to communicate with API's and having different parameter formats between GET and POST request. I mean, In my opinion it is not logical to do one request with query params and others with data in the request body6
-
Heres some research into a new LLM architecture I recently built and have had actual success with.
The idea is simple, you do the standard thing of generating random vectors for your dictionary of tokens, we'll call these numbers your 'weights'. Then, for whatever sentence you want to use as input, you generate a context embedding by looking up those tokens, and putting them into a list.
Next, you do the same for the output you want to map to, lets call it the decoder embedding.
You then loop, and generate a 'noise embedding', for each vector or individual token in the context embedding, you then subtract that token's noise value from that token's embedding value or specific weight.
You find the weight index in the weight dictionary (one entry per word or token in your token dictionary) thats closest to this embedding. You use a version of cuckoo hashing where similar values are stored near each other, and the canonical weight values are actually the key of each key:value pair in your token dictionary. When doing this you align all random numbered keys in the dictionary (a uniform sample from 0 to 1), and look at hamming distance between the context embedding+noise embedding (called the encoder embedding) versus the canonical keys, with each digit from left to right being penalized by some factor f (because numbers further left are larger magnitudes), and then penalize or reward based on the numeric closeness of any given individual digit of the encoder embedding at the same index of any given weight i.
You then substitute the canonical weight in place of this encoder embedding, look up that weights index in my earliest version, and then use that index to lookup the word|token in the token dictionary and compare it to the word at the current index of the training output to match against.
Of course by switching to the hash version the lookup is significantly faster, but I digress.
That introduces a problem.
If each input token matches one output token how do we get variable length outputs, how do we do n-to-m mappings of input and output?
One of the things I explored was using pseudo-markovian processes, where theres one node, A, with two links to itself, B, and C.
B is a transition matrix, and A holds its own state. At any given timestep, A may use either the default transition matrix (training data encoder embeddings) with B, or it may generate new ones, using C and a context window of A's prior states.
C can be used to modify A, or it can be used to as a noise embedding to modify B.
A can take on the state of both A and C or A and B. In fact we do both, and measure which is closest to the correct output during training.
What this *doesn't* do is give us variable length encodings or decodings.
So I thought a while and said, if we're using noise embeddings, why can't we use multiple?
And if we're doing multiple, what if we used a middle layer, lets call it the 'key', and took its mean
over *many* training examples, and used it to map from the variance of an input (query) to the variance and mean of
a training or inference output (value).
But how does that tell us when to stop or continue generating tokens for the output?
Posted on pastebin if you want to read the whole thing (DR wouldn't post for some reason).
In any case I wasn't sure if I was dreaming or if I was off in left field, so I went and built the damn thing, the autoencoder part, wasn't even sure I could, but I did, and it just works. I'm still scratching my head.
https://pastebin.com/xAHRhmfH33 -
How do you all dress in the workplace? Do you wear a uniform (similar clothes daily) or dress up? I think devs should never have to dress up to work but maybe that is just my weird opinion.13
-
Well, been awhile. The latter half of this is probably gonna be unpopular, but the gist of it is that all of the devs working on camera-centric apps, get your shit together, if possible. As mentioned there may not be a way for you to get your shit together, because Google and the others involved ultimately are a mess. In that case, you're dismissed. I haven't proof-read this, so don't take it exactly verbatim.
Woke up this morning to a need for this, so here goes:
----
OPEN LETTER TO SNAPCHAT
----
Snapchat,
You guys need to get your shit together. This is a tack-on to what Marques Brownlee already stated.
I woke up this morning to a seriously FUCKED UP UI. UX didn't change as much, still looks Snapchat-esque. But holy hell WHAT THE FUCK?
I'm not averse to change, despite the above. HOWEVER, there's an exception to that: You cannot change out UX/UI from under me with no warning. I need to know that within the coming weeks, there will be changes to how I interact/interface within the app. An option to opt into testing would be nice as well, but doesn't look like you guys have that figured out. With that testing should come feedback, and something like Jira, where issues can be reported and triaged. You're a company, unfortunately, so I doubt you'd be willing to even go as far as accepting feedback in the first place, which is a shame.
Seriously, as Marques pointed out, Android Snaps are shitty because the app takes a screenshot of the viewfinder and uses it as a photo. There's no doubt in my mind this is something that others do, but all Android devs need to either not pull this (because it's not clever) or just not make apps (quality over quantity).
I would like to see either Google step in and require a native API that is the same across all devices and leverages all cameras to their full potential (I want to say that Snap's issue stems from an API provided by Google. In this case, Google, get your shit together), or alternatively I'd like to see manufacturers band up to provide a uniform interface to deal with this. Because I don't see the latter happening anytime soon, Google needs to do something about this, although I feel like they probably won't. That said, IDGAF WHO it is, I just want it FIXED. -
The most noble outfit one can wear, that is above every royal mantle in history, is the medical uniform.1
-
[!dev], [toasters]
Does everyone only ever toast perfectly uniform slices of bread?
My grandma has a toaster that has two doors which open to the side and are held closed by a spring. This way if a slice is too thick the door can't close properly, but the damn thing still works. It's from before ww2, like most dead simple devices that work surprisingly well. I can't find anything similar anymore. The only two types now are the top-loaded design that simply doesn't work with thick slices, and the version for Americans or families of twelve that is the form factor of a smaller oven. (Which I obviously don't have room for. I already have an oven.)
Btw, how should I tag this? It's a rant, but it has nothing to do with the platform except perhaps the undocumented dependency between toasters and bread slicing machines.7 -
My friend just meant he wants a uniform Drag and Drop on all Linux Distributions.
Also in the terminal...2 -
Many of my friends used to commit unnecessarily just to increase their commits and fill the contribution graph. To remove that shit, I wrote a Chrome extension that would make your contribution graph uniform!
Link to the repo: https://github.com/ashwini0529/...2 -
One time while enjoying the Halloween festivities I was kidnapped.
What happened was this, in my brilliant genuine way of thinking, put on a Stormtrooper costume and stood outside the front door like a model statuesque persona to frighten the living daylights out of the trick or treat gremlins, Doing such an amazing job as usual, pretending in my head that I was invisible for about an hour scaring the life out of everyone when for brief moments to break character.
Along came a car, it backed up to the ground I fought hard to gain that night, as a problem solving professional I remained silent and still as two assailants proceeded to place me into the back seat of their car.
Now ladies look away. When they were discussing what I was worth they actually didn't expect me to sit up in the back seat and say "donde esta la biblioteca". I was wearing a Deadpool outfit under my Stormtrooper uniform the whole time and I got to beat up some bad guys, so this is a really nice fuzzy carebare story with a happy ending.3 -
Me: hey, I noticed we are doing this weird stuff in 'platform A' can we file a story to fix this.
Dev: It must be legacy code or library implementation before my time. By the way it's the same in platform B.
Me: yeah, we will need to fix that too.
Dev: tell you what. For now let's keep our platforms uniform we will fix it when platform B is fixed.
Welcome everyone... to the new chicken egg problem. Where even bugs are needed to be uniform across platforms.1 -
Does anyone have any ideas on how to decrease latency of audio multicast via pulseaudio?
Currently having a non uniform latency of 1-10 seconds
This is in case of local network6 -
I have this weird problem when I try to call a shell command with python. I'm trying make a path o linux with forward slashes but once the string gets built it either has no forward slashes or too many or non-uniform slashes across the whole path. This is so frustrating. Eventually the path doesn't get recognized at all.
-
I need help structuring a new TypeScript project built on a MERN stack. I used CRA for the client, so I opted to have separate tsconfig files -- one for client (auto-generated by CRA) and one for server (extends node12 tsconfig). However, I'm trying to setup eslint and prettier globally so that the lint/style rules are uniform across the codebase. CRA adds an eslint config that extends react-app, which is fine, but I'd like to still have my global rules. I have written my eslintrc.json file and am happy with it, so I placed it in the project root directory. I figured I would install eslint, prettier, etc. in the project root, then when I run eslint globally, it would lint the server code with the global rules and the client code with the global rules and the react-scripts rules.
However, react-scripts complains that I've installed a newer version of eslint in a parent directory. I can either ignore that rule or use the same version as react-scripts, but it seems like react-scripts is going to run eslint on its own when I run npm start, regardless of if I have a global config. What should I do? Is there a better way to structure the app?1