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
-
Working really hard, finishing tasks, upgrading servers. Cancel some useless meetings to finish up features, working till 2am to get a database migration working. Half of the platform is transformed, both customers and team are very happy about their accomplishments.
Boss: "OK, I think we're on the right path with these changes, but productivity and morale is honestly disappointing. Are you guys sleeping enough? You all look very tired and unmotivated!"
Attend all meetings, call boss at 7am to discuss random purchases like a whiteboard, run around the office holding a (broken, lol) MacBook, looking very busy & slightly worried. I shout random things at people across the office like "Nice work Gary!" and "Damn, you are on a roll Angela!". I initiate smalltalk with department heads, only to immediately disrupt the conversation by checking my phone saying "Oh I really have to take this one" (empty battery, lol). No one writes a single line of code for four weeks, and nothing new has been deployed by the whole team.
Boss: "I think it's commendable how productive the team has become this month. You guys are all so active and involved. A real improvement!"6 -
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".
6 -
Boys and girls. Never work as a Udacity mentor to get some extra pocket money. NEVER EVER! They are absolute rubbish. It is sad to see the platform that I once loved get transformed from an extremely cool thing into this crap.
There will be a rant or a series of rants in the future about this.9 -
EoS1: This is the continuation of my previous rant, "The Ballad of The Six Witchers and The Undocumented Java Tool". Catch the first part here: https://devrant.com/rants/5009817/...
The Undocumented Java Tool, created by Those Who Came Before to fight the great battles of the past, is a swift beast. It reaches systems unknown and impacts many processes, unbeknownst even to said processes' masters. All from within it's lair, a foggy Windows Server swamp of moldy data streams and boggy flows.
One of The Six Witchers, the Wild One, scouted ahead to map the input and output data streams of the Unmapped Data Swamp. Accompanied only by his animal familiars, NetCat and WireShark.
Two others, bold and adventurous, raised their decompiling blades against the Undocumented Java Tool beast itself, to uncover it's data processing secrets.
Another of the witchers, of dark complexion and smooth speak, followed the data upstream to find where the fuck the limited excel sheets that feeds The Beast comes from, since it's handlers only know that "every other day a new one appears on this shared active directory location". WTF do people often have NPC-levels of unawareness about their own fucking jobs?!?!
The other witchers left to tend to the Burn-Rate Bonfire, for The Sprint is dark and full of terrors, and some bigwigs always manage to shoehorn their whims/unrelated stories into a otherwise lean sprint.
At the dawn of the new year, the witchers reconvened. "The Beast breathes a currency conversion API" - said The Wild One - "And it's claws and fangs strike mostly at two independent JIRA clusters, sometimes upserting issues. It uses a company-deprecated API to send emails. We're in deep shit."
"I've found The Source of Fucking Excel Sheets" - said the smooth witcher - "It is The Temple of Cash-Flow, where the priests weave the Tapestry of Transactions. Our Fucking Excel Sheets are but a snapshot of the latest updates on the balance of some billing accounts. I spoke with one of the priestesses, and she told me that The Oracle (DB) would be able to provide us with The Data directly, if we were to learn the way of the ODBC and the Query"
"We stroke at the beast" - said the bold and adventurous witchers, now deserving of the bragging rights to be called The Butchers of Jarfile - "It is actually fewer than twenty classes and modules. Most are API-drivers. And less than 40% of the code is ever even fucking used! We found fucking JIRA API tokens and URIs hard-coded. And it is all synchronous and monolithic - no wonder it takes almost 20 hours to run a single fucking excel sheet".
Together, the witchers figured out that each new billing account were morphed by The Beast into a new JIRA issue, if none was open yet for it. Transactions were used to update the outstanding balance on the issues regarding the billing accounts. The currency conversion API was used too often, and it's purpose was only to give a rough estimate of the total balance in each Jira issue in USD, since each issue could have transactions in several currencies. The Beast would consume the Excel sheet, do some cryptic transformations on it, and for each resulting line access the currency API and upsert a JIRA issue. The secrets of those transformations were still hidden from the witchers. When and why would The Beast send emails, was still a mistery.
As the Witchers Council approached an end and all were armed with knowledge and information, they decided on the next steps.
The Wild Witcher, known in every tavern in the land and by the sea, would create a connector to The Red Port of Redis, where every currency conversion is already updated by other processes and can be quickly retrieved inside the VPC. The Greenhorn Witcher is to follow him and build an offline process to update balances in JIRA issues.
The Butchers of Jarfile were to build The Juggler, an automation that should be able to receive a parquet file with an insertion plan and asynchronously update the JIRA API with scores of concurrent requests.
The Smooth Witcher, proud of his new lead, was to build The Oracle Watch, an order that would guard the Oracle (DB) at the Temple of Cash-Flow and report every qualifying transaction to parquet files in AWS S3. The Data would then be pushed to cross The Event Bridge into The Cluster of Sparks and Storms.
This Witcher Who Writes is to ride the Elephant of Hadoop into The Cluster of Sparks an Storms, to weave the signs of Map and Reduce and with speed and precision transform The Data into The Insertion Plan.
However, how exactly is The Data to be transformed is not yet known.
Will the Witchers be able to build The Data's New Path? Will they figure out the mysterious transformation? Will they discover the Undocumented Java Tool's secrets on notifying customers and aggregating data?
This story is still afoot. Only the future will tell, and I will keep you posted.6 -
Coding while listening to piano music makes me feel like a pianist who use 'keyboard' for performance. ( However, the next one in my music list is techno music and I transformed to a DJ hhayaa!4
-
So I took my old C# project "RotatingCube" for a spin and transformed the unreadable and inefficient mess into a different program, featuring better readability and more comments, with multiple cubes at once, without the shitty flickering.
I did that for school but it was quite fun to tinker with only outputting the differences to a previous output.
Check it out at https://github.com/filthycoding/...!
Next I just need multithreading for performance reasons. -
I am thinking about leaving this platform. To be honest I don't get anything out of it anymore and the only thing keeping me here is the less-rant'ish content like @devNews or the stories.
I am actually a bit disappointed, the quality of devrant really did degrade alot in the last few months. Don't get me wrong but I feel like people have become "normies" over here. I don't mean that in an edgy or degrading way but let me explain. When I started here I had a very high opinion of the people here. Everyone seemed like a passionate / knowledgeable individual from whom you could hear interesting stories or learn. Maybe I just saw it like that because I was still a very inexperienced dev and was looking for a dev community. But nonetheless I think devRant transformed into a place of mediocrity.
Dont get me wrong I wouldn't think of myself as aspiring or generally "better" than anyone else on here, but the content over here got a little stale.
I am not the kind of person who would "rant", in the first place, so I may have a different mindset and to be honest "ranting" has always been a thing I looked down upon. It just does not support my style of thinking. I totally get that people sometimes need to "vent" their feelings but there is nothing productive to gain from ranting, like you ain't not improving your situation by doing it. The more passionate raters over here call people things, I would never even dream about saying to people. Don't worry I'm no sjw or something like it, I don't care if you do it. If it helps you sure, why not. But there is a point where you corner yourself so much that you stop respecting your colleagues because they wrote that shitty code, instead of helping.
Some tech sure is bad, but it is not getting any better by insulting it.
Another thing I use to notice are people, thinking so highly of them selfes / being so close-minded - that they only accept their own views as true. These are the people that I always try to avoid, but that is getting harder and harder as time goes on.
Collectivism and group thinking are very strong on devRant making it really hard to defend a unpopular opinion - I get that devRant is not the kind of platform that would support actual proper arguments/discussions - but I still feels like some people shove opinions down another people's throat with no reasoning behind it.
Arguments on devRant are always won by the person coming up with the most witty response. Having another opinion is always seen as offensive. That's not exactly the definiton of open-mindedness.
Another rather annoying thing are what I call the "non dev, dev's". See: As a developer you should aspire to understand what your doing - I won't get into this too much but one sentencd: How are things like serious "Semicolon memes" a thing? I am as much into memes as the next guy, but debugging 3 hours, just to find out its a typo. I mean come on...
I sure get that devRant is not the kind of place where you would find the people I am looking for, and that's why I am leaving.
My whole post may seem super negative of the platform - and it is to an extend - but I sure also had a good time back in the day - devRant as in "the platform" surely is not at fault, but a forum is only as good as the people on it. Maybe I changed, maybe devRant did. All I know is that it is not for me anymore.
I won't delete my account and I probably will not leave completely, but all I will do is the "once a week" checkout.6 -
Caffeine meets every criteria for being a drug:
- Alters mental state
- Addictive
- Has withdrawal symptoms
- Tolerance increases with time
If you rely on caffeine to function, statistically, you spend the majority of your waking life in caffeine crush, longing for more and more caffeine to just function normally.
Face it: you’re a drug addict. Caffeine being legal doesn’t mean it’s not a drug.
I don’t do caffeine at all. I don’t drink sodas that have caffeine, I don’t drink tea either. That’s why I’m always full of energy. Yes, caffeine withdrawal gave me a week of terrible headaches, but I pushed through, and now my life is completely transformed.36 -
This is the third part of my ongoing series "The Ballad of the Six Witchers and the Undocumented Java Tool".
In this part, we have the massive Battle of Sparks and Storms.
The first part is here: https://devrant.com/rants/5009817/...
The second part is here: https://devrant.com/rants/5054467/...
Over the last couple sprints and then some, The Witcher Who Writes and the Butchers of Jarfile had studied the decompiled guts of the Undocumented Java Beast and finally derived (most of) the process by which the data was transformed. They even built a model to replicate the results in small scale.
But when such process was presented to the Priests of Accounting at the Temple of Cash-Flow, chaos ensued.
This cannot be! - cried the priests - You must be wrong!
Wrong, the Witchers were not. In every single test case the Priests of Accounting threw at the Witchers, their model predicted perfectly what would be registered by the Undocumented Java Tool at the very end.
It was not the Witchers. The process was corrupted at its essence.
The Witchers reconvened at their fortress of Sprint. In the dark room of Standup, the leader of their order, wise beyond his years (and there were plenty of those), in a deep and solemn voice, there declared:
"Guys, we must not fuck this up." (actual quote)
For the leader of the witchers had just returned from a war council at the capitol of the province. There, heading a table boarding the Archpriest of Accounting, the Augur of Economics, the Marketing Spymaster and Admiral of the Fleet, was the Ciefoh Seat himself.
They had heard rumors about the Order of the Witchers' battles and operations. They wanted to know more.
It was quiet that night in the flat and cloudy plains of Cluster of Sparks and Storms. The Ciefoh Seat had ordered the thunder to stay silent, so that the forces of whole cluster would be available for the Witchers.
The cluster had solid ground for Hive and Parquet turf, and extended from the Connection River to farther than the horizon.
The Witcher Who Writes, seated high atop his war-elephant, looked at the massive battle formations behind.
The frontline were all war-elephants of Hadoop, their mahouts the Witchers themselves.
For the right flank, the Red Port of Redis had sent their best connectors - currency conversions would happen by the hundreds, instantly and always updated.
The left flank had the first and second army of Coroutine Jugglers, trained by the Witchers. Their swift catapults would be able to move data to and from the JIRA cities. No data point will be left behind.
At the center were thousands of Sparks mounting their RDD warhorses. Organized in formations designed by the Witchers and the Priestesses of Accounting, those armoured and strong units were native to this cloudy landscape. This was their home, and they were ready to defend it.
For the enemy could be seen in the horizon.
There were terabytes of data crossing the Stony Event Bridge. Hundreds of millions of datapoints, eager to flood the memory of every system and devour the processing time of every node on sight.
For the Ciefoh Seat, in his fury about the wrong calculations of the processes of the past, had ruled that the Witchers would not simply reshape the data from now on.
The Witchers were to process the entire historical ledger of transactions. And be done before the end of the month.
The metrics rumbled under the weight of terabytes of data crossing the Event Bridge. With fire in their eyes, the war-elephants in the frontline advanced.
Hundreds of data points would be impaled by their tusks and trampled by their feet, pressed into the parquet and hive grounds. But hundreds more would take their place. There were too many data points for the Hadoop war-elephants alone.
But the dawn will come.
When the night seemed darker, the Witchers heard a thunder, and the skies turned red. The Sparks were on the move.
Riding into the parquet and hive turf, impaling scores of data points with their long SIMD lances and chopping data off with their Scala swords, the Sparks burned through the enemy like fire.
The second line of the sparks would pick data off to be sent by the Coroutine Jugglers to JIRA. That would provoke even more data to cross the Event Bridge, but the third line of Sparks were ready for it - those data would be pierced by the rounds provided by the Red Port of Redis, and sent back to JIRA - for good.
They fought for six days and six nights, taking turns so that the battles would not stop. And then, silence. The day was won, all the data crushed into hive and parquet.
Short-lived was the relief. The Witchers knew that the enemy in combat is but a shadow of the troubles that approach. Politics and greed and grudge are all next in line. Are the Witchers heroes or marauders? The aftermath is to come, and I will keep you posted.4 -
So, the GUI is built by writing YANG files that are then transformed into protobufs and jsons. Protobufs are then digested by GWT to compile java into javascript and HTML. What part of the process you don't understand?
Wait, I actually don't exactly know where the jsons end up being used, but apparently they are being sent by C++ backend to GWT frontend. Somehow.12 -
Well done Microsoft
You’ve transformed a product MS Excel from something great into something unusable ..endlessly over designing it with needless fucking icons everywhere…
Just leave it THE FUCK ALONE from 20078 -
What the actual fuck GitHub/CircleCI?!??
I transformed a GitHub account into an organisation and lost admin access to a repo even though I'm the owner of the organisation. Now I can't even access the settings for the repo on CircleCI. What the hell? WHAT THE HELL?!!?! THE FUKKKKKKKKKKKk? -
Not really a rant but more of a fact kinda thing. Noticed a post earlier about someone ranting about why they code figured I'd do the same...
I code not because I wanted to for say but because my after my uncle's death I needed something that I could feel in complete control of. Coding gave me that ability to control the computer however I want and tell it to do whatever however. At the same time it taught me so much more about myself and the people around me in the process. Today I don't code because I need to control something m today I do it because I can't live with out. It forces me to think critically of everything and everyone. It forces me to learn something new everyday and every night. It requires me to solve complex problems with limited solutions. It allows me to create solutions when everything else has failed and it gives me a drive to complete things. It's the reason I live technology and it's the reason I have the job I do. It's the reason my boss loves my work and it's the reason other people on my team envy me. Code transformed my life into what it is today. And it will forever be my greatest peice of education.1 -
Adobe's ExtendScript toolkit is abyssmal. I find posts from 2008 referring to issues that have not changed even in CC2017. Do you think they are small issues I'm bitching about? I'll list 2. First, the toolkit only colours "var, return, for, foreach" and a bit more keywords and the strings, of course you can set up color schemes but those are limited and not colouring stuff. The second issue is auto-complete, it rarely kicks in and suggestions have 0 connection to what are you doing and are always the same. It doesn't recognize anything of what are you doing.
Probably in 2008 you had to program with the manual near you like writing assembler, now there's an improvement in 2017, they got a window named object browser or something like that that actually is a summarised portable manual that could've been easily transformed in auto-complete suggestions.
Adobe writes about this and I quote: "a complete integrated development environment". Although I will not write much scripts in it, I need to write a big one and thought about extracting that object data and putting it in a more capable javascript editor. LO and Behold what I discovered, the ExtendScript Toolkit that's supposed to edit Extended javascript and save it as jsx or jsxbin is almost completely (it has some dlls too) built using around 100 jsx files. It's the equivalent of building a js IDE to edit js.
Sorry for formatting, I'm on mobile, I tried.
-
Hopefully, you already know that the company controlled by the alledged reptiloid subhuman and olimpic testicle juggler formerly known as Mister Zuck My Tits is not to be trusted.
But as is always the case in this bitch, I've been forced into cowjizz flooded swamps' worth of stinking shit platforms for the sake of avoiding isolation.
And so, I've just found yet another way in which Facebook **THUNDERSTRIKE** ... the company, not the geriatric ward, is one of the CROWN ACHIEVEMENTS of human civilization.
Let me tell you something: some people are fucking broke. Hell, some people sleep on the streets, live on scraps, and willingly engage in acts of public defecation when provoked. But I'm not even talking about them no, just plain *broke*.
And so imagine being that guy who doesn't really use his phone much, except maybe for sharing cat pictures with mom because that's what being an absolute chad is all about. You don't get a new phone, because money is a __little__ bit tight. But THEN...
The dreaded CAPITAL strikes, and requests of you to bend and fall onto your knees so as to provide intense, intimate and manual -- as well as oral -- PLEASURE to the [NOT SO] METAPHORICAL PENIS of the """SYSTEM""".
Oh, what an abominable, drooooooling revenant that lies before you!
"Gimme your ass... " he says, menacingly, as you wail about in a futile attempt to guard and preserve the very last vestiges of your own anal virginity.
And so you fight, and kick him in the NADS with everything you have, down to the final shreds of vigor. Victory! Or so you thought...
"You must... " he mutters, mortally wounded "update WhatsApp... "
"Still you breathe?!" you exclaim, suddenly transformed into a heroic, sexy moustachoed arquebusier "After I'm done ~OILING~ my VICTORIOUS CHEST, I *shall* bestow DEATH uppon you!".
But as you rip open your shirt to apply sensual oiling to your marvellous frontal assets, your nemesis reveals it's portentous Portugal: "this new version of Android... " he gasps as he perishes "is incompatible with your device... "
"Ughh! Sacrebleu!" you shriek out in pain, realizing that you are now unable to ACCESS THE FUCKING DATA THAT IS IN YOUR OWN FUCKING HARDWARE BECAUSE OF A STUPID FORCED BINARY INCOMPATIBILITY.
That's right. Now even if I *do* get a new phone, I can't do shit about losing all of the family memes. And contacts and all of that shit, but the stickers are more important. A minor inconvenience, yes, and it didn't need all of this preamble but I was doing the dramatic fight scene bit inside my head as I was writing and I got into it.
Because the only documented way to transfer all of that data is to OPEN THE APPLICATION and scan some code, but everytime I go to do that, IT TELLS ME I NEED TO UPDATE. And every time I GO TO UPDATE, it says that MY PHONE is TOO FUCKING OLD!! AAAAAAAGHGHGHGHGHGHGHG!!!!
And you too, might be a dashing french man from centuries past, with both balls and tits down to your fucking knees, folding your arms in a position that exhumes smugness in a disgustingly irreverent and self-aggrandizing way, looking at me as a mere plebeian who cannot wrap his head around the mystical art of interacting with Google's black deuce box.
And you would be somewhat right in your judgement! But just having to fiddle about with these fucking pocket Elmo screens is such a traumatic experience for me that I'd rather lose my stickers.
[ADBREAK] Are you a debonair victorian undercover butt pirate, taking unparalleled care of your Falstaffian, highfalutin poils pubiens? Need your "sword" sharpened, as you browse through the pages of this magnanimous lexicon? Would you rather allocate final death to your coworkers than learn one more synonym for sonorous, supercilious and pontifical?
We all know that ALL you need to help keep that honor intact is slaying your enemies in high-stakes combat. But how to satisfy less gallant needs, when male prostitution is outlawed in more than sixteen duchies?
Look no further than BloodCurse, the ancient hex that will haunt your family for countless generations! With BloodCurse, you may crawl the earth as a mindless, shameless, piece of shit cockswallowing JUGGERNAUT that craves nothing BUT the consumption of scabbed human ass!
BloodCurse is easily contracted through consumption of the GENITAL fluids of highly-lecherous succubi, conjured through [EXTREMELY CENSORED]! This forbidden arcana allows the user to debour HIS OWN testicles in no time!
Get your bottle of scents, sensual Portuguese chest oils, and fucking designer-drug bath salts for the low, low price of a passionate, unceassing self-blowjob! And use my code FRONTALASSETS for 60% OFF in your next soul-robbing foray into the felational dark arts!
Big ups to BloodCurse for sponsoring this RRRRRRRR~$RRR$$RR%5RRRRR$0000:>A48CC50A E3A1B22A : 330D4750 7C24E5A5|.......*3.GP|$.. 5262E7D5 0D1C24E6 : 85594B39 1CB7593E|Rb......YK9..Y>
:~11 -
Just today I lost a lawsuit because my contract was written and signed in Nigeria and I sued them in the USA and I couldn't convince the judge it was fraud. I transformed the company implenting SAP and office365 and a WAN and many other projects. Worked nearly every single day 3 years in a row even during vacations, public holidays and holidays. Lost over 400k USD in lost benefits and wages that were in the contract but never paid. I feel absolutely devastated.
Unless you work for a US or European based company never ever work in Nigeria.5 -
I just transformed a sorting command that was seven lines long into an ungodly abomination that was about 70 lines.
We don't do these things because they are easy, we do them because we thought they are easy.
I will always remember that phrase and might never find out who came up with it.13 -
To me this is one of the most interesting topics. I always dream about creating the perfect programming class (not aimed at absolute beginners though, in the end there should be some usable software artifact), because I had to teach myself at least half of the skills I need everyday.
The goal of the class, which has at least to be a semester long, is to be able to create industry-ready software projects with a distributed architecture (i.e. client-server).
The important thing is to have a central theme over the whole class. Which means you should go through the software lifecycle at least once.
Let's say the class consists of 10 Units à ~3 hours (with breaks ofc) and takes place once a week, because that is the absolute minimum time to enable the students to do their homework.
1. Project setup, explanation of the whole toolchain. Init repositories, create SSH keys for github/bitbucket, git crash course (provide a cheat sheet).
Create a hello world web app with $framework. Run the web server, let the students poke around with it. Let them push their projects to their repositories.
The remainder of the lesson is for Q&A, technical problems and so on.
Homework: Read the docs of $framework. Do some commits, just alter the HTML & CSS a bit, give them your personal touch.
For the homework, provide a $chat channel/forum/mailing list or whatever for questions where not only the the teacher should help, but also the students help each other.
2. Setup of CI/Build automation. This is one of the hardest parts for the teacher/uni because the university must provide the necessary hardware for it, which costs money. But the students faces when they see that a push to master automatically triggers a build and deploys it to the right place where they can reach it from the web is priceless.
This is one recurring point over the whole course, as there will be more software artifacts beside the web app, which need to be added to the build process. I do not want to go deeper here, whether you use Jenkins, or Travis or whatev and Ansible or Puppet or whatev for automation. You probably have some docker container set up for this, because this is a very tedious task for initial setup, probably way out of proportion. But in the end there needs to be a running web service for every student which they can reach over a personal URL. Depending on the students interest on the topic it may be also better to setup this already before the first class starts and only introduce them to all the concepts in a theory block and do some more coding in the second half.
Homework: Use $framework to extend your web app. Make it a bit more user interactive with buttons, forms or the like. As we still have no backend here, you can output to alert or something.
3. Create a minimal backend with $backendFramework. Only to have something which speaks with the frontend so you can create API calls going back and forth. Also create a DB, relational or not. Discuss DB schema/model and answer student questions.
Homework: Create a form which gets transformed into JSON and sent to the backend, backend stores the user information in the DB and should also provide a query to view the entry.
4. Introduce mobile apps. As it would probably too much to introduce them both to iOS and Android, something like React Native (or whatever the most popular platform-agnostic framework is then) may come in handy. Do the same as with the minimal web app and add the build artifacts to CI. Also talk about getting software to the app/play store (a common question) and signing apps.
Homework: Use the view API call from the backend to show the data on the mobile. Play around with the mobile project to display it in a nice way.
5. Introduction to refactoring (yes, really), if we are really talking about JS here, mention things like typescript, flow, elm, reason and everything with types which compiles to JS. Types make it so much easier to refactor growing codebases and imho everybody should use it.
Flowtype would make it probably easier to get gradually introduced in the already existing codebase (and it plays nice with react native) but I want to be abstract here, so that is just a suggestion (and 100% typed languages such as ELM or Reason have so much nicer errors).
Also discuss other helpful tools like linters, formatters.
Homework: Introduce types to all your API calls and some important functions.
6. Introduction to (unit) tests. Similar as above.
Homework: Write a unit test for your form.
(TBC)4 -
I used to watch my brother code in Turbo C++, creating console games and doing university assignments. Writing something on the computer which transformed into something animated was such a wonderful revelation to me and that's when I started to learn bits and pieces of programming. Now, I'm a fill stack developer :)2
-
I got an instruction to follow exactly what the client wants with the design i have made because they are also a “designer” and guess what
A nissan juke just got transformed into fucking fiat multipla
As long the client happy i must deal with it even it against my will
So sad and mad looking my design becoming something else
Thankfully there’s DevRant to relieve this emotion 🤣 -
In my project to process CSV file it needs to be transformed into XML file. Basically 100 MB CSV is turned into 3GB XML. They can be deleted afterward but it is not implemented and no one cares. Our storage gains around 1-2 TB data each month. Right now we have ~200 TB of XML in our s3
I think I can add Big Data to my CV *sarcasm*5 -
I had the idea that part of the problem of NN and ML research is we all use the same standard loss and nonlinear functions. In theory most NN architectures are universal aproximators. But theres a big gap between symbolic and numeric computation.
But some of our bigger leaps in improvement weren't just from new architectures, but entire new approaches to how data is transformed, and how we calculate loss, for example KL divergence.
And it occured to me all we really need is training/test/validation data and with the right approach we can let the system discover the architecture (been done before), but also the nonlinear and loss functions itself, and see what pops out the other side as a result.
If a network can instrument its own code as it were, maybe it'd find new and useful nonlinear functions and losses. Networks wouldn't just specificy a conv layer here, or a maxpool there, but derive implementations of these all on their own.
More importantly with a little pruning, we could even use successful examples for bootstrapping smaller more efficient algorithms, all within the graph itself, and use genetic algorithms to mix and match nodes at training time to discover what works or doesn't, or do training, testing, and validation in batches, to anneal a network in the correct direction.
By generating variations of successful nodes and graphs, and using substitution, we can use comparison to minimize error (for some measure of error over accuracy and precision), and select the best graph variations, without strictly having to do much point mutation within any given node, minimizing deleterious effects, sort of like how gene expression leads to unexpected but fitness-improving results for an entire organism, while point-mutations typically cause disease.
It might seem like this wouldn't work out the gate, just on the basis of intuition, but I think the benefit of working through node substitutions or entire subgraph substitution, is that we can check test/validation loss before training is even complete.
If we train a network to specify a known loss, we can even have that evaluate the networks themselves, and run variations on our network loss node to find better losses during training time, and at some point let nodes refer to these same loss calculation graphs, within themselves, switching between them dynamically..via variation and substitution.
I could even invision probabilistic lists of jump addresses, or mappings of value ranges to jump addresses, or having await() style opcodes on some nodes that upon being encountered, queue-up ticks from upstream nodes whose calculations the await()ed node relies on, to do things like emergent convolution.
I've written all the classes and started on the interpreter itself, just a few things that need fleshed out now.
Heres my shitty little partial sketch of the opcodes and ideas.
https://pastebin.com/5yDTaApS
I think I'll teach it to do convolution, color recognition, maybe try mnist, or teach it step by step how to do sequence masking and prediction, dunno yet.6 -
I've seen a lot of buzz around the EU's GDPR and since I don't live there I'm wondering if it applies only if you store personal data and should it count if it's hashed for example?🤔
Let's say you hash a client's IP, it's not technically his data you've irreversibly transformed it into something else, like a computation.
For example let's say he provides you with a number and you multiply it by another and store the result, let's say 2 x 2 = 4, Is the 4 his data or yours?
Also I'm really interested in the general opinion of ranters about article 13.14 -
Being sleepy at work with a window open. For some reason the sounds of the construction site transformed into hellish screams of people being eaten by a giant human like mouth for a good 30 seconds. That's fun
-
I think after 3 months of lockdown my colleagues transformed into 🥝 or something
Yeah here's the new account
No password for it in database
This prevents from updating password
I just about had it with these fucking amateurs, good thing payday is near, I need a shitload of more drugs for motivational purposes -
The documentation of scala akka http may be just gibberish as far as I am concerned. You would think that hooking into the marshalling process (aka de/serialization) would be straight forward, I've dealt with similar problems before and solved it.
I have an object, it should be transformed into a Json and vice versa. Should be easy as pie.
Not with scala and akka-http. The docs tell you how to achieve something in dozen different ways yet lack a complete example. My first custom marshaller I created in a "marshall" package in my! namespace, but it was breaking scala compilation due to some black magic.
It's not clear how when and why marshallers are added, they just somehow are. Why do I have to deal with entity marshallers vs response marshallers. I just want each instance of a certain type to be transformed into a specific Json presentation.
Asking on stackoverflow also only yields in incomplete hints of "just do boargh" presupposing certain knowledge while sounding borderline condescending.
Currently, I just want to burn the project and rebuild it with fucking PHP. Flame all you want, at least I would get things done and the JMS serializer library has decent documentation and it works in an expected way.
Akka-http, combined with Scala, looks from my current rage-driven perspective like a solution worse than the problem. -
FFS, fucking Fuckbook and their fucking new wall system
I have posts from pages I am particularly not interested in at all (ie, all pages I see), I get a post with the recent Khimbho app story, I proceed to hide all posts from this page, and keep scrolling. The fucking next post is, guess what, another one with the Khimbho thingy, from another page. Hidden again. I have 4-5 more posts like these on my wall, among other posts which I also hide.
I then close my FB tab, and when later on I come back on it:
"ÜBERHOT WHOOPY CONTENT: KHIMBHO APP WAS TAKEN DOWN FROM THE PLAY STORE"
...
<take a deep breath>
...
FUUUUUUUUUUUUUUUUUUUUUUU STFU GET OFF MY LIFE FUCKING RUBBISH SPAMMY FUCKPAGE TURD CRAP SHOVE YOUR WALL UP YOUR RECTUM AND THROUGH YOUR DIGESTIVE SYSTEM, TAKE IT OUT OF YOUR MOUTH AND REPEAT UNTIL YOU'RE TRANSFORMED INTO A FUCKING PILE OF MESS READY TO BE THROWN IN A TRASHCAN SO YOUR CORPSE WILL BECOME HOME TO A SPECIAL BREED OF FLIES THAT WILL HUNT DOWN PEOPLE LIKE YOU AND FUCKING EAT YOU ALIVE
Man I'm pissed. -
FUCK ME!#@$%@ 6 hours now, trying to make a production build of my react/redux app but FUCKING envify sets NODE_ENV after the imported libraries are transformed!! IT WORKED TWO DAYS AGO WHAT HAPPENED :((2
-
It's kind of depressing looking at how bad the source code has transformed from a previous project that I had planned, designed, and did the initial implementation.
But I guess this is the problem of having developers who don't really care about the quality of their work, especially when it comes to PHP. -
A very long rant.. but I'm looking to share some experiences, maybe a different perspective.. huge changes at the company.
So my company is starting our microservices journey (we have a 359 retail websites at this moment)
First question was: What to build first?
The first thing we had to do was to decide what we wanted to build as our first microservice. We went looking for a microservice that can be used read only, consumers could easily implement without overhauling production software and is isolated from other processes.
We’ve ended up with building a catalog service as our first microservice. That catalog service provides consumers of the microservice information of our catalog and its most essential information about items in the catalog.
By starting with building the catalog service the team could focus on building the microservice without any time pressure. The initial functionalities of the catalog service were being created to replace existing functionality which were working fine.
Because we choose such an isolated functionality we were able to introduce the new catalog service into production step by step. Instead of replacing the search functionality of the webshops using a big-bang approach, we choose A/B split testing to measure our changes and gradually increase the load of the microservice.
Next step: Choosing a datastore
The search engine that was in production when we started this project was making user of Solr. Due to the use of Lucene it was performing very well as a search engine, but from engineering perspective it lacked some functionalities. It came short if you wanted to run it in a cluster environment, configuring it was hard and not user friendly and last but not least, development of Solr seemed to be grinded to a halt.
Elasticsearch started entering the scene as a competitor for Solr and brought interesting features. Still using Lucene, which we were happy with, it was build with clustering in mind and being provided out of the box. Managing Elasticsearch was easy since there are REST APIs for configuration and as a fallback there are YAML configurations available.
We decided to use Elasticsearch since it provides us the strengths and capabilities of Lucene with the added joy of easy configuration, clustering and a lively community driving the project.
Even bigger challenge? Which programming language will we use
The team responsible for developing this first microservice consists out of a group web developers. So when looking for a programming language for the microservice, we went searching for a language close to their hearts and expertise. At that time a typical web developer at least had knowledge of PHP and Javascript.
What we’ve noticed during researching various languages is that almost all actions done by the catalog service will boil down to the following paradigm:
- Execute a HTTP call to fetch some JSON
- Transform JSON to a desired output
- Respond with the transformed JSON
Actions that easily can be done in a parallel and asynchronous manner and mainly consists out of transforming JSON from the source to a desired output. The programming language used for the catalog service should hold strong qualifications for those kind of actions.
Another thing to notice is that some functionalities that will be built using the catalog service will result into a high level of concurrent requests. For example the type-ahead functionality will trigger several requests to the catalog service per usage of a user.
To us, PHP and .NET at that time weren’t sufficient enough to us for building the catalog service based on the requirements we’ve set. Eventually we’ve decided to use Node.js which is better suited for the things we are looking for as described earlier. Node.js provides a non-blocking I/O model and being event driven helps us developing a high performance microservice.
The leap to start programming Node.js is relatively small since it basically is Javascript. A language that is familiar for the developers around that time. While Node.js is displaying some new concepts it is relatively easy for a developer to start using it.
The beauty of microservices and the isolation it provides, is that you can choose the best tool for that particular microservice. Not all microservices will be developed using Node.js and Elasticsearch. All kinds of combinations might arise and this is what makes the microservices architecture so flexible.
Even when Node.js or Elasticsearch turns out to be a bad choice for the catalog service it is relatively easy to switch that choice for magic ‘X’ or component ‘Z’. By focussing on creating a solid API the components that are driving that API don’t matter that much. It should do what you ask of it and when it is lacking you just replace it.
Many more headaches to come later this year ;)3 -
Getting the angular interceptor working the way I want has proven to be a pain for me. I try to update an auth token, which returns a promise that has to be transformed to an observable again. based on that, redirect to a login page, in case of 401. But nothing works! Either infinite page reload because of the login() promise function of the auth provider or no reaction at all after a router redirect. 😤4
-
Transformed my gaming rig into a dual boot hackintosh since I had a SSD from my previous build laying around. Now the fucking thing boots perfectly fine besides that shitty wifi USB dongle which just reconnects 3-10 times to the wifi and then suddenly causes a kernel panic. Fucking piece of shit 😑
-
1. It is a creative process that I can actually perform reasonably well at.
2. I get a buzz when delivering the solutions to the client and seeing their ideas transformed into a working application. It is, to my mind, a similar feeling that architects and engineers get when seeing their projects to fruition.
3. After 30 years, I am still learning new things, and I am still excited to see how coding will develop in the future. -
This is a repost of an original rant posted on a request for "Community Feedback" from Atlassian. You know, Atlassian? Those beloved people behind such products as :
• Thing I Love™
• Other Thing You Used One Time™
• Platform Often Mentioned in Suicide Notes, Probably™*
Now this rant was written in early 2022 while I was working in an Azure Cloud Engineer role that transformed into me being the company's main Sysadmin/Project Manager/Hiring Manager/Network Admin/Graphic Designer.
While trying to simultaneously put out over 9000 fires with one hand, and jangling keys in the face of the Owner/Arsonist with the other, I was also desperately implementing Jira Service Desk. Normally this wouldn't have been as much of a priority as it was, but the software our support team was using had gone past 15 years old, then past extended support, then the lone developer died, then it didn't work on Windows 10, then only functioned thanks to a dev cohort long past creating a keygen....which was now broken. So we needed a solution *now*.
The previous solution was shit of a different tier. The sight of it would make a walking talking anthropomorphised sentient puddle of dogshit (who both eats and produces further dookie derivatives) blush with embarrassment. The CD-ROM/Cereal Box this software came in probably listed features like "Stores Your Customer's First AND (or) Last Name!" or "Windows ME Downgrade Disk Included!" and "NEW: Less(-ish) Genocide(s)"!
Despite this, our brain/fearless leader decided this would be a great time to have me test, implement, deploy, and train everyone up on a new solution that would suck your toes, sound your shaft, and that he hadn't reminded me that I was a lazy sack enough lately.
One day, during preliminary user testing I received an email letting me know that the support team was having issues with a Customer's profile on our new support desk. Thanks to our Owner/Firestarter/Real World Micheal Scott being deep in his latest project (fixing our "All 5 devs quit in the last 12 months and I can't seem to hire any new ones" issue (by buying a ping pong table)), I had a bit of fortuitous time on my hands to investigate this issue. I had spent many hours of overtime working on this project, writing custom integrations and automations, so what I found out was crushing.
Below is the (digitally) physical manifestation of my rage after realising I would have to create / find / deal with a whole new method for support to manage customer contacts.
I'm linking to the original forum thread because you kind of need to have the pictures embedded in said reply to get really inhale the "Jira-Rant" ambiance. The part where I use several consecutive words as anchor links to tickets with other people screaming into the void gets a bit sweet n' savoury too - having those hyperlinks does improve the je ne say what of it all.
bit.ly/JIRANT (Case Sensitive)
--------------------------
There is some good news at the end of this brown n' squirty rainbow though!
Nice try silly little Jira button, you can't ruin *my* 2022!
• I was able to forget all about Jira a month later when I received a surprise vacation home! (To be there while my Mom passed away).
• Eventually work stress did catch up to me - but my boss thoughtfully gave me a nice long vacation! (By assaulting *while* firing me (for emailing in a vacation request while he was a having a bad (see:normal) day))
5 -
Got in a great company wherein I will be transformed from php to mean/mern stack. Improvise adapt overcome.
Will apply php best practices in the JS world.
After mean/mern, study react native or flutter. I like flutter but in my company there are only react native projects. Hhmm maybe because flutter is just new. Exciting future indeed 💪6 -
HOW CAN I HIRE A HACKER TO RECOVER MY STOLEN BITCOIN. CONNECT WITH SPARTAN TECH GROUP RETRIEVAL
In the tumultuous landscape of cryptocurrency investments, the unyielding support of Spartan Tech Group Retrieval plays a pivotal role in helping individuals restore their Bitcoin investments. With expert guidance and an unwavering commitment to client success, their team navigates the complexities of lost or compromised digital assets. Utilizing advanced recovery techniques and an in-depth understanding of blockchain technology, they empower investors to reclaim what is rightfully theirs. Their dedication not only alleviates the financial anxiety associated with frozen or vanished assets but also fosters confidence in the rapidly evolving world of Bitcoin investments. Spartan Tech Group Retrieval stands as a beacon of hope, providing essential resources and strategies to ensure that setbacks can be transformed into opportunities for resurgence. However, many have discovered that embracing recovery tools like Spartan Tech Group Retrieval can transform their experience from despair to empowerment. This platform offers a structured approach, guiding individuals through the process of reclaiming lost funds and rebuilding their portfolios. Users share heartening stories of resilience, detailing how they went from facing financial ruin to regaining control over their investments. The platform not only provides technical assistance but also fosters a supportive community where shared experiences ignite hope. By utilizing Spartan Tech Group Retrieval, investors learn valuable lessons about risk management and the importance of a strategic mindset, turning their losses into stepping stones for future success. This transformative potential highlights that, even in the unpredictable realm of cryptocurrency, recovery is not just possible; it's a powerful opportunity for growth. Thanks to Spartan Tech Group Retrieval, I was able to recover the funds I thought I had lost for good. What’s more, they equipped me with the knowledge and tools to protect myself from future scams. They helped me set up stronger security protocols, including the use of hardware wallets and multi-factor authentication, ensuring that my investments would be much safer going forward. But perhaps most importantly, Spartan Tech Group Retrieval restored my faith in the cryptocurrency space. Prior to my experience with fraud, I had always believed in the potential of digital assets. However, after the scam, I had serious doubts about the entire industry. Spartan Tech Group Retrieval professionalism, persistence, and integrity proved that while fraud exists, there are also people working tirelessly to protect investors and mitigate the damage caused by these criminals. Text on WhatsApp:+1 (971) 4 8 7 -3 5 3 8
Telegram:+1 (581) 2 8 6 - 8 0 9 2
Email: spartantechretrieval (@) g r o u p m a i l .c o m
: so that you can get the help you seek.
3 -
It's been some months and I've been working with data, I'm in charge of the data migration and after 4 months into the job, they tell me that the data is sometimes transformed but they do not have a tool to validate the data, instead they do it manually.
When I said, that if we do it manually, it'll be prone to human error. My team says that humans make errors.
They're basically checking 2 rows of the database manually and then pray. That's their way of testing/validating the data.
Couple years back when I was in college, we used to talk about code quality or whatever but I don't think that's followed anywhere.
Developers are lazy. That's the fucking truth.1 -
BITCOIN RECOVERY REDEFINED: RAPID DIGITAL RECOVERY EXPERT APPROACH
What began as a tragic loss quickly turned into a story of healing and success. I had accumulated a substantial digital fortune over the years as an experienced Bitcoin fan, keeping my private keys safe and safeguarding my digital assets. But destiny had other ideas, as a thoughtless error caused the unimaginable—my whole Bitcoin holdings to vanish into thin air. I struggled with the notion that my years of hard-earned savings had been completely destroyed in an instant, and I felt panic and sorrow. However, I resisted giving up. I set out on a mission to find my lost Bitcoin, searching the internet for any semblance of hope, driven by an unrelenting determination. It was then that I discovered the legendary Rapid Digital Recovery – a shadowy figure renowned for their uncanny ability to retrieve even the most elusive of digital assets. Mustering my courage, I reached out, entrusting this enigmatic expert with the daunting task of restoring my lost fortune. The Wizard, with their vast knowledge and unparalleled skills, delved into the intricate tapestry of the blockchain, meticulously tracing the path of my missing Bitcoin. Through a series of complex maneuvers and ingenious strategies, they managed to locate and recover every last satoshi, returning my digital wealth to me with a triumphant flourish. In the aftermath of this harrowing ordeal, I found myself overwhelmed with a profound sense of gratitude and joy. Not only had I regained my financial security, but I had also gained a newfound appreciation for the resilience of the Bitcoin network and the dedication of those who safeguard its integrity. This experience has forever transformed my relationship with cryptocurrency, instilling in me a deeper respect for the power of decentralized finance and the extraordinary individuals who work tirelessly to protect it. From the depths of despair to the heights of jubilation, my recovery tale stands as a testament to the unwavering spirit of the Bitcoin community and the transformative power of the Rapid Digital Recovery prowess. The delight I felt was beyond description, and the relief I felt was incredible. In a moment, all of the worry and the restless nights were gone. Rapid Digital Recovery and the skilled staff who made the impossible possible have my sincere gratitude. They really made my worst become a reality. I highly recommend their services if you find yourself in a similar circumstance. Dial:
Web site Info: https: // ra pi ddigit alrecove ry .o rg
What sapp Info: +1 41 4 80 7 14 85
Email Info: rap iddi gital recov ery @ exe cs. com
2 -
Oh Shit, Git!?!
In case of fire 🔥:
1. git commit
2. git push
3. git check-tf-out of that goddamn building
(Totally upto ya btw if you don't wanna get transformed into Kentucky fried hooman)
4. git push -o restoftheday.skip -
IS IT POSSIBLE TO RECOVER STOLEN FUNDS BACK? Yes. HIRE ADWARE RECOVERY SPECIALIST
Like a lot of people, I never thought that one error might result in the loss of 91,000 BTC. When I discovered my Bitcoin was gone, I experienced an incredible sense of shock and disbelief. I had invested a lot of time and energy into building up my cryptocurrency holdings, and all of that seemed to be gone in a moment. The emotional toll was too great, and I was plagued by feelings of remorse and failure. Nothing appeared to give me optimism, and I felt as though my financial future had been ruined. After doing some investigation, I came upon ADWARE RECOVERY SPECIALIST. I was apprehensive at first. To get my Bitcoin back, I had already tried a few different approaches, but none of them had been successful. However, ADWARE RECOVERY SPECIALIST standing and client testimonials persuaded me to give them a shot. I was unsure if I would be able to get such a big amount back when I reached out, but their staff informed me right away that they could assist. Although the actual recovery process took a while, ADWARE RECOVERY SPECIALIST made sure I was always informed and up to date. They put in a great deal of effort on my behalf, and I had never experienced such dedication. Every step I took got me closer to the result I so badly wanted, and every update from their team gave me optimism. I subsequently got the notification that my 91,000 BTC had been entirely restored after what felt like an eternity of waiting. At first, I couldn't believe it. I was so relieved that what had looked like an unattainable goal was suddenly a reality. I was able to recover not just my Bitcoin but also my piece of mind because of ADWARE RECOVERY SPECIALIST diligence and skill. In the face of adversity, both ADWARE RECOVERY SPECIALIST and I emerged as shining examples of resilience and determination, demonstrating that setbacks can serve as powerful catalysts for success. After experiencing a troubling loss, ADWARE RECOVERY SPECIALIST transformed its challenges into a blueprint for innovation and strategic recovery, inspiring countless others who find themselves grappling with similar struggles. Meanwhile, my own journey with Bitcoin, marked by the daunting task of recovering a staggering $91,000, taught me invaluable lessons about perseverance and the potential for triumph in the most difficult of circumstances. Both stories intertwine, illustrating that from the depths of despair, we can rise again, fortified by the wisdom gained through our trials. With unwavering hope and relentless effort, we can reclaim our achievements, turning the page from defeat to victory, and prove that the spirit of growth knows no bounds. Wait no more, Contact ADWARE RECOVERY SPECIALIST.
3
Top Tags
Weekly Rant
View