Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuckBuy Now
Search - "don't trust tech"
I was offered to work for a startup in August last year. It required building an online platform with video calling capabilities.
I told them it would be on learn and implement basis as I didn't know a lot of the web tech. Learnt all of it and kept implementing side by side.
I was promised a share in the company at formation, but wasn't given the same at the time of formation because of some issues in documents.
Yes, I did delay at times on the delivery date of features on the product. It was my first web app, with no prior experience. I did the entire stack myself from handling servers, domains to the entire front end. All of it was done alone by me.
Later, I also did install a proxy server to expand the platform to a forum on a new server.
And yesterday after a month of no communication from their side, I was told they are scraping the old site for a new one. As I had all the credentials of the servers except the domain registration control, they transferred the domain to a new registrar and pointed it to a new server. I have a last meeting with them. I have decided to never work with them and I know they aren't going to provide me my share as promised.
I'm still in the 3rd year of my college here in India. I flunked two subjects last semester, for the first time in my life. And for 8 months of work, this is the end result of it by being scammed. I love fitness, but my love for this is more and so I did leave all fitness activities for the time. All that work day and night got me nothing of what I expected.
Though, they don't have any of my code or credentials to the server or their user base, they got the new website up very fast.
I had no contract with them. Just did work on the basis of trust. A lesson learnt for sure.
Although, I did learn to create websites completely all alone and I can do that for anyone. I'm happy that I have those skills now.
Since, they are still in the start up phase and they don't have a lot of clients, I'm planning to partner with a trusted person and release my code with a different design and branding. The same idea basically. How does that sound to you guys?
I learned that:
. No matter what happens, never ignore your health for anybody or any reason.
. Never trust in business without a solid security.
. Web is fun.
. Self-learning is the best form of learning.
. Take business as business, don't let anyone cheat you.20
I am trying to understand something for a while. devRant is full of privacy advocates and to be honest, part of it is almost taken by a group of people that call other people random swear words people because they are using a particular product of a company.
I will raise some points and will try to discuss them with other people in comments.
I will stick with Google. Since it looks like it's the most hated one. A company that has built one of the most intelligent infrastructure, the most popular mobile operating system and of course, the best search engine currently available.
The problem everyone sees is the privacy. Google tracks the search history to give users a better experience and show relevant ads. You might not need this "better experience". In case you don't know, you can turn off personalized search any time to make sure Google doesn't track. Same goes with Google Chrome, you can turn off all the data it is sending to servers in settings. You can simply not sign in if you don't anything to be synchronised.
An argument is Google should be opt-in rather than opt-out. But the general users are not tech-savvy. And yes, going to settings and turning on personalised search is a lot of work for a huge amount of people. Trust me, I worked in IT before. If they find other search engine giving them a good experience without changing anything in the settings, they will just simply move to that engine.
What interests me most if how people back DuckDuckGo. First of all, not all parts of DDG is not open source (it's fucking not, you can argue all day). Parts of it is closed because of licensing issues.
That is perfectly fine to privacy community. But it's not when Chrome is closed source for almost the same reason. I mean when you're using DDG, you are supporting a US-based company that has privacy all over its face and using closed source application on their server. Have you not learned anything from history?
You might be wondering about my obsession with Google. It hurts me when I see a giant company whose popular software is open source is bashed like this. Google has made huge contributions to open source communities. Chromium, Android, Kubernetes, Angular, GoLang, TensorFlow etc.
And PRISM, how do you know that DDG is not part of it? it's US-based after all.
I just saw an article that used a video with a title "TNW - Aral Balkan - Free Is A Lie | The Next Web" while asking us to switch to DDG. Ummm....DDG is also free right?
Maybe we should raise concerns with the US gov first rather than Google.66
Wtf, really??? Are they trying to liyerally KILL ME????
Got home from hospital today wth my family. Baby got sick. Wife also caught cold... Bad news. It was just me still healthy like a raddish [we have such saying].
So I got home. Started feeling somewhat funny. Sore thighs, feeling nauseaus, chilly, a bit dizzy.
10 minutes later I'm fucking trembling! It felt as of I was kicked put bare ass to -20C outside! I'm not exaggerating [probably made some typos.. Pls correct me] - i live where winters get like -35C. Everything around got like twice darker. And my lower teeth got itchy af [NOT the best feeling, trust me].
I must have caught cold too - I thought to myself, cuz I know what these sympthoms mean. I always have 'em all when I have fever. Since shivers are caused by rising fever I got my Microlife remote thermometer out of my drawer. Click, blue light, wait, beeep. 36.5C. Allright.. Maybe I got it wrong... Try again -- same result. Wife also gave a couple tries - nada. Nil. Nullpointerexception. Healthy like a pickle!
10 minutes later I couldn't stand the cold. Got under my blankets wife made some soup, tea,... I still have this analog thermometer, the one with quicksilver. Pop it into my armpit - jusyt in case. 10minutes later I take it out. It says 39,5 and rising. Try the microlife again. 36,5. WHAT THE FUCK?????????
If I weren't so fond of old-school stuff I'd be in a fucking ER now!!
Fuck you medical digital equipment made to be used at home! FUCK YOU!!
Do you folks kbow where could I get those q-silver thermometers? Just in case. They're already out of matket in my area for quite some time... For being dangerous [i give 'em that, okay?] and.... Lisen to this.... "unreliable"!
I'm sick of this stupid tech world.
Don't get me wrong, I love tech. I just can't stand anymore the global brainwashing that we're part of.
Think about all the huge companies making profit on our data. For a better service, yeah sure, but do we really understand what the cost is?
Ok sure, you don't care about your data because you trust these companies and the advantages are all worth it. What about the fact that we are all forced to buy the next new smartphone after 2 years?
Like if removable batteries were a problem for us, users. Or like the audio jack. Because now someone decided that the pricey wireless headphones are Just What You Need™.
Do you think you own your smartphone?
No, you don't. You are paying a bunch of money for something that soon will be just a useless brick of glass and metal which you can't repair. But you'll be happy anyway.
Someone is so happy to the point that they will defend their favorite company, doesn't matter how they decided to stick it into their ass.
Open your eyes, you've been brainwashed.25
Want to make someone's life a misery? Here's how.
Don't base your tech stack on any prior knowledge or what's relevant to the problem.
Instead design it around all the latest trends and badges you want to put on your resume because they're frequent key words on job postings.
Once your data goes in, you'll never get it out again. At best you'll be teased with little crumbs of data but never the whole.
I know, here's a genius idea, instead of putting data into a normal data base then using a cache, lets put it all into the cache and by the way it's a volatile cache.
Here's an idea. For something as simple as a single log lets make it use a queue that goes into a queue that goes into another queue that goes into another queue all of which are black boxes. No rhyme of reason, queues are all the rage.
Have you tried: Lets use a new fangled tangle, trust me it's safe, INSERT BIG NAME HERE uses it.
Finally it all gets flushed down into this subterranean cunt of a sewerage system and good luck getting it all out again. It's like hell except it's all shitty instead of all fiery.
All I want is to export one table, a simple log table with a few GB to CSV or heck whatever generic format it supports, that's it.
So I run the export table to file command and off it goes only less than a minute later for timeout commands to start piling up until it aborts. WTF. So then I set the most obvious timeout setting in the client, no change, then another timeout setting on the client, no change, then i try to put it in the client configuration file, no change, then I set the timeout on the export query, no change, then finally I bump the timeouts in the server config, no change, then I find someone has downloaded it from both tucows and apt, but they're using the tucows version so its real config is in /dev/database.xml (don't even ask). I increase that from seconds to a minute, it's still timing out after a minute.
In the end I have to make my own and this involves working out how to parse non-standard binary formatted data structures. It's the umpteenth time I have had to do this.
These aren't some no name solutions and it really terrifies me. All this is doing is taking some access logs, store them in one place then index by timestamp. These things are all meant to be blazing fast but grep is often faster. How the hell is such a trivial thing turned into a series of one nightmare after another? Things that should take a few minutes take days of screwing around. I don't have access logs any more because I can't access them anymore.
The terror of this isn't that it's so awful, it's that all the little kiddies doing all this jazz for the first time and using all these shit wipe buzzword driven approaches have no fucking clue it's not meant to be this difficult. I'm replacing entire tens of thousands to million line enterprise systems with a few hundred lines of code that's faster, more reliable and better in virtually every measurable way time and time again.
This is constant. It's not one offender, it's not one project, it's not one company, it's not one developer, it's the industry standard. It's all over open source software and all over dev shops. Everything is exponentially becoming more bloated and difficult than it needs to be. I'm seeing people pull up a hundred cloud instances for things that'll be happy at home with a few minutes to a week's optimisation efforts. Queries that are N*N and only take a few minutes to turn to LOG(N) but instead people renting out a fucking off huge ass SQL cluster instead that not only costs gobs of money but takes a ton of time maintaining and configuring which isn't going to be done right either.
I think most people are bullshitting when they say they have impostor syndrome but when the trend in technology is to make every fucking little trivial thing a thousand times more complex than it has to be I can see how they'd feel that way. There's so bloody much you need to do that you don't need to do these days that you either can't get anything done right or the smallest thing takes an age.
I have no idea why some people put up with some of these appliances. If you bought a dish washer that made washing dishes even harder than it was before you'd return it to the store.
Every time I see the terms enterprise, fast, big data, scalable, cloud or anything of the like I bang my head on the table. One of these days I'm going to lose my fucking tits.10
Applies to: instructions, signs, traveling to new locations, arriving on time, etc.
1. Always read the documentation before asking questions.
2. Ask for clarifications as soon as possible.
3. Never underestimate the complexity of a task even when it looks simple. (traffic)
4. Always test the current application before adding a new feature. (shortcuts, baggage, companions)
5. Never trust everything the previous developers say about their code. People forget. See for yourself.
6. No, you will not remember what this part does. Take notes, write comments, docstrings, and give objects reasonable names. (that hookup has a name and is someone's child)
7. Get things working way before the deadline. (check-ins)
Applies to: talking to people, being precise, etc.
8. Don't turn the method definition into an essay.
9. Break things down into smaller pieces, if possible.
10. Avoid misspellings. The computer may not get confused but the next developers will.
Applies to: communication, relationships, etc.
11. Be considerate.
12. People in higher positions make mistakes too.
13. Communicate. Don't expect people to read your mind and don't assume you have all the information you need.
Applies to: utensils, sex toys, compatibility, sexual preferences, etc.
14. Don't do random hacks just to make something work. If it's not the tool for the job, use something else. Wasabi doesn't make a good lube.
15. Product owners and users don't always know what they want. ;)
16. Stop being an asshole unless you have lubes and da hole tyt.
17. Be assertive, not aggressive but spank and choke me anyway.
18. Consider each sprint as a sport. You may have almost killed each other during the game but keep it civil after. (violent love-making)
19. Don't burn the bridge when leaving. Someday, they can refer you to a better job or you can refer them and get money out it. (hookups and prostitutes)
Applies to: beliefs, religion, obsessions, hobbies, etc.
20. Programming languages are not cults. Same with IDEs, tech stacks, etc.
21. Use linters. (check yourself)
22. Be aware of your own bias especially when testing and debugging your own code. (reflect)
23. Being antisocial does not make you a better developer. Stop romanticizing it. (delusions)
Applies to: life in general
24. Be patient. You'll get out of the maze. You always do.
25. Stop blaming inanimate objects for your code not working. Behind every inanimate object is a person responsible for the failure. Most of the time, that person is you. If not, talk to the person and solve the issue.
26. Take breaks.
27. Keep learning new things.
Applies to: negotiation, transactions, relationships, etc.
28. Always send documented proof of requirement changes. (50 shades of grey contract, ew)
Applies to: sex
29. Write tests. Test your tests. Testes. Testicles. Tentacles. Testicular cancer.
30. Hostility never results to productivity. Wank it out, get back to work, and stay calm. (doms in BDSMs are gentle creatures)5
Recently at my work everyone got all hyped about blockchain. I've spent years studying it and especially crypto so I like to think I know a lot about it. Now every time some feature is discussed (like tracking video views) someone non tech shouts out "Oh we can use a blockchain!" And I have to spend half an hour convincing them why it's a bad idea in this particular case. Like we don't need to share that data, we don't need to ensure integrity without trust etc. I mean a blockchain is a great piece of tech but please stop trying to apply it everywhere...
It's like people think that the blockchain features at its most simplified level don't work anywhere else. E.g. as if stuff you put into MySQL suddenly changes because data integrity is not a 'feature' in that sense...2
There is this dude called Richard Eng which is sort of famous for 2 things:
First: he is known as *the* Smalltall evangelist of mothern times. And he constantly writes about it. Which is fine since he tries to attract new users to this beautiful and simple little language.
The thing is, saying "use this because that is shit" is never going to convince a community, specifically one as potent as that of the JS community. And to make it worse...the dude links his reasoning about bad languages to articles he wrote. As in "this is shit, look at my completely biased article regarding why its shit"
Once he is confronted about it he links back to his own writings. Much like christian fanatics do
"good is real because it says so in the bible"
"but how can you trust that resource?"
"Because the bible is the word of God"
"and how do you know?"
"Because it is in the bible"
Circular arguments like that cannot be taken seriously. And what this guy does for the Smalltalk community hurts more than it helps really.
Claims like those are all around us. If we were to believe or consider them depending on who said what then we would never have the amazing cluster of tech choices that we have.
Take c++. It is absolutely powerful and gives you the ability to do pretty much anything. If we were to take Linus Torvalds's word about it being shit and only having subpar development we would miss on absolutely powerful tools.
The same came to me from Evee, writer of "PHP a fractal of bad design" or the "Node.js is cancer" article.
You are never going to please anyone with anything. I go by live and let live, and whilst I don't like some technologies I certainly don't look down on those that do.4
If they followed my suggestion and went straight to debugging the server issues they would have been solved it from week 1 and everyone would have thought the migration had a minor performance hiccup. In fact, we have already done such at least twice before and nobody batted an eye.
Instead they self-labelled the migration a failure on first error, setting the stage for apologizing to the client, and put themselves on the spot for a whole staging / production signoff, replication / backup worfklow, almost a blue-green "seamless" deployment reminiscent of DigitalOcean.
Well they're not DigitalOcean, and anyone who has spent any time understanding users knows they will not participate in "new system" tests long enough to find or report issues.
So of course the migration stretched out to almost three months up until the whole reason for the migration - the rapidly escalating risk of the old provider disappearing - hit like a freight train and now they have to go through the problem of debugging the server like I told them to on week 1. Only this time they've set the client mindset against it, lost any chance of reverting, have had grave risk for data loss, and are under pressure to debug other people's code in real-time.
This is why I don't trust devs to do ops. A dev's first solution to any problem is to throw tech at it.