Wow this one deserves a rant. Where should I even begin? I got a new job for over half a year now doing work in an agency. We're building websites and online shops with Typo3 and Shopware (not my dream, but hey). All fine you might think BUT...

1) I have been working on the BIGGEST project we have all by myself since I started working at this company. No help, nobody cares.

2) If something goes wrong all the shit falls back to me like "wHy DiDnT yoU WoRk MoRE?". Seriously? How should one dev cover a project that's meant for at least two or three.

3) The project was planned four years ago (YES that's a big fat FOUR) and sat there for 3,5 years - nobody gave a fuck. I got into the company and immediately got the sucky shit project to work on.

4) I was promised some time to get familiar with the projects and tech we use and "pick something I like most to get started". Well that never happened.

5) I was also promised not to talk directly to our customers. Well, each week I was bombarded with insults, a shitload of work and nonsense by our customers because (you guessed it) I was obligated to attend meetings.

6) The scheduled time for a meeting was 30 minutes, sometimes they just went on for over two hours. Fml.

7) Project management. It does not exist. The company is just out to get more and more clients, hires more god damn managers and shit and completely neglects that we might need more devs to get all this crap finished. Nope, they don't care. By the way: this is not like a 200 employee company, it's more like 15 which makes it even sadder to have 4 managers and 3 devs.

8) We don't use trello (or anything to keep track of our "progress"), nobody knows the exact scope of the project, because it was planned FOUR FUCKING YEARS AGO.

9) They planned to use 3 months on this project to get it finished (by the way it's not just an online shop, it has a really sophisticated product configurator with like 20 dependencies). Well, we're double over that time period and it is still not finished.

10) FUCK YOU SHOPWARE

11) The clients are super unsatisfied with our service (who would have guessed). They never received official documents from us (that's why nobody knows the scope), nor did they receive the actual screen design of the shop so we just have to make it up on the go. Of course I mean "I" by "we", because appearently it is my job to develop, design and manage this shit show.

12) My boss regularly throws me in front of the bus by randomly joining meetings with my client telling them the complete opposite of things that we discussed internally (he doesn't know anything about this stupid project)

13) FUCK YOU COLLEAGUES, FUCK YOU COMPANY, FUCK YOU SHOPWARE AND FUCK YOU STUPID CUSTOMERS.

14) Oh btw. the salary sucks ass, it's barely a couple of bucks above minimum wage. Don't ask me why I accepted the offer. I guess it was better than nothing in the meantime.

Boy that feels good. I needed that rant. But hey don't get me wrong. I get that dev jobs can be hard and sucky, but this is beyond stupidity that I can bear. I therefore applied for a dev job in research at a university in my dream country. Nice colleagues, interesting projects, good project management. They accepted me, gave me a good offer and I can happily say that in 6-7 weeks my current company can go fuck themselves (nobody knows the 10.000+ lines of code but me). Just light it up and watch it burn!

Okay so this is going to be a rant.

My exams started last wednesday. I'm doing a study called Application Development and I'm in my 5th year now (out of 4, long story).

This is the stuff that's going wrong at the moment and it's getting FUCKING annoying.

- The windows computers were not installed that well so everyone had to downgrade from the last update which took way too long.
- We have to have at least 1-3 conversations with the 'client' and 'manager' for each document but the waiting lists are so long that we have to wait for about 2-4 hours in general (we had a total of 18 hours for the first task) so a lot of people couldn't even have a meeting about around half of the documentation. Having meetings about everything is a REQUIREMENT for a good grade.
- Some of the teachers are so slow that the meetings take way too long.
- Although documentation is important, we calculated that about 80% of the WHOLE FUCKING EXAMS will be documentation which is way too fucking much.
- Some of the grading points (like chapters you have to write in the documentation) ARE NOT EVEN IN THE TEMPLATES MY STUDY PROVIDES. Already had a moment where a teacher was like 'I'm missing this chapter?' me: 'It's not in the official templates?!?' teacher: 'stop right there. I have to grade you for this so is that your or my problem'? unbe-fucking-lievable.
- Some students get so many 'musts' that we are seriously doubting if we can get this to work within about 2 days (12 hours).

Sorry for this rant but I had to get this the FUCK out.

TFW your client's git policies are so draconian that the dev teams use "develop" as trunk, and completely ignore the release process.

I wrote up 50 pages of git standards, documentation and procedure for a client. Bad indian director 9000 decides the admin (also Indian) who specializes in Clearcase and has no git or development experience is more qualified to decide and let's him set the policy.

