Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Search - "service workers"
I realize I've ranted about this before, but...
First the fact that external services can throw back 500 errors or timeouts when their maintainer did a drunk deploy (but you properly handled that using caching, workers, retry handlers, etc, right? RIGHT?)...
Then the fact that they all speak a variety of languages and dialects (Oh fuck why does that endpoint return a JSON object with int keys instead of a simple array... wait the params are separated with pipe characters? And the other endpoint uses SOAP? Fuck I need to write another wrapper class around the client...)
But the worst thing: It makes developers live in this happy imaginary universe where "malicious" is not a word.
"I found this cloud service which checks our code style" — hmm ok, they seem trustworthy. Hope they don't sell our code, but whatever.
"And look at this thing, it automatically makes database backups, just have to connect to it to DigitalOcean" — uhhh wait...
"And I just built this API client which sends these forms to be OCR processed" — Fuck... stop it... there are bank accounts numbers on those forms... Where's that API even located? What company?
"We can not guarantee the safety of your personal data, use at your own risk [...] we are located in Russia".
I fucking hate these millennial devs who literally fail to get their head out of the cloud.
Somehow they think it's easier to write all these NodeJS handlers and layers around some API, which probably just calls ImageMagick + Tesseract on the other side.
If I wasn't so fucking exhausted, I'd chop of their heads... but they're like hydra, you seal one privacy breach and another is waiting to be merged, these kids just keep spewing their crap into easy packages, they keep deploying shitty heroku apps... ugh.
I can't believe this company.
They want to stop using Certificates because it bothers the customer.
I had to use https because we were using service workers for a PWA.
I tried explaining we need them for the product to work, and also it's a basic security measure.
They were removing the certificates without my knowledge.
I found out because a colleague wanted a way to disable the service worker and asked me for help.
The manager said your not the boss of the company, it's not your company to make decisions.
Just do what they say, he tried to justify the decision from above, I said ok when was the last time you installed a certificate? he said never.
Ok, then what the fuck are you talking about, its 10 minutes to get a certificate letscrypt HELLO.
This company is very hierarchical 1900 style, I'm the person who does innovation in the organization, that's the most fucked up part, they say no to everything.
OMG, I'm going to quit.
There just asking to get hacked, this is just the tip of the iceberg.
Is this common or are they morons?18
National Health Service (nhs) in the UK got hacked today... Workers at the hospitals could not access patient and appointment related data... How big a cheapskate you gotta be to hack a free public health service that is almost dying for fund shortages anyway...16
It's not a dev quiting but my brother who worked in parcel delivery at that time.
He was hired on a temporary contract but promissed from the beginning and in every discussion they had, that he'll get a permanent position after 6 moth, if his work is good.
Fast forward 6 months. They had a meeting and told him how satisfied they where with his work so naturally he asked about the permanent contract. Fuckers acted suprise and shit. Claiming to never have said any of it. However as they are happy with him and so "generous", they offerd him another contract for 6 months and told him, they could talk about a permanent one after that period.
He kind of has a temprament, so he got up, fliped them the bird and called them lying assholes and went home. He didn't show for the time left on his contract.
The funny thing about it he worked for the swiss postal service (which is owned by the state) but not directly but through this.company providing temporary workers (which is cheaper for them as they get a shitty salary compared to a full time employee with all the benefits).
Nice thing though, the accounting department still sent him a christmas bonus (he quit somewhere around mai...)7
My company decided to reinvent the wheel by writing its own queue system instead of using the existing message queue service.
And it uses plain PHP with exec() to run the workers.
Where do we store the job? We use mongoDB which is already used in our existing projects. We can query the collection/table each time the queue service start, execute the jobs, and let it exit if there's no job anymore. Don't worry, systemd will start the queue service again once it exits.
How to monitor the workers? Yep, we use ps and grep to check if the worker's PID still exists in the OS.
What about error stack traces? Nice question, we redirect the stdout and stderr when exec()-ing into a file.
What about timeout? We don't need it, let's just assume no one is going to write while(true).
It works flawlessly! /s8
This was not exactly the worst work culture because the employees, it was because the upper level of the organization chart on the IT department.
I'm not quite sure how to translate the exact positions of that chart, but lets say that there is a General Manager, a couple of Area Managers (Infrastructure, Development), some Area Supervisors (2 or 3, by each area), and the grunts (that were us). Anyway, anything on the "Manager" was the source of all the toxicity on the department.
First and foremost, there was a lack of training for almost any employee. We were expected to know everything since day-1. Yes, the new employees had a (very) brief explanation about the technologies/languages were used, but they were expected to perform as a senior employee almost since the moment they cross the door. And forget about having some KT (Knowledge Transfer) sessions, they were none existent and if they existed, were only to solve a very immediate issue (now imagine what happened when someone quit*).
The general culture that they have to always say "yes" to the client/customer to almost anything without consulting to the development teams if that what was being asked to do was doable, or even feasible. And forget about doing a proper documentation about that change/development, as "that was needed yesterday and it needs to be done to be implemented tomorrow" (you know what I mean). This contributes to the previous point, as we didn't have enough time to train someone new because we had this absurd deadlines.
And because they cannot/wanted to say "NO", there were days when they came with an amount of new requirements that needed to be done and it didn't matter that we had other things to do. And the worst was that, until a couple of years (more or less), there was almost impossible to gather the correct requirements from the client/user, as they (managers) "had already" that requirement, and as they "know better" what the user wants, it was their vision what was being described on the requirements, not the users'...
And all that caused that, in a common basis, didn't have enough time to do all this stuff (mainly because the User Support) causing that we needed to do overtime, which almost always went unpaid (because a very ambiguous clause of the contract, and that we were "non-union workers"**). And this is my favorite point of this list, because, almost any overtime went unpaid, so basically we were expected to be working for free after the end of the work day (lets say, after the 17:00). Leaving "early" was almost a sin for the managers, as they always expected that we give more time to work that the indicated on the contract, and if not, they could raise a report to HR because the ambiguous clause allowed them to do it (among other childish things that they do).
Finally, the jewel of the crown, is that they never, but never acknowledge that they made a mistake. Never. That was impossible! If something failed on the things/systems/applications that they had assigned*** it was always our fault.
- "A report for the Finance Department is giving wrong information? It's the DBA's fault**** because although he manages that report, he couldn't imagine that I have an undocumented service (that runs before the creation the report) crashed because I modified a hidden and undocumented temporal table and forgot to update that service."
But, well, at least that's on the past. And although those aren't all the things that made that workplace so toxic, for me those were the most prominent ones.
* Well, here we I live it's very common to don't say anything about leaving the company until the very last day. Yes, I know that there are people that leave their "2-days notice", but it's not common (IMHO, of course). And yes, there are some of us that give a 1 or 2-weeks notice, but still it's not a common practice.
** I don't know how to translate this... We have a concept called "trusted employee", which is mainly used to describe any administrative employee, and that commonly is expected to give the 110% of what the contract says (unpaid overtimes, extra stuff to do, etc) and sadly it's an accepted condition (for whatever reasons). I chose "non-union workers" because in comparison with an union worker, we have less protections (besides the legal ways) regarding what I've described before. Curiously, there are also "operative workers", that doesn't belong to an union, but they have (sometimes) better protections that the administrative ones.
*** Yes, they were in charge of several systems, because they didn't trust us to handle/maintain them. And I'm sure that they still don't trust in their developers.
**** One of the managers, and the DBA are the only ones that handle some stuff (specially the one that involves "money"). The thing that allows to use the DBA as scapegoat is that such manager have more privileges and permissions than the DBA, as he was the previous DBA2
I was using the app Jobr to apply for random positions. It’s like tinder — only you swipe to send your resume.
A week or so later I got an email from a company locally that wanted to set up an interview. I honestly thought it was a scam! I didn’t even remember applying for the job.
Long story short, they’re mostly desktop developers, and I’m the first front end web guy. I was initially hired to help with UI stuff but on the last project I was developing Service Workers. So I guess I just get invested and give my fullest.
Now myself and one of the other programmers are working on the 3rd gen of our software, built with Vue.js and rest APIs.4
Public Service announcement:
If one of your co-workers asks: "Hey, do you have a sec?"
DO NOT reply: "Yeah, I have tons of secs"
Someone who doesn't think before they speak7
Look what I'm fixing to say is gonna make seem like a cunt and it'll probably be deserved but at the same time, I think it should be said too.
The increasingly high number of people fishing for compliments and attention because of their CHOSEN profession being important in the current times is starting get old as fuck.
I've seen so many people fishing for compliments; rather it be medical workers or truck drivers because their job is more important now than usual.
Like don't get me wrong, they're all necessary for society to function. But for crying out loud y'all chose this profession for yourselves. You knew this could happen whenever you decided to go to school for your job. You don't hear server admins bragging and fishing for attention whenever they restore access to a service.
Just do your job, know that everyone appreciates what you're doing even if it's not being verbally said, and let it end there. Personally feel that if you went into the medical field for the praise and recognition, then you went in there for the wrong reason.
Anyways, y'all stay safe and let's get this shit show over with already. Ya boy is going insane5
How the fuck does TypeScript still not have service worker support? Seriously, it's just a typings file. People have written that typings file. They would just have to include it in the lib collection shipped with the compiler. Yeah, it would have DOM calls intermixed with the SW api, but frankly, having the typings for a set of calls you can't use is infinitely better than missing them for a set of calls you can.
The relevant issue is 5 years old btw.7
I just officially graduated from a web dev program and it feels...
Learned ES6, React, Webpack, service workers, offline databases, accessibility, (...bla bla bla)
And my knowledge with data structures and algorithms isn't even that great yet.
I look at the stuff I still don't know and wonder if I'll ever be comfortable with my level of expertise.13
I think some of my co-workers see me as real life human version of Google search engine.
Hope they would understand that just because I'm little bit more up to date in tech knowledge and an accidental Google nerd doesn't make me a know it all..
But i understand their tendency to trust my recommendation over their googling skills
They want me to find
1- best freelancing website
2- best platform or service for someone who wants to do online teaching
Results that I'm aware of:
1- freelancer, guru, upwork
2- YouTube, udemy, Pluralsight, skillshare, thinkific
Any other recommendations?2
To everyone who are using service workers on your website to implement notifications: wait untill I visit your website at least more than once before you ask me if I want notifications from your website.3
I haven't got in for a while but dude, I want to rant.
This guy originally wanted a simple online shopping system, with the "cart" sent to WhatsApp. No big deal, most of it was done in 2 days.
Then he wanted geolocation so the app would show you the nearest sites. Sure, why not. I had never worked with something like that so it might be worth it to try and learn.
Then he wanted custom URLs. It took me a little but this wasn't in the plans...
Then a copy of the system but focused on workers instead of products.
And another for big providers.
Then an integration with a delivery service.
And more in the following weeks...
Dude. WTF, I was only paid some weeks and he keeps adding and adding stuff. All at the same time while the first still didn't have the final design. It's been 3 months.
I hate this kind of guys. I didn't know the kind but now I hate them.5
I've always wanted to do something in IT Support, but I didn't know where to start. I've been helping my co-workers optimize their system and even helped retrieve photos from a tablet that had a broken screen; her service plan said along the lines of "if they weren't there they were lost," I was able to retrieve them in a matter of hours (Really guys! I'm shocked! It was just a broken touchscreen, the storage was just fine. I think I'll remember this moment).
And because my growing impopularity, I started a new business called The Webnician. The company is split into two sections, the Technician, and the Web Developer. Hence, The Web(Tech)nician. I am proud of my name choice.
Then I wanted to become a certified technician, so I did some research on how to become one and found out I need to take the CompTIA A+ 220-901 and 220-902 exam and... I couldn't be more excited!
I've always loved computers, and maybe my late father had some say into it. Nevertheless, I am excited to begin my journey, even though it took awhile to find where I needed to go. I hope you all can follow me on my journey and support my new business.
I don't have anything else to say, so I'll just leave here.1
I'm in love with service workers. This is so fucking satisfying (also love the offline first capabilities)6
Which will block browser coin miners on Chrome for now. Other ad/script blockers might work (though not always guaranteed).
Currently, these miners don't limit their CPU usage (and neither does the browser) so it's not great for your PC use.
If implemented correctly, like only using for a few seconds or for captchas/link shorteners (as suggested on the Coin Hive site), this could be a nice alternative to ads. But there is a guarantee that many will start using this unethically and not even tell users, nevermind that they'll do it for the entire session of the site.
Add Service Workers to the mix and it's a bag of trouble.12
Everyone I tell this to, thinks it’s cutting edge, but I see it as a stitched together mess. Regardless:
A micro-service based application that stages machine learning tasks, and is meant to be deployed on 4+ machines. Running with two message queues at its heart and several workers, each worker configured to run optimally for either heavy cpu or gpu tasks.
The technology stack includes rabbitmq, Redis, Postgres, tensorflow, torch and the services are written in nodejs, lua and python. All packaged as a Kubernetes application.
Worked on this for 9 months now. I was the only constant on the project, and the architecture design has been basically re-engineered by myself. Since the last guy underestimated the ask.2
Okay, if I understand correctly, if you want your website to be RGPD compliant, you must wait for user opt-in before storing anything to their device.
Maybe I'm asking myself too much questions but, how exactly does this work for a PWA ? Should you ask user for permission before starting a service worker and/or before caching any content ? If so, what if the user refuses the authorization ? The app is broken ? Or it just fallback to good old http browsing if it's server-rendered ?3
Service based companies and Nepotism
In India, most IT companies hires their own family members. Even they promote their own family members. One of the my friend worked as dev he found that mostly his co workers are relatives of founder or managers. He told me that he understand if they get hired from some kind of references but that's not case here. Even HR is also family member of manager/founder. Most of this guys don't know any language. Even they don't have any kind of professionalism
Imagine that working on companies where your co-workers and HR is family members of managers and founder. Where you find help because everyone will against you because all are family members.
they deduct PF of workers who are not relatives and never pay tax to goverment. In india, most developers are desperate to get job because that's what education system and society taught them.
Hope startup culture will kill all these shitty companies1
A small piece of advise: If you are considering using service workers, please checkout sw-toolbox you'll thank me later
10:15 on a Friday and already...
- accidentally nuked dev copy of htdocs (fucking fuck!!! shit!)
- remote work for the summer has been cancelled
- irritating client (with a bunch of incorrect assumptions and pedantic requests) believes they deserve top priority and instant service and are blowing up my phone/email
- construction workers in and around office being disruptive
- other projects stalled for no reason
I’m looking forward to booze and sleep.3
When I build something new for the first time.
A year ago I discovered PWA (progressive web apps), web workers and service workers, wanted to build something cool, I sat down at 10AM and started digesting every resource I could find, test, make mistakes, try again, then my eyes started to itch I looked at the clock it's already midnight !
For 2020 I want to achieve more insight of my already running collaboration service/tool for businesses by talking more to managers, chiefs and workers.
And for a better internet community a GUI for NGINX for home servers (any PC) that could interface with purchased domains to make configuration become automatic, to make self hosted web-apps/services more accessible and streamlined.