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
-
My wife opens a document, writes her entire paper and uses the close ❌ button to save it.
I think I married an adrenaline junkie.12 -
For this episode of practiseSafeHex's most incompetent co-worker were going to move past developers and go straight to a CEO.
*sitcom audience oooooohhhhhhh*
I know! , always risky, everyone has a bad story, but lets try bring it home. Here we go, Most incompetent co-worker, candidate 2, "R".
R was ... now how do I say this ... R was a special kind of Bastard. A perfect blend of impatient, arrogant, a dickhead and to borrow a phrase from family guy "below the line of mental retardation".
I've actually spoken about him recently here: https://devrant.com/rants/1141873/...
I won't bother duplicating the content here, but its worth a read.
Some of the other highlights of R include:
- Not understanding that my first demo was UI / Frontend only (despite frequent explanations). I didn't slack off for the next 2 weeks, I was busy making all those buttons actually do stuff and connect to the server. Shockingly "Test 1", "Test 2" and "Lorem ipsum" wasn't our content.
- He once asked how long a bunch of tasks was going to take, I told him 2 weeks and he gave me 2 and a half days. He pulled me into a meeting the next week to see where it all was, and I literally sat there saying "I asked for 2 weeks" over and over until he shut up.
- R's favourite phrase was "when I was a developer", typically followed by some sort of insult, forever labelling him "asshole" by everyone who has ever worked for him.
- When apple launched iOS 7 and changed the UI and the methods you could use, he refused to invest the time in upgrading to iOS 7, but demanded the app look like an iOS 7 app. No amount of "There is no method to access the status bar in iOS 6" could make him comprehend the issue at hand.
- The worst was when I was dealing with an issue to do with 64bit being introduced (which I tried to explain ... christ give me strength). When another dev fixed a similar but unrelated issue he stood up in front of the office and said loudly "pfft practiseSafeHex tried to tell me this was something to do with 64bit, which made absolutely no sense, guess he doesn't know what he's talking about"
Thankfully I handed in my notice ... after less than 2 months, making in abundantly clear why. Will R make it to the top of the list of most incompetent?
Tune in later for more practiceSafeHex's most incompetent co-worker!!!12 -
Me and my father at breakfast.
Me: Do you wanna play Russian Roulette?
Father: I boot up Windows every day. I already live the risky life.3 -
--- GitHub 24-hour outage post mortem ---
As many of you will remember; Github fell over earlier this month and cracked its head on the counter top on the way down. For more or less a full 24 hours the repo-wrangling behemoth had inconsistent data being presented to users, slow response times and failing requests during common user actions such as reporting issues and questioning your career choice in code reviews.
It's been revealed in a post-mortem of the incident (link at the end of the article) that DB replication was the root cause of the chaos after a failing 100G network link was being replaced during routine maintenance. I don't pretend to be a rockstar-ninja-wizard DBA but after speaking with colleagues who went a shade whiter when the term "replication" was used - It's hard to predict where a design decision will bite back and leave you untanging the web of lies and misinformation reported by the databases for weeks if not months after everything's gone a tad sideways.
When the link was yanked out of the east coast DC undergoing maintenance - Github's "Orchestrator" software did exactly what it was meant to do; It hit the "ohshi" button and failed over to another DC that wasn't reporting any issues. The hitch in the master plan was that when connectivity came back up at the east coast DC, Orchestrator was unable to (un)fail-over back to the east coast DC due to each cluster containing data the other didn't have.
At this point it's reasonable to assume that pants were turning funny colours - Monitoring systems across the board started squealing, firing off messages to engineers demanding they rouse from the land of nod and snap back to reality, that was a bit more "on-fire" than usual. A quick call to Orchestrator's API returned a result set that only contained database servers from the west coast - none of the east coast servers had responded.
Come 11pm UTC (about 10 minutes after the initial pant re-colouring) engineers realised they were well and truly backed into a corner, the site was flipped into "Yellow" status and internal mechanisms for deployments were locked out. 5 minutes later an Incident Co-ordinator was dragged from their lair by the status change and almost immediately flipped the site into "Red" status, a move i can only hope was accompanied by all the lights going red and klaxons sounding.
Even more engineers were roused from their slumber to help with the recovery effort, By this point hair was turning grey in real time - The fail-over DB cluster had been processing user data for nearly 40 minutes, every second that passed made the inevitable untangling process exponentially more difficult. Not long after this Github made the call to pause webhooks and Github Pages builds in an attempt to prevent further data loss, causing disruption to those of us using Github as a way of kicking off our deployment processes (myself included, I had to SSH in and run a git pull myself like some kind of savage).
Glossing over several more "And then things were still broken" sections of the post mortem; Clever engineers with their heads screwed on the right way successfully executed what i can only imagine was a large, complex and risky plan to untangle the mess and restore functionality. Github was picked up off the kitchen floor and promptly placed in a comfy chair with a sweet tea to recover. The enormous backlog of webhooks and Pages builds was caught up with and everything was more or less back to normal.
It goes to show that even the best laid plan rarely survives first contact with the enemy, In this case a failing 100G network link somewhere inside an east coast data center.
Link to the post mortem: https://blog.github.com/2018-10-30-...7 -
Saw a video of an interview on Cloud Computing...
That genius guy says: "Cloud computing is highly risky. Because if it rains, all the data will be lost."4 -
I'll start my own series on hacking.
BECOME A HACKER WITH 4 SIMPLE STEPS!!!!!1!
#1 Open cmd
#2 Enter hackermode
Type "color 0a"
#3 write a Hackerscript
Type "%0 | %0"
Step 3 is a bit risky and may fail. Reboot and repeat until you understand why it failed
#4 Realize that the internet is scary place and that you can't trust anyone.9 -
Yesterday, my girlfriend caught a virus. There were 5+ running programs, in program files, program files x86, system32, basically everywhere. The virus modified chrome, firefox, edge (and even installed a false uc browser assuming we had one), there are many entries at startup programs, also running daemons, once you kill one of them, the others detect it and replicate their killed fellows. Tried to run a linux live usb disk for a cleanup, but the computer hibernates instead of shutdown, making modifications on disk risky.
I spent hours trying to suppress the processes, do a manual cleanup and antivirus search. It looked all cleaned up, then I reinstalled chrome, and now it switches its homepage everytime I open it, it also injects batch arguments to desktop link forum chrome (deleting it manually does not help, it comes back). I'm a linux guy, and in a few hours, I hated windows more than ever.
If anybody knows the authors, I *really* want to meet them. I promise I'm not going to punch them, but kneel down, bow my head in respect, and say "teach me master."14 -
Fellow developers,
For all people asking u to be partners of their "billionaire" idea, and to be paid from revenue ONLY when the plateform goes live or shit like this, BEWARE.
For all of them i had the same answer: "ok, ill share with you the project, but until it goes live, i am the only one who is giving sacrifice, and since we are partners, i want us both to do same level of sacrifices in order to deserve later the share of revenue... That being said, u have to pay the hours of devlopment, all of them, and when it goes live, from the revenue ill get, ill pay you back what you paid on dev cost"
It is the only way to be really even...
And if he refuse, ask them again "why? I taought u where 100% sure that your idea will work and become a billionaire why u think it is risky tp pay few thousands????"
... Now he is having second thaughts12 -
WHAT THE HELL??
It's been over TWO WEEKS now and my Arch sticker pack still has NOT arrived!!!
I'm really starting to get mad now.
Unlike the stickers, my brand new laptop has arrived. But as you might have guessed, it's completely useless at the moment.
Like, what's even the point of having a laptop with Arch, when you can't show everyone else you're using Arch? So humiliating, can't even go in public now with that laptop.
People in the cafeteria will look at the back of my laptop without knowing I'm using Arch. The shame... Almost inhuman.
My only option is to go to speak to everyone individually to tell them I'm using Arch.
However, that might be risky. Imagine if I would miss someone!? They would leave without knowing I was using Arch.
In fact, I might not even meet them EVER AGAIN! In that case they would NEVER know I was on Arch! OMG! TOO MUCH HORROR!!!
All this because of a shity manufacturer.
Manufacturers like this really piss me off.
Because YOU can NOT ship on time I have to WASTE precious time now, THANKS A LOT China Stickers Corporation.10 -
Your entire time with the company, be polite and cordial, don't say risky things, basically be a good boy. But importantly, stay social. Just politely social.
After several months of this, enough time that your fellow employees and management are well aware of your personality, go to the PM in private. Threaten them that if they don't leave you alone you're going to break into their house at night, sedate them, dislocate their jaw and take a shit down their throat.
The beauty of this is that they can't reasonably go to anyone over this, as it's totally unbelievable and out of character. And will be so horrified of what they just heard that they will leave you alone.1 -
(Best read while listening to AEnima by Tool, loudly)
Dear Current Workplace,
Fuck you, for the reasons enumerated below.
Fuck your enterprise grey blue offices, the stifling warm air of a hundreds of bodies and sub par "development laptops".
Fuck your shitty carbonated water machines which were a cost saving measure over decent drinkable water.
Fuck your fake "flexi time", "you can do home office whenever you want" bullshit. You're still inviting me to mandatory meetings at 09:00 regularly.
Fuck your shitty, in house, third part IT provider sister company. They're the worst of all worlds. If it was in company, we'd get to give out to them, if it was an external company we'd fire them. And yes, when I quit I will quote the dumpster fire that is our corporate VPN as a major factor.
Fuck your cheery, bland, enterprise communication. Words coming under the corporate letterhead seem to lose all association with meaning. Agile, communication, open are things you write and profess to respect, but it seems your totally lack understanding of their meaning.
Fuck your client driven development. Sometime you actually have to fix the foundations before you can actually add new features. And fuck you management who keep on asking "why are there so many bugs and why is it always taking longer to deliver new releases". Because of you, you fucknuts, Because you can't say "NO" to the customer. Because you never listen to your own experienced developers.
Fuck your bullshit "code quality is important to us" line. If it's so important, then let us fix the heap of shit you're selling so that it works like a quasi functional program.
Fuck you development environment which has 250 projects in a single VS solution. Which takes 5mins plus to compile on a quad core i7 with 32 gb of ram.
Fuck this bullshit ball of mud "architecture". I spend most of my time trying to figure out where the logic should go and the rest of the time writing converters between different components. All because 7 years ago some idiot "architect" made a decision that they didn't have to live with.
Actually, fuck that guy in particular. Yeah, that guy who was the responsible architect for the project for 4 years and not once opened the solution to look a the code.
Fuck the manual testing of every business process. Manual setup of the entities takes 10mins plus and then when you run, boom either no message or some bullshit error code.
Fuck the antiquated technology choices which cause loads of bugs and slow down development. Fuck you for forcing me to do manual tests of another developers code at 20:00 on a Friday night because we can't get our act together to do this automatically.
Fuck you for making sure it's very clear I'm never going to be anything but a code monkey in this structure. Managers are brought in from outside.
Fuck you for being surprised that it's hard to hire competent developers in this second rate, overpriced town. It's hard to hire anywhere but this bland shithole would have anyone with half a clue running away at top speed.
Fuck you for valuing long hours and loyalty over actual performance. That one guy who everyone hated and was totally incompetent couldn't even get himself fired. He had to quit.
Fuck you for your mediocrity.
Fuck you for being the only employer for my skill-set in the region; paying just well enough that changing jobs locally doesn't make sense, but badly enough that it's difficult to move.
Fuck you for being the stable "safe" option so that any move is "risky".
Fuck your mediocrity.
Fuck you for being something I think about when I'm not at work. Not only is it shit from 9 to 5 you manage to suck the joy out of everything else in my life as well?
Fuck you for making me feel like a worse developer every day I work here. Fuck you for making every day feel like a personal and professional failure. Fuck you for making me seriously leave a career I love for something, anything else.
Fuck you for making the most I can hope for when I get up in the morning is to just make it until the night.6 -
TM: Hey, do you have a moment?
Me: not really, I'm already overtime and have enough work for the whole year.
TM: Yeah, we know. Just a quick meeting to discuss something awkward.
Me: Hmkay.
...
Later that day:
TM: Yeah. To make it quick - we're confused and bit dissatisfied with how project X turned out. The staging server is blazing fast, but the devs machines seem to be extremely slow... Some devs complained.
Me: No wonder. I said from the beginning that the devs shouldn't do X and Y, and that the dev machines need to be redone after staging is done - as we need to gather hands on experience first, cause no one could explain to me what resources the project actually needed.
TM: Oh. I wasn't aware of that.
Me: I guessed so. You were on vacation at the beginning and I didn't had the time to lead another team...
TM: Yeah... So the dev machines get replaced?
Me: They _could_ be replaced, but the devs would need to reset up their environment, as I and won't transfer the environment of the dev user.
TM: Ah... So they would have to retransfer their personal modifications, if they made any?
Me: Yes. As always, the basic setup just provides the necessary services, settings etc. - stuff like remote IDE settings on the machine, configuration etc is left out and we don't transfer it as it is usually too much of a hassle and risky, as every dev does have his / her own preferences, and we don't want to support every possible configuration out there.
TM: Just out of curiosity... Staging was ready like... Last year?
Me: Beginning of December, yes.
TM: Sigh.
Me: The jolly of having a kinder garten full of toys that no kid wants to clean up...
TM: No comment. The kinder garten Kids might make me a Pinata otherwise.
Me: If only they'd fill us with chocolate first instead of just beating us.
...
Tales of lazy devs, to be continued...3 -
So I just made a throwaway SO account because I had a 'risky' question and I don't wanna loose my 22 hard earned reputation points on my main account.
Maybe it's just me but I think it's very sad that asking a question on SO that doesn't get downvotes is so difficult.
Anyways, if anyone knows about UMDF drivers, here's the question: https://stackoverflow.com/q/...5 -
When you're coding on a VM so slow that it takes at least 5 seconds for eclipse to save your changes, all because company thinks its too risky to have source code on the bloody physical machine
6 -
So I have seen this quite a few times now and posted the text below already, but I'd like to shed some light on this:
If you hit up your dev tools and check the network tab, you might see some repeated API calls. Those calls include a GET parameter named "token". The request looks something like this: "https://domain.tld/api/somecall/..."
You can think of this token as a temporary password, or a key that holds information about your user and other information in the backend. If one would steal a token that belongs to another user, you would have control over his account. Now many complained that this key is visible in the URL and not "encrypted". I'll try to explain why this is, well "wrong" or doesn't impose a bigger security risk than normal:
There is no such thing as an "unencrypted query", well besides really transmitting encrypted data. This fields are being protected by the transport layer (HTTPS) or not (HTTP) and while it might not be common to transmit these fields in a GET query parameter, it's standard to send those tokens as cookies, which are as exposed as query parameters. Hit up some random site. The chance that you'll see a PHP session id being transmitted as a cookie is high. Cookies are as exposed as any HTTP GET or POST Form data and can be viewed as easily. Look for a "details" or "http header" section in your dev tools.
Stolen tokens can be used to "log in" into the website, although it might be made harder by only allowing one IP per token or similar. However the use of such a that token is absolut standard and nothing special devRant does. Every site that offers you a "keep me logged in" or "remember me" option uses something like this, one way or the other. Because a token could have been stolen you sometimes need to additionally enter your current password when doings something security risky, like changing your password. In that case your password is being used as a second factor. The idea is, that an attacker could have stolen your token, but still doesn't know your password. It's not enough to grab a token, you need that second (or maybe thrid) factor. As an example - that's how githubs "sudo" mode works. You have got your token, that grants you more permissions than a non-logged in user has, but to do the critical stuff you need an additional token that's only valid for that session, because asking for your password before every action would be inconvenient when setting up a repo
I hope this helps understanding a bit more of this topic :)
Keep safe and keep asking questions if you fell that your data is in danger
Reeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee5 -
"It is risky to release an app that depends on APIs that you don't control."
Yeah, dude, we also live in the real world.
Better to say: "Your app should handle cases where the third party API is partially or even totally down."
God, some people, they build a wall of rules around themselves and wonder why their skills don't improve.13 -
I fucking hate chained methods. Ok, not all of them. Query things like array.where.first... that stuff is ok.
Specially if it's part of the std lib of a lang, which would be probably written by a very competent coder and under scrutiny.
But if you're not that person, chances are you'll produce VASTLY inferior code.
I'm talking about things like:
expect(n).to.be(x).and.not(y)
And the reason I don't like it is because it's all fine and dandy at first.
But once you get to the corner cases, jesus christ, prepare to read some docpages.
You end up reading their entire fucking docs (which are suboptimal sometimes) trying to figure if this fucking dsl can do what you need.
Then you give up and ask in a github issue. And the dev first condescends you and then tells you that the beautiful eden of code he created doesn't let you do what you want.
The corner cases usually involve nesting or some very specific condition, albeit reasonable.
This kind of design is usually present in testing or validation js libraries. And I hate all of those for it.
If you want a modern js testing lib that doesn't suck ass, check avajs. It's as simple as testing should be.
No magic globals, no chaining, zero config. Fuck globals forced by libs.
But my favorite thing about it that is I can put a breakpoint wherever the fuck I want and the debugger stops right fucking there.
Code is basically lines of statements, that's it, and by overusing chaining, by encouraging the grouping of dozens of statements into one, you are preventing me from controlling these statements on MY code.
As an end dev, I only expect complexity increases to come from the problems themselves rather than from needlessly "beautified" apis.
When people create their own shitty dsl, an image comes to my mind of an incoherent rambling man that likes poetry a lot and creates his own martial art, which looks pretty but will get your ass kicked against the most basic styles of fighting.
I fucking hate esoteric code.
Even if I had to execute a list of functions, I'd rather send them in an array instead of being able to chain them because:
a) tree shaking would spare from all the functions i didn't import
b) that's what fucking arrays are for, to contain several things.
This bad style of coding is a result of how low the barrier to code in higher level langs are.
As a language or library gets easier to use you might think that's a positive thing. But at the same time it breeds laziness.
Js has such a low learning curve that it attacts the wrong kind of devs, the lazy, the uninspired, the medium.com reader, the "i just care about my paycheck" ones.
Someone might think that by bashing bad js devs I'm trying to elevate myself.
That'd be extremely stupid. That's like beating a retarded blind man in a game and then saying "look, I'm way better than this retarded blind man".
I'm not on a risky point of view, just take a stroll down npmjs.com. That place is a landfill. Not really npm's fault, in fact their search algorithm is good.
It's just the community.
Every lang has a ratio of competence. Of competent to incompetent devs.
You have the lang devs and most intelligent lib devs at the top. At the bottom you have the bottom.
Well js has a horrible ratio. I wouldn't be shocked to find out that most js devs still consider using import or await the future.
You could say that js improved a lot, that it was way worse beforr. But I hate chaining now, and i hated back then!
On top of this, you have these blog web companies, sucking the "js tutorial" business tit dry, pumping out the most obscenely unprofessional and bar lowering tutorials you can imagine, further capping the average intelligence of most js devs.
And abusing SEO while they're at it, littering the entire web with copy paste content.2 -
Going to create a couple of cron jobs that delete stuff from database.
What could possibly go wrong? ;)6 -
Fuck this day!
Like really fuck it!
I have one of the most terrible crunch-time i ever experienced.
I’v been working 12+ hours every day with an ever-changing project timeline.
It started simple, we made a timeline, it was risky even then but it was realistic, we started working immideatly, everything looked good then a few days in BOOM! Actually our project management completely forgot client B’s projects soo we need to do that too with the same fucking deadline!!! (About 10x more work in waay less time)
Then this morning i got an email from the graphics team that we need to document our design process RIGHT FUCKING NOW! Because management wants documentations, in the middle of a fucking crunch-time.
Today it almost got physical with my project manager, i told him that he is not a programmer, i dont fucking care about his shit, just fuck off and let me work because we won’t be ready based on his unrealistic bs.
I feel like completely fucked over, like we were told 2 days before deadline that the whole company and people’s jobs depends on us now because if we wont finish this clients won’t pay.
WE ARE TWO PROGRAMMERS for studio of 10-12 people!!!
Soo i’w been thinking about getting the fuck out of here ASAP, i got an offer from a pretty big international gamedev company just what i needed, i already did their test before all of this, i passed A+.
We scheduled a skype interview for today. I had completely no time to prepare or chill off, just got out of the office, got into a starbucks and i’m interviewing. No time to even check my mic or internet, the call was so shit i could not hear anything, they neither because the plaza was loud af. Meanwhile im nervous about work, about the interview, about can they hear me at all because of the noise. I fucked it up. BIG time! I was so done i could not reverse a fucking string in c++ or explain what is a signed int!!!
Needless to say they said no.
Need time to think about it or realize what happened? Nice dreams. Back to the office and continue working.
I can’t do this anymore. My girlfriend came for me and took me home at 10pm but all i could do was stare at the floor on the subway. I don’t want people to lose their jobs but i just phisically can’t do this anymore.
Meanwhile any time i talk to my project manager about being tired he says like “hshshsbsb i have 60 hours in the last 4 days i got the worst part, i would be grateful in your place..” like fuck off dude, i dont give fuck about how you feel about this. This is not okay for me, you did this to the project, your fucking job is to manage it! I have one day off before going back to this, i have completely no idea what to do now...
[ps: this is not Nemesys. They did not let me work on my own stuff because i would be a competitor, so i left.]5 -
IBM decided to change the EOL of CentOS 8 from 2029 to 2021, then continue CentOS as useless RR testbed. What a nice attempt at forcing users into the paid RedHat version.
That's a risky move because Rocky Linux is already gearing up to replace CentOS, and the whole RedHat ecosystem could bleed out to Ubuntu, Suse, and Debian LTS. Well done, suits.16 -
nice, 10k reached before sidtheitclown! (that’s all that actually matters, heh)
so, yes, as promised it’s me… chris from chris’ full stack blog.
I think kiki knew this, as I used to be called fullstackchris… though very briefly... don't know why i was ever worried about the old clowns i used to work for knowing my identity here
i’m a host of react round up, and also an ex-futures trader (that life is / was hidden on Twitter), I’ve recently quit because I’m ALSO still building 4ish SaaS products including The Wheel Screener (wheelscreener.com) and CodeVideo (codevideo.io), over my LLC, Full Stack Craft (fullstackcraft.com)
oh yeah, and on top of that i have a full time job in Switzerland (read: not poor boi 38 or 40 hour work week, 42 minimum)
so yeah, its a fucking lot of shit to do and sometimes it’s too much! glad i have this place to vent
so, don’t be too harsh on me… really, 99% of my bitterness comes from the approximate 5 years of my working life (2018-2023) were taken from me by lying business folk type who actually didn’t know what the FUCK they were doing or talking about, even after promising me they did (at two different companies). Listen, I’m all for people telling me iTs a RiSkY VeNTuRe; i get it. But if you say everything is rock solid (like funding, my future employment, etc.) and it is not, then fuck you; you’re just lying to my face, it has nothing to with management vs employee, engineer vs. non-technical - you’re literally just a *bad person* (sorry, mechanical engineering genes and honesty to the core - sue me) To be sure, I was partially at fault - too optimistic, and too gullible, and I’ve have since learned my lesson. but still working on it. (obviously)
but things are look up - my company is running better than ever, the current job is great with insanely smart people
In the end, it’s always the hardcore engineers who are the most honest, hardworking, respectful, and the best to work with - you people know who you are…
Until then… see you in the next rant!!!! 🤬🤬🤬🤬🤬
Dutifully signed,
🤡14 -
I'd never do anything "risky" in a prod environment if I considered it so at the time, but in retrospect there's *lots* of things considered risky now (both from a security and good practice viewpoint) that were standard practice not long ago:
- Not using any form of version control
- No tests (including no unit tests)
- Not considering XSS vulnerabilities
- Completely ignoring CSRF vulnerabilities
- Storing passwords as unsalted MD5 hashes (heck that was considered very *secure* in the days of plaintext password storage.)
...etc. I'm guilty of all of those previously. I daresay in the future there will be yet more things that may be standard practice now, but become taboos we look back on with similar disdain.2 -
About starting your career at a medium-bigger company that's well-established, versus starting at a smaller company.
That's my point of view:
It's always wiser to begin at a company that's more established (you will also be sure that you will get paid on time). I started at a well-established company, and I managed to buy gear, travel, do stuff, and then I realised that I wanna do more, not only live to work 😎.
Smaller companies are kinda risky, think of it, their goal is to reach the level of a well-established company, which is some levels lower than that. On the other hand, if you do well at a smaller company, your next goal will be to work for a bigger company, which will surely be nicer, more professional and will pay better. So you will have managed to et there with all the skills in your pocket already, which will come in handy later!
Bigger companies are excellent if you have a family (wife and kids), they provide stability, that's the most important thing, but I believe that in order to get "settled" in a company like that, you should at least have tried something else first, like doing your own thing or get challenged in more complicated gigs that require you to up your skills.
In the end, it's all sun and fun, with you code editor by your side 😉. I'm interested to see your opinions.1 -
Why do people suggest using arch when they have many ready to go distros.....?
I've heard that chances for breaking the whole system is high and is risky...
18 -
I want to switch to an encrypted email service. My question, what if the service provider suddenly decides to close down the email service.
I feel like it's too risky to move all my emails to them.5 -
!rant
Super awesome day today.
1. Got up early to do a risky production deploy and it worked!
2. Three PRs approved before lunch.
3. Got some time to continue learning scala.
4. Coffee and cupcakes with some refugees and discussed work as a software engineer.
5. Tried virtual reality for the first time. Really fun.
6. Helped prepare our goals for this quarter and present them to the department.
7. Department meeting had free local craft beer and pretzels.
8. Went bouldering after work and flashed a 6c.
9. Curled up with my wife watching Netflix.
I really love my life sometimes.5 -
fuck it; at 10K updoots i'll reveal my identity
then everyone will know i'm a closet psychopath
it may be risky!
it may be ruinious to my career!
let's do it!21 -
Founder: Are you sure you want to join this startup?
Candidate: 100% sure Sir
Founder: Startups are risky, what if we shut down next month?
Candidate: Sir, I will do whatever it takes to not let that happen
Founder: That’s what I was looking for. You can join at 90% salary cut. That will give us 2 months more runway3 -
Not dev, but a perf-eng confidence boost.
Our company was hired by a client to onboard perf-testing process and do some perf-related go-live stuff. Basically, make sure the app meets the SLAs.
Our company mobilized some internal resources for the task. The had 3-4 months. 2 months later they realized they won't pull it off. What a shame...
When the threat of dropping the ball and losing the client and recommendations became very real, they engaged us. Half the time, half the resources, a worried and annoyed client who now wants to control the whole initiative.
During the first 2 meetings we get the general idea of what they have, what they want. We take some time to prepare a plan to make it on time. The client argues our plan, mostly because one of the main points was mocking downstream dependencies [integrations]. He asks, then demands to do it all with live integrations. We explain why this is an incredible risk and why we should do it the proposed way. He disagrees.
Alright then... Maybe he knows smth we don't. Let's do it the risky way...
A month later test results are far from the target. I did my best with app de-bottlenecking and fine-tuning. But since the live integrations do not deliver, they hide other bottlenecks. The initiative is stuck.
Finally, the client agrees to do it with mocking. But now there's no time left as it will take almost a month to prepare mocks...
The client agrees we should have done it our way from the start. They postpone the go-live and we carry out our testing and tuning the right way.
That was one expensive and long "I told you so". But it boosted our [perf team's] confidence to the top and beyond :)
don't tell us how to do our job, unless you do want extra expenses -
First day back from holiday.
CEO announces everyone the pandemic is over and everyone has to return to the office.
Talked about how good it is to come and crack a joke with a colleague and that they care about our wellbeing.
I have barely been able to even focus on work because of all the chaos in the company since the beginning of the year (many interviews for hiring new devs, company events, meet etc.)
Colleagues talking about the fact that nobody can work from the office given all the chaos in the projects and nobody will come because they can't fire us all.
I have to answer to an outsourcing company today for a new fully remote full stack .NET developer position for the same pay, but might be risky in terms of what I can actually deliver in terms of code.
What advice can you give me? Jump the boat or not?12 -
Idea: postpone risky decisions to the 1st of April and say it was a joke if people don't like it.
~~Or keep them to troll people even harder~~ -
So good to see flash finally be put to pastor. Am I sad no flash sucked from a developer standpoint but even more from a business standpoint! Why? Here’s why!
....Yes it was fast in the sense of quickly getting content out and functioning BUT this ment you are at the mercy of Adobe / Macromedia (depending on the timeframe) for support AND mercy of the company whom create the browsers for support.
Meaning your product is fully reliant on others for existence and can easily not exist if one of two other beings choose.
For developers shame on you for accepting this you should never have supported this.. if you did it was just for a job you are suppose to be experts in your field and when management came to you for guidence you allowed this technology to be used rather than saying no this isn’t good! It’s too risky...
Fuck... how many people choose a career path that made them flash only developers.. well guess what becuase you niched yourself now your out of a job... rethinking now?
CAN ANY OF YOU TELL ME WHAT OTHER WIDLY USED TECHNOLOGY IS RELIANT ON A SEPARATE ENTITY?!
geee it would be a shame if one day that technology was phased out or no longer supported and then a date was picked and boom shutdown... geee that would suck...
I remember for years before it was announced it would be ending ... I said development around flash should be avoided at all costs because of it’s reliance on someone else for your product to function and exist...
Let this be a foreshadowing/ warning... learning experience/ AMAGE.. to those who use similarly situated technologies...
Developers you were warned.
Businesses you were warned.15 -
I’ve been in a sabbatical for the last few months and it’s been incredibly enlightening!
One of the things that I discovered is that I can still enjoy working with computers!! Just because something has been done doesn’t mean that I can do it again. It’s been done, but not by me yet. I’m not claiming is objectively better or anything like that, I’m just saying that is mine!
Together with that I’m also finding out that making things “my own way” is very motivating and satisfying! I don’t think this would work on a team, but it certainly makes programming a creative endeavor, which I think is why it sucks so much to work in the tech industry nowadays! Creativity is risky and dangerous and so, if Facebook became a million dollars company using ______ then let’s call that “industry standard” and do it everywhere, even if all it is is distilled excrements that only works because of the billions…
I guess the bottom line is that I’ve found out that I like programming because I’m a creative and places that force me to program while killing my creativity are both toxic and miserable… and I never wanna go back! -
I'm working in a really really small start up company (I'm the only developer here with the owner being a programming professor in the local uni).
It's my first job after leaving uni and I knew it was a risky decision that I've made but it was my hometown and I could save some extra money by saving on rent and food, also I've always loved a good challenge.
But the challenge isn't working as excepted. It's been a year since I've started here and there was no planning for almost nothing, it's a "do as you think it's best but I'll probably won't like so you have to it again" kind of methodology. Also I've been hire to do an hybrid mobile app and I've ended up doing a full e-commerce website with shitty outdated technology that I've had no experience in using.
So for me I'm more than done. I'm tired of having my suggestions being completely ignored, of the lack of planning and instruction and the fact that I'm being underpaid for what I do.
Fuck it, I'm looking for a new job.3 -
I think another intriguing job asides programming is engineering (*for some*). A week has past and I've been on the hike assisting my beloved brother on his contracted engineering job while I am less occupied. The job is based on 🗼Tower analysis and It's quite risky as you'd have to climb up to 56 meters high just to take readings of antennas, and fix some other stuffs. The only thing I find intriguing about this job is his love for it, funny enough he also thinks I love the job too and I guess I'm guilty for his thoughts (*Sorry bro, I love the job for you not me*).
With my little experience so far on my *new brotherly job* I noticed the most hectic task isn't going up and down the tower taking readings but at the end of all operations, he'll have to gather the values and snapshots he took while on the tower to prepare reports on msword & excel for the other buttwags at the office (or home I guess)
then archive and sends via mail. Seeing this lengthy process I was forced to ask why he wasn't using any reporting tool like Jotforms or any other equivalent and I was willing to look up some recommendations for him, his reply was: "I'm already used to this form of reporting, its what I was trained with and what the company provided, nevertheless a friend of mine suggested something of such weeks back but I would have to pay monthly fee for its usage which is quite on the high side and I don't think I'd prefer that."
Sounds convincing but not enough, okay here is another deal: You use an android phone right? and at my office we work on system automation (*basically does not know what I do for a living probably thinks I'm a hacker the illegal one*), how about i design you an android app for you to capture the tower data and a PC software for you to auto generate the msword & excel reports, I can get this ready for you in less than 5 nights (*I've got less task on my desk, and was willing to take the timeout to prepare the solution that he needed, all I needed to hear for a kick start was an "Okay" just to be sure he wants it*) I suggested and re-assured but up to this point he still declined my offer and is willing to stick with his current reporting pattern (*Me died*).1 -
<sanityCheck> //asking for a friend
Some clever b*****ds wrecked a section of our production mysql db. To fix it I need to rollback the affected records 2 weeks - around 50/300 tables are affected, the other data must remain intact.
Currently my plan is to take a 2 week old dump and cherry pick the data I need from it, then combine it with a dump of the db in it's current state, drop the db and recreate it.
I know this approach will work - but it's risky, a pain in the ass and dealing with 300mb text files is tedious so since I only need to start in around 8 hours I figured It wouldn't hurt to post my approach and see if anyone thinks my plan is borderline retarded.
If you have any advice .etc that will make my life easier I would greatly appreciate it.
So in your opinion...
- is there a better/safer way?
- do you know of any db dump merge tools?
- have a recommended (linux) text editor for large text files?
- have you made any personal mistakes/fuck ups in the past you think I should avoid?
- am I just being a moron and overthinking this?
- if I am being a moron - In your humble opinion has the time come for me to give up all hope and pursue my dream of becoming a professional couch surfer?
</sanityCheck>
Note: Alternatively, if your just pissed that my rant is asking for a solution instead of simply trashing the people that created my situation and your secretly wishing it was on SO where it belongs so you can moderate/edit/downvote/mark the shit out it, feel welcome to troll me in the comments (getting dev advice just doesn't feel reliable without a troll - you matter to me). Afterwards If your panties are still in a bunch I'll post it on SO and dm a link to you to personally moderate - my days already fucked and I wouldn't want to ruin yours too.4 -
!tech #off_my_chest
when I look back to the earlier years of my life, I see nothing but loneliness. I had no friends in school, people didn't sit with me, only a few people barely talked with me and it was a mess.
I used to blame my parents for it: I thought they isolated me in a lot of areas which lead to hampering my growth and relations.
However, I recently got a taste of my old days and realized the root cause of the problem: DISEASES.
I used to be a very weak and sick child. I had extreme cough so much so that i will go on coughing for 1 min in every 2 mins. Cough hasn't touched me in last 10 years, but recently i caught cough again and it lead to a whole lot of revelations.
I currently have a good social network. I have one friend from past 10 years with whom I used to goto the park every day. I took off this park routine for 2 days citing sickness and he was worried. So once I felt better on 3rd day, i went to the park with him. While walking I again started coughing (albeit very less), but I could notice his expressions. he wanted to just get out of this whole situation. Next day, he didn't even bothered to message, and when i did, he started making excuses.
I had another group of home friends, who are so close to me that we went for snacks at any random time on any random day. Last year i went onto 3 road trips with them. but last weekend they straight up declined meeting me saying get better first.
---------------------------
I don't blame any of my friends or parents.
no one wants to be around a sick person, thinking that if the situation worsens, then the ill guy might need help that they couldn't provide, and if the situation went out of hand, then they would be the one to blame. And it's not just my illness, I think this might apply to anyone with an illness or a disability. everyone treats them as liabilities or time ticking bombs
Everyone wants to be in a homogenous group of healthy people with no one having any life problems so everyone could enjoy a movie life.
Guess what? THAT'S NOT HOW LIFE WORKS!!
People are at different stages of life in terms of age, knowledge, power, health, and finances. in a group of 5, if people come together to watch a movie, there maybe 1 person who is giving away his evening's dinner money for affording the tickets. another might be missing out on her sick grandma or office work just to be part of this one gathering for 3 hours.
And regarding ill people, we are not your responsibility once we are out of our patient bed!
I understand that I might need my friend's help in calling my parents or an ambulance if the situation worsens, but isn't that normal for healthy people too? what if 2 guys are walking on the street and one is hit by a car? won't the other call the ambulance?
And suppose My friend is not able to the help I needed, would I blame him for it?
NO!
Absolutely no! It was my decision to go out and meet people even when sick even if it was a risky move. Life only goes forward if we take risks. But if it backfired, then the instance where he was not able to help would be much less significant than the instance where i decided to get up and go out. That would be the only major blame area and the only person to blame would be me, myself!
The sick is just an inconvenience on people's souls, that's it.
--------
This whole experience makes me so worried about my office and professional situation. I am an excellent engineer working from home and this WFH has helped me keep my cough from worsening while working in a professional capacity.
But our office is shifting to WFO and that is a concern.
1. being in a different state, and working in office takes so much attention and focus that i often forget eating lunch or going to washroom. idk how i will treat my sickness if i got sick there.
2. being in home, i can do my work without bothering other people with my cough. at office, people will want to sit away from me and that ewould be not possible. eventually i would be forced by people to take leaves to "get better" as am bothering everyone
3. if i don't get "better" soon, which is there definition of being healthy enough to come to the office without any sickness (even though my illness doesn't hamper my efficiency), they will fire me .
i am royally fucked. even when i get better, WFO will always have a negetive factor like this. for cases of self illness, family illness, parents illness, if you are not being an 'office' slave (just being the 'work' slave isn't enough), you won't get the money4 -
Resizing my partitions without backup and moving them between disks.
Never had a failure but i guess it could be risky3 -
I had a jobinterview this morning at a small startup, that doesn’t even have clients yet. That sounds too risky to be in right now3
-
Anyone else here having health issues getting in the way of our hobby? I understand that our field is risky. Any actual advice you can give that you yourselves did to be healthy again? Thank you so much.9
-
I was sitting down at my desk today, pissed due to some more lack of coffee, and wondering about my future.
It came upon me that I absolutely despise what I am currently doing (job wise). There is a part of me that tells me that things are going to be alright, but that is just some nonsense that my mind makes up to rationalise how terrible it actually is here at this company.
I think that perhaps my abhor for my current position is a little more directed to the people and company that I work for, but I am really just fed up.
I have found quite a liking in terms of web-design. The clients and the work is a lot less stressful than what I am doing now - and I actually enjoy what I am doing. It is nice to see something come to fruition.
Perhaps that's the way to go? God decisions are fucking risky.1 -
Risk is part of my everyday life.
I take the risk everyday when opening IDE and changing line of code that can either break database or crash other systems that are depending on one I am developing. ( not instantly but in some time in the future )
So....
Many years ago I was updating some application server production code while being drunk.
Everything went fine except me waking up in the morning and didn’t remember how I did it.
... what I learned from my developers life except that heavy drinking and updating servers is not the best idea ?
First, don’t give a fuck, do your job and ask questions even if the person in front of you said that understood everything and you think you understood all of shit.
Second, if you think you know what to do think twice.
Third, having any backup, any tests and any documentation is always better then having nothing.
And the most important.
The most risky in every business are people around you, so always have good people around and there would be no risk at all or you won’t even think about it.
✌🏽 ❤️ -
Let me just say that I've been playing whack a mole with a new feature for while now. And it's becoming very tiring.
TLDR; CTO is changing the way we're going to implement this, every other day.
June 1st,
CEO: let's implement feature AAA,
CTO: we're going to have a call with Andy to tell us all about his product that will make this super easy, call will be June 4th.
Days before June 4th,
Me: Researchs product X, makes demo works flawlessly.
June 4th,
Call all good, few tips from Andy. We come to the pricing section of Product X
CTO: this will not work, pricing doesn't fit on our budget, fair enough.
June 7th -11th
Me: research altenative approach. Makes second demo.
CTO: Works good, seems to have too many moving parts, let's have call with Bob to check Product Y. It should make our lifes easier.
ME: Geee, ok let's check it out.
June 14th,
Call with Bob, all good, product has a fair price, stuff is experimental.
CTO: let's use Product Y, and just use what we get from their api now, and worry about changes later.
Me: Hmmm, that's a bit risky, but ok, you the boss, right?, starts again new demo. API doesn't work as documented.
Lots of trial and error to figure out how the api is working now, finally demo works well,
June 17th,
API changed, now it works as documented, (expected as it is experimental), previous demo doesn't work anymore.
June 18th,
Redoing research. inputs are completely different from Product Y now, need to redo all that is working and do and a lot more of research.
Go live is scheduled for end of next week, I hope that the API is stable now, and that I get to go live on schedule.
It is funny to see, that it would probably been the same if we just waited on the API to stabilize, and check the pricing section before choosing a product? Who knows.
Anyways, I actually feel happy that over the years I developed the patience to work with ever changing situations like this one.4 -
!tech
I have this bad habit of never taking decisions without discussing. For risky, highly impactful decisions, ig this is a good approach, but when you are trying to be a host, or taking some very basic decisions like ordering food, or booking a time slot, i would ask opinion of all the parties involved.
I sometimes cross the line of being considerate to being bothering, irritating and unreliable with my debating nature.
I Don't know why but i for every situation i feel having a second opinion is necessary and good.For eg, Once i was my sister and our flight got cancelled due to bad weather.
I had to choose : either take the next available flight booked by the same airlines for free, which was around 26 hours later, or book the next flight from another airlines which was in 2 hours but costed twice. we were in a different state, and my middle-class/opportunity deprived brain was seeing a path for both choices, but i thought of consulting sis and she lost her mind. she got scared, she started regretting all our choices, the airway travels , everything.
if i had just taken the decision of going with the 2 hour late flight, i would hav saved myself from so much drama.
How to fucking man up in a decision making situation?8 -
Never fixed? lol.
Maybe I took hell of a time, maybe I've ignored it for long but at least I've always fixed bug which I came across and will fix if I come across any new (as there might be many hidden :P ).
As I mostly work on eCom and integrations, it's way too risky keeping bug.
Cheers!! -
Opinions on buying an old unsupported android phone?
Say I'd buy a galaxy S7 thats no longer supported or even an S8 that soon will be unsupported and don't plan to use a custom ROM.
How bad would that actually be?
I know it'll lack security patches, but how risky is that?7 -
!rant
What is better? Stable but boring company(currently working here) or risky but intressting job(small company can fail or grow).
If the company grows the pay can get a lot higher then the current job offers.
I'm struggling with this question for couple of days please help fellow devs.4 -
Best: leaving Job in just 6 months to start freelancing.
Worst: yet to make :p, probably I'm planning to stop working for masters or moving to Geemany from India for on site project. And both are pretty much risky 😅 -
Living abroad during corona times is shit. Trying to visit the family back home...
2019: it's too risky, I won't chance it
2020: still too risky, I won't chance it, even though technically I can now
2021 - Jan to Oct: I can go now, but I can end up getting stuck at the other side. I'll wait just a bit longer
2021 - November - right, quick, I'll book just THREE short days to say hi to the family...
BOOKED
2021 - days later: LOCKDOWN AGAIN MOTHERFUCKER! Your flights are GONE! Try again next time fool!2 -
I just thought about shelfing the progress of a colleague that always leaves his pc unlocked and resetting his branch to the last release locally.
But that would be a bit too harsch and risky. -
How do you go about finding work in the tech industry, to me it seems far harder sell then anything else?
Right now I’m struggling to get new business in since I do websites and apps
It seems because it’s niche and it’s a lot of money to put down it’s a risky sell to someone you don’t really know.
I believe my sites are quite good and I get decent feedback from customers telling me they get good results from their new site
🤷♂️ so I’m a bit at a loss -
Switched from recording based automation tool (ranorex) to script based (puppeteer) for a web app. Risky because everyone was against this and I had to deliver.
-
Which ons is less risky and which one Is most profitable to succeed ?
0- telling the admin you forgot your password and as he's logging in, sniff his password (you already placed sslstrip)
1- gain access to router using its vulnerabilities and redirect the traffic to a fake page and get the password.
2- exploiting smb port of admin's system and placing a krylogger or stealing his cookies if available
3- brute forcing admin password :/
4- pressing forgot password on admin account and staying close to him and sniff the SMS containing the otp using rtl-sdr (and of course you will be prompted to set a new password)
5- any other way .
Also the website itself is almost secure.
It is using iis 8.5 and windows server 2012
Only open ports are 80 and 443.5 -
I don't know if this counts but wrote a generator that replaced a shitty linq to sql dal to use our system so I didn't have to mess with a web app I'd written. In place replacement with a few methods that made the other transaction lock field updates and calls etc
Most risky I can think of
Everything else was data migrations but there were always backups1 -
so what will you do if a company is offering you a job and you have a 60 day notice period? (assuming that the said company hasn't asked this question before/during the interview process)
seeing the current market situation, it seems very risky since the new company is obviously going to keep searching for backup devs who might show up before your joining date.
meanwhile it will be very awkward for you to work during your notice period since 60 days is almost a financial quarter and you are the notice period guy, so you might end with non important tasks
what will you do?5 -
Finally purchased my t480s for university after mooonths of reading reviews and reddit posts. I hoped that the mbp refresh wouldn't be so expensive :( I've got a mid 2009 from work which no one used so they let me take it home and yeah to be honest i like it very much. i wanted learn programming for ios & android, but honestly paying 2,3K€ (student price for the 13" i5 16gb ram 512gb ssd) and having the risk of a (maybe or maybe not) failing keyboard and no chance of upgrading it is too risky for me and my wallet :( I paid 1,5K€ (again student price) for the thinkpad (i7 16gb ram 512gb ssd and the mx150) and i think i'll love it :)
Just wanted to share with you guys :) (i hope i didn't start a pc vs mac fight haha)2
Top Tags
Weekly Rant
View