FF to today:

- documentation, mostly contradictory, is copy pasted from the atlassian wiki
- source tree is the standard
- no force pushing of any branches, including work branches
- no ff-merge
- no rebasing allowed
- no ssh, because he couldn't figure it out...errr it's "insecure"
- all repos have random abbreviated names that are unintelligible
- gitflow, but with pull requests and no trust
- only project managers can delete a branch
- long lived feature branches
- only projects managers can conduct code reviews
- hotfixes must be based off develop
- hotfixes must go in the normal release cycle
- releases involve creating a ticket to have an admin create a release branch from your branch, creating a second ticket to stage the PR, a third ticket to review the PR (because only admins can approve release PRs), and a fourth ticket to merge it in
- rollbacks require director signoff
- at the end of each project the repo must be handed to the admin on a burned CD for "archiving"

And so no one actually uses the official release process, and just does releases out of dev. If you're wondering if IBM sucks, the answer is more than you can possibly imagine.

I give up. It‘s impossible to argue with Apple.

I tried to bring my unofficial iOS devRant app "JoyRant" into the AppStore. It was available via TestFlight for years and it wasn‘t a problem there, apparently. Now for the AppStore, it is a problem.

I talked with the Apple review team for 3 weeks and the discussion went in circles.
They said that my app tries to disguise as or to misrepresent another app on the store (the official devRant app, even though it‘s not available anymore, apparently).

I was asked to remove all of the mentions of devRant from any description or any place in the app. I did. Even though it was stupid because how are people supposed to know that they need a devRant account to use my app? I‘m not allowed to mention devRant.

After that, they said that it can not have the name JoyRant because it sounds too similar to devRant.
I changed it to devJoy everywhere, the app, the meta data for the app store, the github page where the required legal crap is hosted, and in the legal documents themselves.
Did it help? No, it didn‘t.

Apple then proceeded to claim that my app is trying to deceive the users into thinking that this is the official devRant app. Even though I have explicitly stated in the description that it is just an unofficial devRant client.

Now apple says that I should "revise the app content".
Which I assume means that I need to make it something different. Yeah. Great suggestion!

So, I will rename the app back to JoyRant and provide it via TestFlight, as it was before.

Thanks for reading. I needed to vent.

Preface: i'm pretty... definitely wasted. rum is amazing.

anyway, I spent today fighting with ActionCable. but as per usu, here's the rant's backstory:

I spent two or three days fighting with ActionCable a few weeks ago. idr how long because I had a 102*f fever at the time, but I managed to write a chat client frontend in React that hooked up to API Guy's copypasta backend. (He literally just copy/pasted it from a chat app tutorial. gg). My code wasn't great, but it did most of what it needed to do. It set up a websocket, had listeners for the various events, connected to the ActionCable server and channel, and wrote out updates to the DOM as they came in. It worked pretty well.

Back to the present!

I spent today trying to get the rest to work, which basically amounted to just fetching historical messages from the server. Turns out that's actually really hard to do, especially when THE FKING OFFICIAL DOCUMENTATION'S EXAMPLES ARE WRONG! Seriously, that crap has scoping and (coffeescript) syntax errors; it doesn't even run. but I didn't know that until the end, because seriously, who posts broken code on official docs? ugh! I spent five hours torturing my code in an effort to get it to work (plus however many more back when I had a fever), only to discover that the examples themselves are broken. No wonder I never got it working!

So, I rooted around for more tutorials or blogs or anything else with functional sample code. Basically every example out there is the same goddamn chat app tutorial with their own commentary. Remember that copy/paste? yeah, that's the one. Still pissed off about that. Also: that tutorial doesn't fetch history, or do anything other than the most basic functionality that I had already written. Totally useless to me.

After quite a bit of searching, the only semi-decent resource I was able to find was a blog from 2015 that's entirely written in Japanese. No, I can't read more than a handful of words, but I've been using it as a reference because its code is seriously more helpful than what's on official Rails docs. -_-

Still never got it to work, though. but after those five futile hours of fighting with the same crap, I sort of gave up and did something else.

zzz.

Anyway.
The moral of the story is that if you publish broken code examples beacuse you didn't even fking bother to test them first, some extremely pissed off and vindictive and fashionable developer will totally waterboard the hell out of you for the cumulative total of her wasted development time because screw you and your goddamn laziness.

Client sends me support email concerning the CMS.

