Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API

From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "painful"
-
So I just found out that my colleague who I often have to work with does not use a debugger to troubleshoot any bugs at all. Actually, he does not even run or test his code locally either with prints or something similar. He just commits java code directly on bitbucket, no source control, without making sure it compiles and then he runs a CI provided by devops that takes 4 freaking hours to run because he bloated that shit up somehow.
I suggested politely to help him find a more efficient approach and to use my hardware setups for speeding up his work because I assume it must be pretty painful to work with, but he just refused.
That and those "seniors" with 10 years Linux development XP in the embedded field who don't know basic commands like ls, cat and touch and code in notepad.
Fucking me, who the hell am I working with and can someone please end me?6 -
It's nice wanting to follow the best practice but many Java programmer have the bad habit to overdo it making lasagna code which causes painful headaches to who needs to maintain it afterwards. This is just a little sample of the "paranoia driven development" many does in my company.15
-
Reading 3GPP standards is so painful. I download a document to read it. A month or so later, an updated version is out. I need to download it again. It's so annoying to keep checking. I guess I'll have to write yet another script for yet another fucking problem.
The documents themselves are not that good too. My work would be a lot easier if there is a web interface for the standards.3 -
Officially graduated today
20.10.2022.
After 6 painful years
BSc computer science
Shit was tough as fck
Defended my thesis with grade 10/10 (or A in ur american grading system)
...
What do i do now i feel so lost25 -
Yes yes yes
Let's spend countless hours writing painful spaghetti that generates a financial report, extend that spaghetti for specs, then not bother to check the amounts or status. or where it says the money went. Nope, checking non-unique names is totally good enough. We're so good at this. Ten points to the legendaries.
Let's also make the object factories not create the objects correctly, and make sure that report includes entries for orders that don't include any actual payments. Oh, their status? "Ready to send" of course! Let's send that totally valid $0.00 to nobody!
Oh, but Root. Root, root, root. You can't ADD payments to this. no no no. if you do, it'll break specs everywhere else that uses that factory! Shame on you for suggesting it.
Pssh, now you want to make a payment just for this report? Why would you do that? Our best devs have been working on this for years! What could you possibly know that they don't? No, they're perfect. Don't touch them. Just make them better, okay? No take, only throw!5 -
i was hired to join a team of old devs (40+) in an unnamed European country "yay goodbye 3rd world it's time to enjoy the quality of life" assist with enhancing already existing software and creating new solutions.
prior to my arrival most things were slow and super buggy, looking at the code base it shouldn't be a surprise, amateur hour everyone, logic implemented that is not needed, comment driven development, last time code review was done back in 1996. lots of anti patterns.
i swear there is a for loop that does nothing but it loops through a 100+ elements list, trunk based development with tfs since git is "not really needed"
test projects are not there.
>enter me an educated fool, with genuine passion for the craft and somehow a decent amount of knowledge.
>spent the last year fixing stuff educating people on principles and qualities.
> countless hours of training and explaining. team is showing cooperation, a new requirement comes in to develop with react.
> tear my ass creating reusable shit and self explanatory code with proper naming etc using git with feature branching, monday is first deployment day.
> today a colleague was working on an item submit a pull request and self approve it
> look at the code..... WTF the dumb fuck copied and pasted the whole code from different kendo components but somehow managed to refractor the name to test component, commented out all the code that he didn't use did the api call directly from the component, has 2 useeffects that depends on the a fucking text box changes for no reason, no redux implementation, the acceptance criteria is not achieved, and it doesn't work it just look right.
> first world country shit cannot scold, cannot complain, lead by example.
>asked him why you did this, the response was yeah probably i shouldn't have done that, i really didn't understand anything in the training but didn't want to waste time!!!!
> rest of the team created a different styled disaster with different flavors they don't even name their shit the same way.
fellow developers I'm stuck in a spaceship with a bunch of imposters, seriously i never cried in my entire life now I'm teary and on the verge of a break down.
talk with management "improving needs time" and offers me to join a yoga session to release the stress as if reaching nirvana would deliver shit on monday.
i really don't know what do is this a rant, is this a cry for help, I'm not sure, any advice is welcomed.7 -
House search has never been as painful as 2021. Not only the websites are shit at stopping agencies from outright lying on their websites, but also they can't even give you a quicker browsing experience. All the click click clicks just to view one fucking option. Duplicate advertises, photos from "a similar apartment", no 3D showing, no blueprints, etc. , and all in all, awful experience all around that nobody cares to fix. 😒8
-
Almost a year and a half. I was so overworked and my failures were so impactful. I would go home and obsess over work all evening and have fever dreams on nights that I could sleep. It was so mentally painful that I was going to jump off a building after a few drinks to make it stop. A military turned civilian doctor told me that I showed symptoms like soldiers in prolonged conflict. He told me “quit or it will kill you” without even knowing about the suicide stuff. So I quit the job and to this day still suffer flashbacks and have crazy mood swings.
Burnout is real. Dangerous stress is real.4 -
I had some fun with ChatGPT today. I wondered how good its problem solving skills are. Turns out, it's no better than an entry/junior dev armed with all the docs out there - it knows what's written there, how to use the thing (language/framework/tool/etc.), but it has no "understanding" neither of the problem nor the tool, in a holistic way. It's got the knowledge, but it neither has the skill nor understanding of how/why to use it to solve a problem (any problem beyond plain simple complexity).
So the problem I asked it to solve was related to this one I had: https://devrant.com/rants/6312527 .
It was painful to troubleshoot this problem with ChatGPT. It kept on focusing on this particular problem and reacting to errors while trying to fix its initial solution. It took us a good while. Eventually, it reached a working solution, but it was an ugly, convoluted approach that was not feasible to cover my use case with.
FWIW I think it is interesting to follow its line of thought. Eventually, a pattern emerges of how it tries to solve the problem. And it reminds me a lot of myself on the first week in the IT field :)6 -
After many painful hours of fixing cmake errors, I've managed to successfully build 2 large C/C++ projects in a week. That shit hardens you.3
-
This is not joke but fact
More than a year ago I write code without tests, I must confess its frustrating trying to debug without proper testing. testing is painful I must admit but you can't compare the confident you have on your code with the pains when writing tests.
About a year ago I wrote a whole software without tests and this words from a friend hunted me everyday till date he said, what cannot be tested cannot be trusted. Wise words.7 -
Hot tip: if you are a company, don’t ever ever ever ever spend your money on an Optimizely academy course. They have the worst course material I have ever seen in my life, and the material is outdated by several years from exercise to exercise. And the training videos are literally just a recording of a live class with a couple students. They should pay me to sit through this fucking shitshow. It is not worth a single cent, but guess how much they charge for the course and certification?!?! $2300 😱🫣😂. It’s so fucking bad I want to kill myself. Whoever decided to pour as little effort into this as possible over at Optimizely, I hereby curse you to a 2300 painful deaths and I hope someone shoves a ice cold rod up your ass to wake you up. *slams keyboard*2
-
It's funny how you start feeling bad for the next dev taking over your project because it turned into a total spaghetti code shit show that will be impossible to maintain in the future with new features coming in.
Honestly... if a projects starts out with a certain scope which then gets extended EVERY FUCKING WEEK with requirements that can't even be met in the initial timeframe it's no wonder the code quality will decrease over time.
This just reminds me daily how important good project management (and I'm not talking about suit wearing pain-in-the-ass-managers) and the inclusion of devs in the planning process really is.
It's so fucking crazy that companies run like that with people up front that have NO FUCKING CLUE what they are doing, nor do they understand the mechanics, tech and effort that go into certain features. They're like "beep, boop, it's done by Friday you fuck!".
The funniest part of this stupid charade is that the closer we get to a new "deadline" (we will not meet the deadline anyways) the more nervous the "managers" get. WHY didn't you properly plan this shit in the first place? WHY didn't you care for the last six months where all this fucking bullshit could still have been prevented?
Meanwhile I'm just so sick and tired of this shitty project and this sucky company that I just don't have any motivation left to keep on working. It's so fucking hard and painful to work on projects that suck ass, are poorly designed. I just got to the point where coding is no fun any more. Thank god I'm out of here soon... fml5 -
I wish all you frontend devs who use the keydown event to hack tab-order a very painful and very quick death.
Especially those who fail to ensure that TAB; Shift+TAB is always identity.2 -
Had to fire two good developers and a decent QA engineer due to financial reasons in the company :(
That was the painful part, but moreover GUESS WHO'S GONNA GET MORE RESPONSABILITY FOR THE SAME WAGE?!
So long and thanks for all the fish. I'll see you in valhalla4 -
Roof is leaking... Due to rainy stormy weather here, I have now 3 buckets in my flat for catching the water.
Next thing that broke was the faucet in the kitchen... Whoever installed the kitchen (inherited from previous tenant) was a fricking fuck nugget. Not only are most important parts like the stove unbalanced (cooking is very fun...) - but most things were wrongly installed.
The rubber band under the faucet was a few mm larger than the faucet itself... Stretched out as someone really tightened the screws... Too tight. Friction tore the rubber band on one side. Note that the faucet is one of the large, pompous ones which weigh a fuckton. So the fucking faucet now - as the rubber band tore - turned into a sprinkler as the faucet moves due to water pressure.
Ok. Faucet out, new faucet in. Shouldn't be that hard.
Wait. Wtf?
Turns out they didn't use a milling head... The hole is a cone, top larger - then getting smaller.
Ok. No problem.
Let's do some drill action.
Uhm. Why is the place to the window wet... Oh. Great. Another leak.
*some mopping action*
Back to the kitchen. Realizing I didn't fully close the valve for water -.
Kitchen cabinet, next mopping action.
Water with saw dust is pretty ugly combination -.-
Aka: My relaxing Saturday became a full blown """Fuck you with an anchor""" day instead. Thanks universe. Love you hon. Please, next time put at least some lube on the anchor, entry is quite painful.13 -
TL;DR; do your best all you like, strive to be the #1 if you want to, but do not expect to be appreciated for walking an extra mile of excellence. You can get burned for that.
They say verbalising it makes it less painful. So I guess I'll try to do just that. Because it still hurts, even though it happened many years ago.
I was about to finish college. As usual, the last year we have to prepare a project and demonstrate it at the end of the year. I worked. I worked hard. Many sleepless nights, many nerves burned. I was making an android app - StudentBuddy. It was supposed to alleviate students' organizational problems: finding the right building (city plans, maps, bus schedules and options/suggestions), the right auditorium (I used pictures of building evac plans with classes indexed on them; drawing the red line as the path to go to find the right room), having the schedule in-app, notifications, push-notifications (e.g. teacher posts "will be 15 minutes late" or "15:30 moved to aud. 326"), homework, etc. Looots of info, loooots of features. Definitely lots of time spent and heaps of new info learned along the way.
The architecture was simple. It was a server-side REST webapp and an Android app as a client. Plenty of entities, as the system had to cover a broad spectrum of features. Consequently, I had to spin up a large number of webmethods, implement them, write clients for them and keep them in-sync. Eventually, I decided to build an annotation processor that generates webmethods and clients automatically - I just had to write a template and define what I want generated. That worked PERFECTLY.
In the end, I spun up and implemented hundreds of webmethods. Most of them were used in the Android app (client) - to access and upsert entities, transition states, etc. Some of them I left as TBD for the future - for when the app gets the ADMIN module created. I still used those webmethods to populate the DB.
The day came when I had to demonstrate my creation. As always, there was a commission: some high-level folks from the college, some guests from businesses.
My turn to speak. Everything went great, as reversed. I present the problem, demonstrate the app, demonstrate the notifications, plans, etc. Then I describe at high level what the implementation is like and future development plans. They ask me questions - I answer them all.
I was sure I was going to get a 10 - the highest score. This was by far the most advanced project of all presented that day!
Other people do their demos. I wait to the end patiently to hear the results. Commission leaves the room. 10 minutes later someone comes in and calls my name. She walks me to the room where the judgement is made. Uh-oh, what could've possibly gone wrong...?
The leader is reading through my project's docs and I don't like the look on his face. He opens the last 7 pages where all the webmethods are listed, points them to me and asks:
LEAD: What is this??? Are all of these implemented? Are they all being used in the app?
ME: Yes, I have implemented all of them. Most of them are used in the app, others are there for future development - for when the ADMIN module is created
LEAD: But why are there so many of them? You can't possibly need them all!
ME: The scope of the application is huge. There are lots of entities, and more than half of the methods are but extended CRUD calls
LEAD: But there are so many of them! And you say you are not using them in your app
ME: Yes, I was using them manually to perform admin tasks, like creating all the entities with all the relations in order to populate the DB (FTR: it was perfectly OK to not have the app completed 100%. We were encouraged to build an MVP and have plans for future development)
LEAD: <shakes his head in disapproval>
LEAD: Okay, That will be all. you can return to the auditorium
In the end, I was not given the highest score, while some other, less advanced projects, were. I was so upset and confused I could not force myself to ask WHY.
I still carry this sore with me and it still hurts to remember. Also, I have learned a painful life lesson: do your best all you like, strive to be the #1 if you want to, but do not expect to be appreciated for walking an extra mile of excellence. You can get burned for that. -
They say “think outside the box”. When you're depressed, the box is made of concrete. The more depressed you are, the smaller the box.
Our brain is wired to cut off thought processes that take too much energy. In depression, this mechanism works against you, cutting off everything but laying down. To me, get up in the morning and go brush my teeth is too outside the box. Thinking about it is like touching a boiling kettle. Painful, ouch-y, and my brain doesn't even want me to think about doing it.
I'm working and living in my bed. I don't really get up. Should I even say about things like going out or cooking?3 -
Using M$ Teams on Ubuntu is a painful experience. Feel like setting up a VM just to run Teams the way I want to it run.6
-
I have a complex about my nose. I was about to bite the fucking bullet and do something about it. Literally just waiting for the procedure room to be ready, when I kept asking myself wtf I was doing. Then looked at my nose again and realized that it really wasn't that big a deal. Not when compared to dealing with internal bleeding and pain for weeks, plus a painful procedure.
Even after all these years, all these accomplishments, all this experience, I'm still a dumb fuck.
Now then, I'll go put some of the money I didn't waste to good use. Like videogames, hookers, and blow. Probably just the former.5 -
I feel like it might be a tiny bit (not much) better among React developers, but I ended up within one of those enterprise Angular till death companies, and it seems like nobody would ever doubt their Typescript skills, yet nobody actually understands Typescript at all.
In theory, I love Typescript. But you can abuse it to a point where it's almost as painful to work with as normal JavaScript.
It's not that I'm a master of Typescript.
But while I feel like I'm the only one understanding the mental model behind Typescript and also get stuff like mapped types or why you might wanna replace your enums with as const assertions, the rest calls themselves Typescript developers in their CV, no doubt. But It's way to easy to write whatever Typescript, while it's not as easy to reel get the hang of it.7 -
1. Keep my job
2. Keep my side job
3. Revive blogging at least 1 post a month
4. Keep focus on what’s important and what are priorities
5. Finish my notes / diary application cause my text files / html pages are now taking up to much space and using cat/grep to search trough them is painful ( it can also help with point 3 )
6. Maybe just maybe start writing prototype of table top rpg game scenario, I have a concept in my mind for a long time but it’s also connected to point 5 and 7 and 8
7. Spend twice more time to practice drawing than in this year
8. Read / listen to more than 1 book a month
I think that’s it from dev stuff1 -
The most painful thing about job application rejection is the canned response. You would be left scratching your head as to why you were rejected.2
-
Is there anything possibly more worthless than Gimp for doing basic image edits. Damn, all I wanted to do was make the white background of an image transparent. I usually use Paint.NET (only available on a PC) for quick crops and background removals. Gimp is just...painful. Now I gotta fire up my PC and send myself the image so I can edit it there.10
-
When my brain was overloaded and overwhelmed during rapid-cycling bipolar disorder, my life and my thoughts were a complete mess. Somehow, when I heard or imagined plurals of certain words, like "cans" or "cups", my brain painted pictures of a cute civilization of living soda cans. They fought oppression that came from us humans, but lacked mental capacity to do so. I felt really sorry for them and wanted to help. The more ordinary the word were, the more striking effect it had on me.
The rapid-cycling fashion of bipolar disorder is often triggered by unfit prescription medicines. This kind of disorder is among the most lethal mental disorders there are, with a huge percentage of patients committing suicide.
If you can't make sense of your thoughts, if your emotional responses seem inadequate or too strong, to the point when you can collapse crying after some random thought, stop whatever you're doing and seek help. Ask friends and family to find you a psychiatrist, as by the time you need help, you may lack mental capacity or emotional resource to find a doctor by yourself. To me, even the idea of leaving my bedroom and going somewhere was painful to think about.
If your thoughts appear to be "put into your brain" against your own will, if they make no sense, don't attempt to make sense of them. They are nothing but a random noise produced by overwhelmed synapses. -
"Code"
And the website says "Lonely geeky people do need apply"
So I put my on my glasses and I went in to ask him why
He said you look like a fine outstanding young man, I think you'll do
So I shook his hand and, I said "I am glad I will be working for you."
Code, code, everywhere there's code
Neo vision, tweakin' my mind
Do code this, and API that, can't you read the fucking manual
And the sign says "If you want to use this site you must accept our cookies"
So I found the CEOs address and doxxed him all night!
To put up a dialog and block content from my sight.
If Todd was here, he'd tell it to your face, man, "it just works"
Code, code, everywhere there's code
Neo vision, tweakin' my mind
Do code this, and API that, can't you read the fucking manual
Oh, say now mister, can't you code
You got to have a laptop and a hoodie to get a job
You can't work, no you can't standup, you ain't supposed to be here
And the website says "You got to have an employee ID to get inside" - yo!
And the website says "Everybody welcome, come in, code and share"
But then they passed around a git pull at the end of it all
And I didn't have a character to code
So I got me laptop and I made up my own fuckin' code
I typed, "Thank you OSS for thinking 'bout me, I'm alive and doing fine", yeah
Code, code, everywhere there's code
Neo vision, tweakin' my mind
Do code this, and API that, can't you read the fucking manual
Code, code, everywhere there's code
Neo vision, tweakin' my mind
Do code this, and API that, can't you read the fucking manual
Yes! Some old song, called "Code code", I wish we did write that one, but
We didn't - git blame!
Hello World!6 -
Aka... How NOT to design a build system.
I must say that the winning award in that category goes without any question to SBT.
SBT is like trying to use a claymore mine to put some nails in a wall. It most likely will work somehow, but the collateral damage is extensive.
If you ask what build tool would possibly do this... It was probably SBT. Rant applies in general, but my arch nemesis is definitely SBT.
Let's start with the simplest thing: The data format you use to store.
Well. Data format. So use sth that can represent data or settings. Do *not* use a programming language, as this can neither be parsed / modified without an foreign interface or using the programming language itself...
Which is painful as fuck for automatisation, scripting and thus CI/CD.
Most important regarding the data format - keep it simple and stupid, yet precise and clean. Do not try to e.g. implement complex types - pain without gain. Plain old objects / structs, arrays, primitive types, simple as that.
No (severely) nested types, no lazy evaluation, just keep it as simple as possible. Build tools are complex enough, no need to feed the nightmare.
Data formats *must* have btw a proper encoding, looking at you Mr. XML. It should be standardized, so no crazy mfucking shit eating dev gets the idea to use whatever encoding they like.
Workflows. You know, things like
- update dependency
- compile stuff
- test run
- ...
Keep. Them. Simple.
Especially regarding settings and multiprojects.
http://lihaoyi.com/post/...
If you want to know how to absolutely never ever do it.
Again - keep. it. simple.
Make stuff configurable, allow the CLI tool used for building to pass this configuration in / allow setting of env variables. As simple as that.
Allow project settings - e.g. like repositories - to be set globally vs project wide.
Not simple are those tools who have...
- more knobs than documentation
- more layers than a wedding cake
- inheritance / merging of settings :(
- CLI and ENV have different names.
- CLI and ENV use different quoting
...
Which brings me to the CLI.
If your build tool has no CLI, it sucks. It just sucks. No discussion. It sucks, hmkay?
If your build tool has a CLI, but...
- it uses undocumented exit codes
- requires absurd or non-quoting (e.g. cannot parse quoted string)
- has unconfigurable logging
- output doesn't allow parsing
- CLI cannot be used for automatisation
It sucks, too... Again, no discussion.
Last point: Plugins and versioning.
I love plugins. And versioning.
Plugins can be a good choice to extend stuff, to scratch some specific itches.
Plugins are NOT an excuse to say: hey, we don't integrate any features or offer plugins by ourselves, go implement your own plugins for that.
That's just absurd.
(precondition: feature makes sense, like e.g. listing dependencies, checking for updates, etc - stuff that most likely anyone wants)
Versioning. Well. Here goes number one award to Node with it's broken concept of just installing multiple versions for the fuck of it.
Another award goes to tools without a locking file.
Another award goes to tools who do not support version ranges.
Yet another award goes to tools who do not support private repositories / mirrors via global configuration - makes fun bombing public mirrors to check for new versions available and getting rate limited to death.
In case someone has read so far and wonders why this rant came to be...
I've implemented a sort of on premise bot for updating dependencies for multiple build tools.
Won't be open sourced, as it is company property - but let me tell ya... Pain and pain are two different things. That was beyond pain.
That was getting your skin peeled off while being set on fire pain.
-.-5 -
Clench your butt tight hole and prepare:
Microsoft, Google, Amazon are the early owns, others going to follow. It's going to be painful year (Build back better).
https://blog.google/inside-google/...
This is just the start.....16 -
2 years ago(jan-oct 2020) i was a college student giving his final exams. some of my personal stats were:
- current knowledge of Android Framework and associated stuff(android, java, kotlin, making and deploying apps , best practises, etc) : 30%
- current knowledge of Web tech (html/css/js/php): 5%
- current knowledge of creating backend/frontend apps:2%
also
- free time: somewhat
- Personal health: barely caring about
====
Same year i got my first job (oct 2020) which i switched in next year (oct 2021). before joining the next(my current) job, my personal stats were:
- current knowledge of Java : 30%
- current knowledge of Kotlin : 70-80%
- current knowledge of Android and Android Stuff(the framework, making production ready apps, deploying, best practises , etc) : 70-80%
- current knowledge of Web tech (html/css/js/php): 3-5%
- current knowledge of creating backend/frontend apps:1%
also:
- Free time: lol, i was working at 1 am too
- Personal health: even lesser caring about, body fats and thick muscles at various places
====
it will be almost a year of me working for these guys in November and this has been an interesting year so far. the stats are:
- current knowledge of Java : 35%
- current knowledge of Kotlin : 20-30%
- current knowledge of Android and Android Stuff(the framework, making production ready apps, deploying, best practises , etc) : 20-30%
- current knowledge of Web tech (html/css/js/node/react): 20-25%
- current knowledge of new stuff* (cordova,unity,flutter, react native, ios) : 5-10%
- current knowledge of creating backend/frontend apps:10-15%
also:
- Free time: a good amount of free time, like in addition to weekends and festivals, i take 2-4 leaves every month
- Personal health: improving a lot. loosing weight, gaining muscles, getting better stamina at running and other activities
====
So i am currently at a weird place. As from my stats, you can see that previously i was in a android heavy role in a company that put a lot of pressure, but i was able to become a better sellable dev through it.
My current role is also of an android dev here, but we maintain b2b products and i am sometimes asked to fix bugs in hybrid apps like unity, react native and cordova, so gained a few knowledge there too. and since i have a lot of free time in my hand, i explored a bit of web technologies too (apart from enjoying a relaxing life and focusing on personal health)
However my main concern is that am becoming a less sellable Dev. The lack of exposure/will to work on android tech has made me outdated from a framework that was once my stronghold. remember that i joined my first company purely because of my passion and knowledge of android os.
When i got offer from this company, i also had another, $5000/year lesser offer in hand. both of these offers were very generous , but i went with the greed and took the offer from this company despite knowing that they are looking for someone who will act as a developer-maintainer kind of person, while the other company giving lesser pay had a need of a pure android engineer.
So i am currently 24. should i keep on doing this relaxing but slowly killing job, or go into a painful, pressurizing but probably making me a better "android" engineer job ?2 -
Can i get success if i worship the devil?
Because for example if i need a car and if i pray to God to have a car, that would be pointless because God doesnt work that way. God wants you to take action so you can have the car. So instead maybe i could rob someone and steal the car and then pray to God for forgiveness because that's how God works?
But since thats illegal and i might get in jail i was thinking to worship satan because you know how most successful people and celebrities sell their soul to satan in exchange for success? I was thinking maybe something similar, not sell my soul but just worship the evil until i finally graduate this shitty disgusting college after 6 painful years and finally start 100% focusing to code on projects i enjoy?
What would be the consequences if i worship evil?6 -
Working with rails in ci/cd environment is always soo painful. Developing is a joy, but operating it is the pure horror :'(3
-
i just want to say i dont like material ui because customizing it is so painful . bootstrap is so much breeze to work with.