There's not enough details to go on, esp. browser info, so I ask her to fill out a support ticket.

She does, but doesn't enter any browser info, AND mistypes her email address so I have to correct it to reply to the right email.

I send her to whatbrowseramiusing.co and ask her to send the info to our support email address.
She emails support directly with these words: "I am using Google bowser".

I reply: click "Send to my designer" on whatbrowseramiusing.co and I give her exact steps to fill out the three form fields

She replies: "There is no 'Send to my designer', I only get the option to buy the domain."

I'm like "Whut?!" Did you mistype the URL? Why don't you click the link in the email? (Paraphrase)

This time I get an official email from whatbrowseramiusing.co, telling me that the client is using Safari 5.0.5. Which is five years old.

At that point I replied and said we really can't support this older browser, and included a link to the Firefox download page.

I couldn't sleep. I was staring at the blinking cursor. A slow, comforting blinking. Like everyone else, I had become a slave to the JavaScript ecosystem. If I saw something like a new build system, or a new framework, I had to have it.

My client changed the requirements again. I'm in pain.

- "You want to see pain?" my colleague said. Go read Apple support forums. That's pain.

I became addicted. Every time I died and every time I was born again. Resurrected.
During the night, I was crying in the Apple forums for an official answer that would never come. During the day, I was surfing StackOverflow to fix my problems. You get "single-serving" friends there. They help you, you help them, and then you never see them again.

- "Then you install Stack and boom, you're done. It's that easy to go functional."

That's how I met him.

- "You know why they make so many javascript frameworks?"
- "No, why?"
- "So that they can distract you while they put backdoors in them. So that you don't have time to check all of their code".
- "You are by far the most interesting "single-serving" friend I've ever met"

Then, my hard disk died. Of course, I didn't have backups: nobody has enough space for all those node_modules folders. All my addictions, lost.

Then I wrote him. If you asked me now, I couldn't tell you why I wrote him. We chatted a lot.

- "It's late, I should really go search another hdd on ebay"
- "Ebay? You called me so you could have my old hard disk."
- "No, I..."
- "Come on."

He sent me his old hard disk. It was a 256MB hard disk, but it was fine for running Arch. Then he asked me to rant about my problems in front of him.

- "I want you to rant as hard as you can"
- "Are you serious?"

We ranted all night about our bosses and clients and their fucked up requests. We kept in touch, and after a while more people were ranting with us. Every week, he gave the rules that he and I decided.

- "The first rule of devRant is -- you don't talk about devRant. The second rule of devRant is -- you don't talk about devRant."

I like to think this is how devRant started. This might also be the reason why we never see @trogus, only @dfox. A lot of shit still needs to happen.

When your team's hard work receive such a mail from the client and still your Project Manager treats you like shit :|

A little back story

Me (hybrid app guy), backend (php api) guy and ui guy (html-css) worked fuckin day and night, to chase the fuckin less than 10 days deadline for this App

We hard to create the App for all 4 platforms including win mobile and blackberry (god bless UI guy and me :|) ~ 2013

Those were the coolest days of our lives , we had a super blast - working (slogging) + drinking + just having fun cursing + not giving fuck to anything and anyone + more drinking..

Cool thing is, our client was in an impression that full backend and front end TEAM is working on this App 😀

This mail still makes us laugh
"professional team" 😁😂

Unfortunately I got paid only half of the salary for next month and left the company shortly
(because official company timing was from 10:00 AM or else half day paycut and I am a night guy, I used to come at around 12:00 noon)

2020

Dotnet Core and dotnet framework are now one (november).

Blazor has an official release for client side webassembly.

I fucking hate MS Teams!

I do not use it at all, but there is another company of our group that has it. At the beginning, I could just access the website and talk to them over there. Ok, the page was not good, but that used to work for me.

The last meeting I had with them, the web version did not exist anymore, they just made me install the app. Luckily there is an official Linux version, so I could install it. I got late to the meeting, but could make it.

Today I had a meeting with a client. Important stuff and Teams did not let me use it because I had no business account with Teams enabled on it.

I've tried to use one of my personal accounts, to create a new one, to enable Teams, I've clicked, enabled, allowed every single thing they asked, but I ended up on the Teams home page again or with Teams asking me to call people on Skype instead of using Teams.

I've managed to create a company on Microsoft account on which I had to be responsible to my workers (!?!?!?) and it finally opened the Teams app, but when I try to enter the client meeting link, it just opens the app with no error message at all.

Fuck Teams and fuck Microsoft!

My coleague's story

- before leaving after long day at the office final look at support cases (after official support hours)
- sev1 ticket logged an hour ago, noone called us (although should have; after support hours)
- angry manager calls and demands to get in touch with the client immediately (we're already after support hours, FTS should pick the case, not us)
- we reach out. Customer has business-impacting case
- after initial info gathering: some cert got expired, they got a new one and placed it in the app's directory. The app still does not work
- the first question we ask: "are you sure you have placed it in the right directory?"
- "yes, we are sure. No problems there" - answers a voice with indian accent
- noone finds the root cause for hours.
- It's already 1am
- someone from client's specialists comes up with an idea: "are we sure the cert is in the right place? Let's try to move it to the same directory the old one was in the first place"
- .................................................
- production is working again
- "Why didn't anyone from support suggest this?!?!"
- .................................................
- 2am. Case solved, manager is informed everything's allright now.
- In the morning we get yelled at by the manager bcz we supposedly missed a sev1 ticket and were incompetent during the conf. call

This reminds me why I stay away from support. And why I started hating people. And why I do not work with indians (our ways are too different for me to stay sane and not to kill anyone).

when the client says 1 week before production that the official web browser is ie8

Sorry, need to vent.

In my current project I'm using two main libraries [slack client and k8s client], both official. And they both suck!

Okay, okay, their code doesn't really suck [apart from k8s severely violating Liskov's principle!]. The sucky part is not really their fault. It's the commonly used 3rd-party library that's fucked up.

Okhttp3

yeah yeah, here come all the booos. Let them all out.

1. In websockets it hard-caps frame size to 16mb w/o an ability to change it. So.. Forget about unchunked file transfers there... What's even worse - they close the websocket if the frame size exceeds that limit. Yep, instead of failing to send it kills the conn.

2. In websockets they are writing data completely async. Without any control handles.. No clue when the write starts, completes or fails. No callbacks, no promises, no nothing other feedback
3. In http requests they are splitting my request into multiple buffers. This fucks up the slack cluent, as I cannot post messages over 4050 chars in size . Thanks to the okhttp these long texts get split into multiple messages. Which effectively fucks up formatting [bold, italic, codeblocks, links,...], as the formatted blocks get torn apart. [didn't investigate this deeper: it's friday evening and it's kotlin, not java, so I saved myself from the trouble of parsing yet unknown syntax]

yes, okhttp is probably a good library for the most of it. Yes, people like it, but hell, these corner cases and weird design decisions drive me mad!

And it's not like I could swap it with anynother lib.. I don't depend on it -- other libs I need do!

I'm in a programming school that gives only projects in C and a method to learn quickly.
Then we don't have official web classes or anything so we have "Labs" or "Clubs" and last time I was at a web programming club, leaded by students (because it gives me some more credits).

I was very surprised because they began to try to learn us the Javascript without talking about DOM.

And their explications about server-side and client-side codes were not clear (and obviously not exhaustive).
I have some (not a lot neither) experience in web programming so I helped him to make his course more understandable but I can't believe that these courses are given by students who don't have any idea of what's web programming...

Why are banks so absolutely archaic and stupid when it comes to tech? I work in a Services based company and currently engaged with a very famous bank to build accounting software for Mutual Funds. The day to day stupidity of this client is driving me absolutely crazy.

They couldn't give us proper requirements, and my company was stupid enough to kickoff the project without official sign off. Not only did they change the requirements, but they added a shit ton MORE features, and essentially bullied us into completing it all in the same timeline. Their attitude is pathetic, they shit talk our dev team, they make us build the worst possible UX, and then complain that it's not looking good and not working well. They have absolutely no idea about any of the technical stuff and think that software is a magic box that will give them what they want.

I swear I have a lot of examples but I'm so angry right now that my words are fumbling and I can't think straight. Stand up is in 45 minutes and I'm just dreading it. Idk how to tell everything, it's just... AAAAAAAAAAAAAAAAAAAA

Update on my devRant client SwiftUIRant:

I’m experimenting with some UI changes compared to the official app.

* vote buttons are laid out horizontally and placed above the rant to not waste space on the left side.
* comments count shows 0 comments instead of disappearing.
* rants are not cut off but visible in full length (I plan to add a toggle setting for that)
* creation date/time is present in the feed
* date/time formatter uses the current system region and the language english. So no more awkward American dates for non American users.

What do you think?

So I’ve finished the project (YES FUCKING FINALLY I KNOW) but it’s not official until I turn in the code to my client (FUCK) and see if he wants me to add anything or if it’s good how it is. Fingers crossed 🤞🏻

This happened about 2 years ago. My colleague at work, who's a kind and smart soul was actually yelling at the phone. Before that nobody had heard her yell at anyone, let alone a client.

The history was that she found out that the client sent her falsified official documents and she confronted him about that, so the idiot client started laughing then yelling that she had to be 'on his side' since he hired us as consultants. That's when she started yelling.

How can anyone be so cynical?
This is also our job to save your moron ass from your own stupidity.
If she didn't found out and the documents sent to the government there would be a lot of trouble for everyone especially the client.

After that we all comforted her and told her she did right. Unfortunately the client wasn't fired (a friend of the boss) but of course we all declined to work with that client again.

Freenas update from 11.1 to 11.2 beta 2

They added experimental smb direct / multichannel support, yay.

Me tries to connect to the smb share:
->Connection timed out 🤔

Tries something.
->Connection refused 😐

Google foo ....
->Nope, no connection 😔
"Failed to retrieve list of shares from server"

Reinstalls freenas to be sure it's not some janky install.
->Nope.

Google some more
->Nope 😭

*Like a year later*
Look into /etc/samba/smb.conf

Client max protocol = NTLM1

Motherfucker! 😬
Who thought that to be a good Idea!?
😠
It's the default Manjaro smb conf from the official repository by the way.

Seriously.
Didn't even know there was a setting for max client protocol.
Thought it was a server only config.
😵
Nope, some motherfucker trolled me long and hard this time. 😩

But back to getting smb direct working on my setup.

Thunar gvfs is like it's own completely separate thing.

Smb status, and all the other commands don't see any open connections anywhere.
Gvfs still connects fine to the share even though the smb.conf is deleted and everything else is complaining that there is no config.

On the one hand, it uses samba, on the other it's not actually.

Where the heck can I see the connection properties and wether rdma works or not?

Mother trucking, fracking, leg breaking piece of a dance type.

Working from home. Most of the team is off. Client has an official half day. Most of them are off. Instead of being online at 7 am, gonna get online around 850 just before daily standup. Laying in bed, enjoying the cool sheets and the fact that there's no rush. ~0730 team lead calls, user shit himself and I need to fix it. Server issue? Nope. Data issue? Nope. Portal bug? Nope.

Client input conflicting data and can't progress with tool.

FUCK reddit

Seriously fuck reddit. I just wanted to post a fucking Question but noooo you must have Karma to post it. Your account has to be old af. Which dickhead designed the god damn karma system???? I'll never try to use that fuckin platform again, the user experience is horrible and their official app is absolute trash. It's slow and buggy, even a fucking 12 year old can code a better client.

Argghhhh I am angry

Okay, so, my company does some stuff around blockchain. I had source for smart contract prepared before and it was on 'todo' queue. So, time for it, time to deploy on Kovan, time to test it on actual chain. Riiiight? Okay compiled no problem, deployed, no problem, i plug into several gui's ABI provided by compiler, and... Well..

I still do not understand why each and every gui prompted me to send view transactions (external view), instead of, well, eval them locally, i checked the ABI manually, it is correct, i stripped it down, it is correct, all up to spec.

I try older version of offline MEW, to have older web3.js with no success that thing works properly.

Every
Single
Web3.js based client
Behaved
Differently

And none behaved correctly.

I would, like, understand, if I didnt use official compiler, but official compiler should for F sakes be compatible with official client.

Today this stole 6 hours of my life, I didnt manage to solve it, and I am legitmitely pissed.

Im getting close to re-implement segment of web3JS to be able to do the tests I need to do.

Its not like I havent done it before....

Looking back on 2020: I only did one small contracting job.

The client wasn’t putting their trust in us. I fired them. They went with another company. Almost a whole year - and the old flash site is still up there! Kinda a waste of time / but got paid for our work - and it feels great to just let shit go.

Besides that, I didn’t do any official dev work all year! I just continued working on our school curriculum and teaching. 2020 has been an R&D dream, really. I feel a bit spoiled! As I sit here in my Christmas pajamas!

Excited for 2021.

The first dev project, like real dev project, I participated in was a school one and it was double.
The class was meant to make us learn about the software's life cycle, so the teacher wanted us to develop a simple, yet complicated, thing: a Web platform to help tutors send/refer students to the university services (psychologist, nutriologist, etc) and to keep track of them visits.
We all agreed on it being easy.
Boy were we so wrong.
I was appointed as dev leader as well as some others (I was the programming leader, the other ones were the DB guy and the security guy) and as such I was in charge of the technology used (well, now we all know that the client is the one in charge of that as well as the designer) and I chose Django because we had some experience with it. We used it for the two projects the teacher asked us to do (the second one was to find a little shop and develop something for it, obviously with the permission and all that), but in the second one I decided to use React on top of Djangl, which ended being a really good combination tho.
So, in the first project, the other ones (all the classroom) started to discuss and decided to use some other stuff like unnecessary carousel for images, unnecessary functions, they created mock ups for stuff that was never there to begin with, etc. It was really awful, we had meetings with the client (the teacher) with updates on the project, and in not a single one he was satisfied with the results. But still, we continued with the path the majority chose and it was the worst: deadlines were not met, team members just vanished until the end of the semester, one guy broke his leg (and was a dev leader) and never said a word not did anything about the project. At the end, we presented literal garbage, the UI was awful, its colors were so ugly because we had to use the university official colors, the functionality was not there, there literally was a calendar to make appointments for the services (when did the client ask for that? No one knows), but hey, you could add services and their data to it, was it what the client wanted? Of course not! What do you think we are? Devs?
Suffice to say that, although we passed with good grades, the project and the team was shit (and I'm counting me in)
The good part is that the second project was finished by me and it looked really good, yet it didn't matter, the first project was supposed to be used by the university, but that thing was unusable.
Then, in the subsequent vacations I tried to make pretty and functional/usable, yet I failed because I had a deadline for another thing I had to do, but hey, the login screen looked amazing!

People always say thet you should not quit your job before you have the next job lined up, but what if you plan to do freelance? This is my dilemma.

A bit of context (rant).

My current job is my first official job. Small company, VERY HIGH staff turnover rate. I have been here for 2 and a half years. My commute on a good day is < 20 mins, and money is relatively good.

During the last 6 months, all devs above me resigned, which lead to the system maintenance being passed on to the few devs left. Our biggest system is a legacy system (Windows CE), and new clients are actively signed up and new features requested. The codebase is not even worthy of being called spaghetti, changes break every client, I need to wash my hands every couple of minutes. Seriously, I would rather maintain obfuscated code. It is like a bunch of highschoolers wrote the system, though I think they would have done a better job.

Management is nice and understanding, but the state of the codebase is killing the spirits.

I fill my nights and weekends moonlighting to keep my mind off of the 'daymares' at work. I have never been a team player, and thrive on my own. I have been thinking quiting and going full freelance/contract the last couple of months. Should things not work out, I can always go job hunting (see issue in par. 1)

Is there a devRant client for android that works better then the official one? I saw devRant native, i love the animations but sadly its incomplete.

Client used IR35 as an excuse to not say thanks for helping them win an award. Been working on a contract for a firm for 3.5 years. I single handedly architected lead, recruited a front end dev and built the site (along with that other contractor).

The other day they won an award for the site. I didn't expect to be on the official thank you list (they named and thanked everyone involved) but they even excluded me and the other contractor (who granted was short term) from the internal email. Their reasons? IR35 and they're protecting me.... My rates are now being adjusted for the work I actually do!

This depends mainly on the programming language with which I want or have to develop a project.

I like to use Behat for PHP and other simple things. At the moment I only have clients who want to implement projects in PHP. God knows why.

For more complicated things I like to use yeoman, but I have to say that there are also a lot of horrible generators, so I follow the official instructions more often.

Otherwise, the usual procedure:
1) git init
2) Planning of features and functions (if not already specified by the client)
3) Select frameworks (mostly necessary)
4) Start programming
5) Commit often
6) Commit often
7) Commit often

A better half of the day wasted.
Why?
Because fabric8 k8s client probably has a bug, where it fails to deliver the last part of the exec() output. Or the whole output, if it's short enough.

brilliant... Aaaaaand we're going back to the official k8s client with ~10 parameters in their methods.

Fucking awesome.

This happened while I was working for my company's client, I was analysing why the build failed and I had ctrl+c the build files(.zip) to my local webserver to see what was wrong. After sometime I was replying an official email via outlook. But somehow those copied build files (.zip) ended up in this email. I realised this only it was too late. Yes config files had clear text passwords.