Boss: I need you to start on this new project, how long will it take?

Me: well, hard to say with no specs whatsoever...

Boss: just your best guess

Me: 4 to 6 month I guess?

Boss: so 3 months it is. When can you start?

Me: no specs, sir...and I said 4 to 6

Boss: the specs are almost ready, I know you can simplify it

Me: ...

Boss: just start with the basic infrastructure already

(4 months later)

Boss: here you are the specs, they might change a little in behaviour and design, but all the main stuff is here

(Hands me a A3 with a total of 21 pictures in InDesign)

Me: o....Kay. what happens when I click here?

Boss: oh, we should still talk about the app workflow, I'll get you updated

(2 weeks and 16 total rewrites of the "specs" later)

Boss: you told me it was a 2 months job, why aren't you finished yet? We must deploy in 3 weeks!

Me: ...

We all have our favourites

When you stare into git, git stares back.

It's fucking infinite.

Me 2 years ago:
"uh was it git fetch or git pull?"

Me 1 year ago:
"Look, I printed these 5 git commands on a laptop sticker, this is all I need for my workflow! branch, pull, commit, merge, push! Git is easy!"

Me now:
"Hold my beer, I'll just do git format-patch -k --stdout HEAD..feature -- script.js | git am -3 -k to steal that file from your branch, then git rebase master && git rebase -i HEAD~$(git rev-list --count master..HEAD) to clean up the commit messages, and a git branch --merged | grep -v "\*" | xargs -n 1 git branch -d to clean up the branches, oh lets see how many words you've added with git diff --word-diff=porcelain | grep -e '^+[^+]' | wc -w, hmm maybe I should alias some of this stuff..."

Do you have any git tricks/favorites which you use so often that you've aliased them?

They're giving multiple projects to work on and it's so fucking hard to remember workflow of 4-5 projects while working on side projects as well

I just discovered ctrl+r in the Linux terminal.

Mother of god this fucker speeds up my workflow!

A massive amount of kudos to the person who made this 😍

How long will it take?
Me: 45mins

...5 hours later
I thought you said 45 minutes
Me: Yeah. 45 minutes from now.

The following dialogue is inspired by a career of similar conversations.

--

Manager: What's the status?

Dev: It works, but I just found a security hole. That contractor did not sanitize all the different kinds of user input and someone approved the PR with "LGTM." A customer can run malicious code and get us in real trouble. I'm patching this now.

Manager: How long with that take?

Dev: If done right, 4-5 days. If done fast, I can squeeze 3.

Manager: Let's not boil the ocean. We need to ship by tomorrow so we can't spend too much time on something that we can fix later.

Dev: Surprising deadline aside, I made a Jira workflow state called "Later" for when you close the ticket after this conversation.

Manager: We need to talk about how your negativity impacts the team.

Dev: Sorry. I just don't want to knowingly release a critical vuln.

Manager: We can introduce a procedural change and have ops vet the documents. We already have a screen where they can approve what uploads get to the customer. If we let a bad egg through, then we'll right-size according to customer feedback.

Dev: Lawsuits are feedback?

Manager:

Manager: I mean

Dev: *Googles "brain parasite symptoms"*

Manager: Hey. The kind of thing you are worried about probably won't happen soon, and we'll be able to handle things in the short term.

Dev: Because it's better that our staff have unprotected sex with the Internet on our corporate network than use a few more days to move everyone along worry-free?

Manager: It's a calculated risk. We're Agile after all, right?

Dev: When it's an excuse.

True!

Today was my last day of work, tomorrow i have officially left that place. It's a weird feeling because i'm not certain about the future.
The job was certainly not bad, and after all i read on devrant i'm beginning to believe it was one of the better ones. A nice boss, always something to eat/drink nearby, a relaxed atmosphere, a tolerance for my occasionally odd behaviour and the chance to suggest frameworks. Why i would leave that place, you ask? Because of the thing not on the list, the code, that is the thing i work with all the time.

Most of the time i only had to make things work, testing/refactoring/etc. was cut because we had other things to do. You could argue that we had more time if we did refactor, and i suggested that, but the decision to do so was delayed because we didn't have enough time.

The first project i had to work on had around 100 files with nearly the same code, everything copy-pasted and changed slightly. Half of the files used format a and the other half used the newer format b. B used a function that concatenated strings to produce html. I made some suggestions on how to change this, but they got denied because they would take up too much time. Aat that point i started to understand the position my boss was in and how i had to word things in order to get my point across. This project never got changed and holds hundreds of sql- and xss-injection-vulnerabilities and misses access control up to today. But at least the new project is better, it's tomcat and hibernate on the backend and react in the frontend, communicating via rest. It took a few years to get there, but we made it.
To get back to code quality, it's not there. Some projects had 1000 LOC files that were only touched to add features, we wrote horrible hacks to work with the reactabular-module and duplicate code everywhere. I already ranted about my boss' use of ctrl-c&v and i think it is the biggest threat to code quality. That and the juniors who worked on a real project for the first time. And the fact that i was the only one who really knew git. At some point i had enough of working on those projects and quit.

I don't have much experience, but i'm certain my next job has a better workflow and i hope i don't have to fix that much bugs anymore.
In the end my experience was mostly positive though. I had nice coworkers, was often free to do things my way, got really into linux, all in all a good workplace if there wasn't work.

Now they dont have their js-expert anymore, with that i'm excited to see how the new project evolves. It's still a weird thing to know you won't go back to a place you've been for several years. But i still have my backdoor, but maybe not. :P

Unpopular opinion about Microsoft buying GitHub.

Just putting it out there that when you made your github repos you did so under their privacy policy and terms and will be protected under those in the future, and that both GitHub and Microsoft are corporations with the goals of making money.

Are people seriously mad that their code has gone from one capitalist corporation to another, with no foreseeable change in privacy or data policy? I have respect for those that switched to self hosted long ago since that's going from corporate to private, but if you throw away the UX and community GitHub has developed because a multinational corporation (with so many branches, products and divisions, which happens to have a few products you don't like) will soon own it, are you actually making a rational, guided decision?

Also just throwing it out there that GitLab is also a company. They've also had issues with keeping data intact in the past. They do, however, have free private repos (although I can't ever trust someone who gives me "free" privacy) as well as builtin CI. There are some definite upsides to it, although the UX has a ton of differences. If you're expecting the same dashboard and workflow you've used on GitHub, don't, GitLab has cool features but the bells and whistles aren't the exact same.

If you're switching to GitLab solely because of Microsoft, step back and think, regardless of how popular it might make you to hate Microsoft, is it really worth changing your development ecosystem to go from one corporate entity to another solely because you don't like the company?

I use GitLab and GitBub as well as Bitbucket and selfhosted git on a daily basis. They each have their upsides and downsides; but I think switching from one to the other solely because of Microsoft is not only totally irrational, but really makes light of/disrespects the amazing tools and UX the teams behind each one have carefully developed. Pick your Git hosting based on features and what works out for your use case, not because of which corporate overlord has their name plastered on it.

(Also just throwing it out there that lots of devs love VS Code, and that's Microsoft owned too... They did also build and pioneer a bunch of really cool shit for devs including Typescript so it's not like they're evil or incapable in any sense?)

Some dumb puns to cheer you up after reading/ranting about "part of your workflow you dislike"

#tower-of-pisa {
font-style: italic;
}

#titanic {
float: none;
}

.yomama {
width: 99999999px;
}

.ikea {
display: table;
}

#bigbang::before {
content: " "
}

.illuminati {
position: absolute;
visibility: hidden;
}

I'd rate these horrible puns a C++

Clients who keep calling in.

I'm a first liner and sysadmin, both (official title is Linux support engineer) so I do tickets+calls+server engineering.

It's highly annoying when you've got a busy day with loads of calls and I'm the first first-liner and I'm working on an important/high-prio ticket and PEOPLE KEEP CALLING.

Every time I can write like a few more words and then the fucking phone rings again aaaand so fucking on.

Your concentration is gone, workflow interrupted and my short term memory is shit so I entirely forget what I was debugging.

But, phone comes first 😞

"Just try and move your workflow to Windows, it's not that different from Linux"

My boss, when I asked him if I could install Arch on my company laptop

Good news: Learning to use Vim was tough as fuck but worth it. I've been on it for a week and not having to use a mouse for text editing anymore just naturally makes more sense.

Bad news: Nothing. Else. Has. Vim. I am going to be spending hours figruing out how to get this to work in MS Office online and Firefox to keep my workflow the same.

P.S. devRant should have a Vim option. Make it a perk for supporters. :)

I feel that people are quick to blame PHP for a lot of things. But come on, you have to admit it has the most straightforward debugging workflow:

Take a ritual knife out of your desk drawer

Sacrifice some blood to the PHP gods

Clean the knife

You can hate me: as a 34 year old php developer, i've never used git in my workflow...
I plan to start today using it on one of my personal project (only because i have arrived at "backup-49.rar")(yes i develop on windows).
Finger crossed

We practice IDD: Incident Driven Development

Basic workflow for software deployment

I've been fairly lucky with my bosses of late since I've progressed in my programming career. But my absolute worst boss was when I first started working in an office environment doing data entry. My boss at the time was terrible, and she was always against innovation or process improvement. She also always tried to make herself look good and taking credit for the accomplishments of others. If she screwed up it was your fault, and she was "always buried in email" so she could never respond to you for pto requests, or escalation of issues between departments. My whole family pretty much worked in various roles in the department and she fired my brother after my mother left the company for no reason, saying he was "sleeping", but I worked right next to him and he's tall and had to slouch just to comfortable see his computer screen since the same manager refused to approve work station improvements for him.

Our workflow was to receive daily spreadsheets of health care claims that we had to manually process and enter into the system. So being the lazy innovator that I am, and trying to find ways I can efficiently work, I delved into studying visual basic and programmed a few functions and tools in excel to analyze, highlight, and process some of the data since the claims on the spreadsheets always had a specific pattern. This was all before I had any formal education in computer science so the program was very basic and clunky but it tripled my efficiency. When I brought it up to my boss to spread it among the rest of our team so they could use it after a short 20 minute training, she struck it down saying any training or use of it would be a waste of resources since it was too technical and complex to be used and if I were to keep improving it or use it I would be fired. It was literally copy and paste from one spreadsheet to the other en masse and clicking a button to sort and fill in the blanks. Eventually I showed it to the director of the department when working on a large data entry project with her, and I was later offered a job as a technical analyst where I was responsible for the codebase that generated the reports for the department and specifically all the reports my old boss used where I would occasionally mess with her to get back at all the crap she gave me and my brother. Since all the reports were blind carbon copied to everyone, I would send out her reports on a delay while everyone else got them on time. It eventually got her in so much crap she had to step down as a manager. She still works in the same company that I started working at again earlier this year, and like the many careers she's ruined she eventually ruined her own within the company 😂

If you are a salesperson, you can just go straight to hell. You're all a bunch of cocksucking twats and I'm amazed you manage to get yourselves dressed each day. You're a no good fucking waste of oxygen and you need to put your fork in a socket the next time you're eating.

I'm working on building a crm and ticket management system for use in the office to handle client passwords. Since I'm building from scratch I wanted to make sure I had properly planned my classes and functions before opening the code editor so I put a message on my door that says "Don't interrupt, thanks" followed by the date so people knew it was a fresh message and not something left from the previous day.

I'm deep in the zone, the psuedo code and logic is flowing, I'm getting classes planned and feeling really productive for an hour or so when suddenly my door flies open and in comes a sales person.

SP: "Hey, do you have any extra phones lying around? Mine's being slow and keeps hanging up on people."

Me: "Do you see the sign on my door right there at eye level which says not to bother me?"

SP: "oh, do you want me to come back later?"

Me: "You've already interrupted me now, let's go see what's going on before I spent an hour setting up a new phone for you." While we are walking across the office I asked him when the last time the phone rebooted.

SP: "idk, Salesperson#2 suggested that as I was headed over here but I figured I'd just ask you."

We get over to his desk and I see he has two phones sitting on his desk. "Where did this one come from?"

SP: "Oh that was on the desk over here but I figured I could use it."

Me: "Well aside from the fact that the phones are assigned to specific people for a reason, you took the time to unhook your phone to set this one up and you didn't think to reboot your phone first. Plug your phone back in."

He plugs the old phone, which is assigned to him, and while booting it does a quick firmware update and boots up fine. He tests a few things and decides it's all better now.

So someone suggested a fix for you and you decided, instead, you would break company IT policy by moving equipment from one station to another without notifying the IT department. You entered a room which had a closed door without knocking, and you disobeyed the sign on the actual door itself which politely requests that you go away. All because you couldn't be bothered to take 2 minutes and reboot your phone, which you had to do anyways.

You completely broke my train of thought and managed to waste 2 hours of effecient workflow because you had an emergency.

Scrum they said.

Credit from imgur

I hate my job. I am furious at my colleagues.

Last November I asked my colleagues (A and B) to help me learn to use something, let's call it Tool. They said okay and set a date for training. Next week they said that they had too much work to do so we'll​ have to postpone. And the next date was also postponed and the next one too, and so on.

Three months in,​ colleague C kept dicking around and being a complete jackass telling me that he refused to work with me for I don't use the Tool.
Not like I didn't want to learn to use the Tool, I simply couldn't. I have long before googled how to use the Tool but in no way can Google ever tell me about our own company workflow, our methods, habits and such.

I was furious, but I am also a the most fucking patient person ever so I let it slide. The Tool wasn't actually needed that much to do my job anyways. And I have known for a while that colleague C needed to push someone under him to feel good about himself.

A few more dates had been set but got cancelled for reasons.
Meanwhile both A and B started to look down on me for not knowing how to use the Tool. I started to feel depressed.

Today B held a "workshop" about the Tool. It took two hours. He was not prepared, had a hangover and generally had a hard time concentrating.
He used aliases that he set up only for himself to show the usage of the Tool instead of commands that a beginner would understand (or google). He kept mumbling and I hsd trouble understanding him. His lecture lacked direction and was all over the place.

I am devastated and furious. I had been waiting since November for this training and when the time actually came he pulled something out of his ass and called it a workshop.

I didn't even get answers for my questions.

Now I feel that I am actually in a worse position than before because while I still cannot use the Tool, they can tell me that there was a workshop and I should've paid closer attention.

I want to quit so bad.

UI/UX Team: "We're using a new piece of software; all you developers can install it, its going to revolutionise our workflow and collaboration"

Me: *checks download page* ... "Only supports MacOS... FFFUUUU"

Where is all the linux love these days -_-

Forget about Internet explorer compatibility, EMAIL TEMPLATES are the actual worst. Outlook uses the same html rendering engine as MS WORD. It's sooo painful. All the bad practices you had to do 15 years ago, you have to do when you write email templates.

YOU WILL NOT KNOW PAIN until you have to make an email template, that works in Gmail, Yahoo Mail, OUTLOOK, outlook.com, outlook for mac, MOBILE, Android, the gmail app, IOS, apple mail, and so on. And after you make an unholy abomination of table garbage, then having to make it responsive/mobile friendly after all that!

If something is broken in one client, fixing it will break something in a different client! And then having to take a stab in the dark to try to fix it and then sending yet another test email (which costs $ per test)

I must have slashed decades off my life having to build email templates. It really is horrendous. There are frameworks like Zurb for email that at least let you feel like you're using a modern workflow. But things break just as often.

Honestly if you have the option, use a wysiwyg editor for building emails. At least when it does break (and they all will) you can at least blame the software.

Which is better than spending 4 hours on why that table cell doesn't line up correctly in outlook.

I cut my index finger cooking, now my typing is crippled.

Plz end my suffering.

Me: I can fix that workflow in about five minutes, In fact I can do it right now as we are speaking on the phone.

Customer: okay well... let me contact the director and make sure it’s okay that you fix it.

Me: I won’t make any changes to how it functions I’m only going to make it work again as it used to

Customer: we might need to schedule a meeting to talk about this because I’m not sure that we should be changing the site without permission

Me on the inside: I literally have global admin rights, unlimited power in Sharepoint, am responsible for making sure this stuff works, and BUILT this fucking thing, so now that I’ve been alerted of an issue I’m going to fix it. You are welcome to blame me if your boss is upset about it but I’m not going to wait for a fucking meeting to make sure it’s okay that I update a god damn email address in a workflow.

Me IRL: okay sounds great let me know when it is :)

Having the cocky junior dev that hasn't yet hit puberty squeak over my shoulder about as high of level concepts as he can discuss without spanning a general knowledge over anything. Front end, he has his 2 cents. Backend, his 2 cents. Any given subject that he knows nothing of, he has a very very general comment to provide. And on top of it he wears a fcn suit and tie to work every day at a start up tech company of 7 people. I'm sorry I forgot what the hell this post was suppose to be about but he completely fucks up every last bit of my productivity

Story time:

At a precious employer.
Hire shit-hot contractor.
No technical test at interview stage because he’s so shit-hot.
Is a uni lecturer.
PhD in mathematics.

Me: Shit, this guy must be good!

6 months later and a tragedy of errors and clearly misspent company funds later:

Manager: can you look at what x did and merge it into the product?

Me: Sure. *looks* *yells fuck very loudly*

*walks over to manager*

“Soooo... you know those 6 months and thousands and thousands you spent? It’s all for nought. There’s barely anything there, and none of it works.”

Manager: “Shit. What are we going to do? Can you fix it?”

Me: “To be honest, it would be quicker to just do it from scratch than try to work out what he’s done and failed to do.”

Manager: “Fuck. Ok. Go for it.”

I then had to build this entire new lot of systems, a workflow system, a user management and permissions system.

I got it done inside a month or so.

For context, we (the devs) knew something was afoot when the contractor couldn’t work out why his keyboard wasn’t working (it wasn’t plugged in), and he also *really* struggled to find his way around visual studio and git.

The moral of this tale? *always always* screen your candidates. Even if they seem amazing on paper.

!rant

So I have been recently hired at my current job for leading a product team. We're a small team working in a big company which have other teams working on other projects. I like my work and I have been appreciated for my work which I did since my stay here.
So I and my manager were discussing about how more can we automate our workflow to reduce the time to get the final builds. It was late in night. Suddenly someone asked, 'did I hear automation?'. We turned to see our CTO listening to our conversation. He told us that he's having trouble with automation in his project. I was new, so I didn't know what did he work on, so I asked.
Me: So what did you guys work on?
CTO: well, we work on automating stuff for clients and save them money. We earn 100x revenue than your product (In a more humble tone). I am currently looking for someone who can lead a team of developers for handling the automation scripting part. *Provides description of the candidate* Do you guys know someone like that?
Manager: (pointing towards me) It looks like his description.
CTO: I want him in my team then.
Manager: That can't happen, he's required in very important stuff and you're not allowed to poach.
CTO: I think I have the right to poach 😉
Me: OK, so how much raise am I going to get to switch teams (to the manager) and how much am I going to get to stay? Whoever gives me more I am theirs.
CTO: I like this guy

It's day three, I am still awaiting for one of them to tell me who won 🙁

PS: They both are friends with each other.

Created a branch for the first time. Now I can switch and stuff. 😍

Awesome!

What workflow?

Last night I nearly finished my portfolio site. I was working on the perfect framework and workflow like forever. But in the end I accomplished a pretty pleasing solutions. For the back-end I choose Laravel with it's built in rest-api, the front-end is managed by Vue. I'm also proud of my assets-management which is handled by Gulp + Webpack (Laravel Mix). But here I decided to run Gulp on images, fonts and CSS and let Webpack bundle the JavaScript.

And what really crawls my balls is that I can write Sass and Jade, even use partials and organized the shit out of this website, and let Gulp just vomit some minified HTML and CSS on the other end.

Man that feels so good.

My typical development workflow:

$ ssh user@devserver
$ cd /appdir
$ git clone/pull
$ vim file
$ vim another file
$ tail -f /var/log/applog
$ vim file
$ git commit -am 'fixed the glitch'
$ git push origin dev
^D

Algorithms strike again :D

By the way I really much agree on both rants. People asking questions that they not even once typed into Google. Disturbing my workflow every 5 minutes...

There are three things in my workflow that I don't like:

1. Feature requests appearing out of thin air.

It's common to be handled work at 2pm that needs to be deployed by the end of day. Usually it's bug fixes, and that's ok I guess, but sometimes it's brand new features. How the fuck am I supposed to do a good job in such a short time? I don't even have time to wrap my head around the details and I'm expected to implement it, test it, make sure it doesn't break anything and make it pass through code review? With still time to deploy and make sure it's ok? In a few hours? I'm not fucking superman!

2. Not being asked about estimates.

Everything is handed to me with a fixed deadline, usually pulled off my PM's ass, who has no frontend experience. "You have two weeks to make this website." "You must have this done this by tomorrow morning." The result, of course, is rushed code that was barely tested (by hand, no time for unit or integration tests).

3. Being the last part of the product development process.

Being the last part means that our deadlines are the most strict. If we don't meet the deadline, the client will be pissed. The thing is, the design part is usually the one that exceeds its time (because clients keep asking for changes). So when the project lands on our desks it's already delayed and we have to rush it.

This all sounds too much like bad planning to me. I guess it's the result of not doing scrum. There are no sprints, no planning meetings, only weekly status update meetings. Are your jobs similar? Is it just usual "agency work"?

I'm so tired of the constant pressure and having to rush my work. Oh, and the worst part is we don't have time for anything else. We're still stuck with webpack 2 because we never have time to update it ffs.

Going to replace my laptop HDD to a SSD tomorrow. Can't wait for a better workflow.

Product manager had me spend an hour setting up his machine for rails development. Then walk him through all of our workflow. He then proceeded to make some changes to a header tag content. Made a pull request while I was holding his hand. Then he walks out of his office acting like he just won a national championship and proceeded to talk about how he was basically a developer for the next hour interrupting work.

Literally what I do 80% of the time at work.

I am the only one that:

Knows CSS properly
Knows SCSS
Understands how to set up a proper front end workflow
Etc
Etc
Fucking etc

I AM the css dude at work and I FUCKING HATE working with CSS, at the same time I take it upon myself to push through the projects because my team is shit at it and I would rather work with it than to have someone else do it and then fix their shitcode.

As a whole....i dislike design. Badly.

devrant now is really integrated in my workflow

We have a new member in our 3 ppl team, he started 2 days ago. Tomorrow the teamlead will have a day off, so I get to explain our workflow and systems to him and will answer any questions he has. Teamlead for a day. Let's see how that goes.

PayPal.

Found a nice method that does what you want? DEPRECATED.

Finally got that adaptive payment workflow all figured out? BREAKING CHANGES.

Want to use that new feature with your langs library? UNSUPPORTED.

Braintree isn't much better.

Anyone else is doing this? When you know you need to implement it, but want to fucus on something else and #TODO just doesn't cut it. xD

PM approves all UI and project gets assigned to me. He then makes tons of UI changes that will affect the workflow of the approved UI. To this point, code was clean and well documented. I request a few days to re arrange the code to reflect the new workflow. PM says: I need a minimal product. I don't need it clean. I want speed to ship and start marketing. That's where I stopped caring.. To the next dev, I am terribly sorry..

boss: we should map all the possible ways to do things in the system so we can test them and make sure we fix the bugs.

Me: yeah, well, that is exactly what automated tests are for, every time we find a non-mapped way that breaks this we make a test out of it and fix, this ways we end up mapping the majority of ways.

Boss: yeah,yeah ... Let's sit down latter and map everything on a document.

I bet my ass we are never gonna have tests as a part of our workflow.

!Rant

Designer decide to have a meeting with stakeholders about UX/UI workflow for control panel of our new embedded system (no framework, no library, gui is bit per bit rendered on frame buffer).
A week later, still nothing on my table, not a mail, not a call. Meanwhile I wrote a framework, the control system, renderer, and messaging queues between tasks.
Wrote some widgets, a layout system and a view swtching mechanism, and a separate stack control to use a "back" button.

Now I am stuck for I do not know what should happen when clicking on various (non obvious) items on the touchscreen.
Fine, I'll ask the designer.

"Oh, I will write the workflow next week" (ETA time, 2 weeks. Seriously? You take a week to draw on Adobe Illustrator 20 screenshot with text and I have another week to write it from scratch in C?)
Ok, while you write it, just tell me what should happen when I click an active item.
"Well, we didn't talk about that. We just decided the colour of the icons on the screen..."
For fuck sake...

The workflow my boss thinks works best:

1. Set a deadline for feature a, b and c.
2. Set some deadline for feature d and e. Before the end of deadline 1.
3. Tells us feature e will only be used to show it once to specific person X and never be implemented into prod.
4. Ask why feature a, b and c are not making fast enough progress
5. Tell us to prioritize feature a, b, c
6. Complain that feature d and e arnt finished yet.

It gets even better when he wants features done before finishing stuff it is reliant on.

Oh, and he wants to use scrum for this, of course. But changes the tasks he wants us to work on 1 day into every sprint.

Best girl i've met.

I attended a CMS Conference last month(I don't use a CMS, i'm just interested with the topics about DevOps and UI/UX). I met this pretty lady ( I find her cute and awesome.) who's one of the speaker, she talked about design principles and applying it to BEM with SASS. After the talk, i asked her some questions about her dev't workflow like what tools she used and some best practices. Our conversation went well and exchange some of our knowledge and ideas also i introduced her to devrant (She's a wordpress user, i showed to her how the community hates WP, idk if she registered). After her talked we separated ways and ended seeing again after the conference as she's looking for a cab going to a mall (Same directions where i'm heading to), We talked again and decided to have dinner together. I felt like she's the best girl i met as she's into TV shows i like (Silicon Valley and Mr Robot). We added ourselves in FB and saying goodbye to each other. After a week or two, i just found out that she already into a relationship and it broke my heart.

I guess im back to the start, but i'm happy that i made a new friend.

So I recently had a university project which focuses video game audio. We had to work in groups of 3 students and the task was to create a video game which uses audio as a gameplay mechanic.

Our idea was to create a game where you collect different audio samples which get looped as background music, and you have to select the correct ones to have a nice tune. To make it a bit more challenging we had enemies, guns and grenades plus doors which only open if the correct music is playing.

The guns fire on-beat, and the grenades always explode on the first beat of the next bar.
It was quite challenging to get things synced since even small offsets are noticable.

I wrote some nice code and theoretically it should have worked but for some reason the gun shots and the grenades didn't quite hit the beat of the music.

I tweaked stuff, created workarounds, optimized lot's of code to get execution times down but it still only worked sometimes.

I tweaked more and more only to realize that the timing drifted over time.

At that time I worked 20-30 hours on tweaking and trying to get it perfectly timed.

After recalculating some numbers I realized that all the audio samples are recorded at 135 bpm, but the guys who did the recordings said it was 130bpm.

I asked them if it could be the case that the samples are 135bpm and they said:
"yes, they are at 135 bpm as we told you"

I scrolled back in the telegram conversation only to see that they said 130.
Changing the number to 135 resolved all the problems and all of my workarounds and tweaks weren't needed.

So I worked for nearly 30 hours just because they didn't notice their fault and even when they realized that the timing is off sometimes (which took forever because they never played the game), they didn't even consider that they might have given me the wrong numbers.

This all wouldn't be that bad if both of my teammates had worked for more than 15 hours but they didn't. I did all the hard work and the only single thing they did fucked up my workflow. It fucked up the system I created and it fucked up the gameplay as things got unpredictable. Because of their fucking fault I worked as much as both of them combined IN ADDITION to all the other work I did (built 3 maps, coded everything, created animations, ...)

I love working in teams, but only if the whole team is motivated. Those two fuckers were the exact opposite.
Luckily i found the error so I could fix it, but guess with whom I'll never ever work together again?

It was my internship and I've end up working on a law company specializing on Australian construction laws they're working on a website that will take care of all the paperworks for the contractors. They have a dev team who's working on it but they don't have a web designer. I was accepted for the job as an intern/web designer/tester. I was so happy that I've got a really cool internship as a designer but that's only for a second.

The hell starts on day one. They've told me that they're using agile workflow and that they need to make the website responsive. It was based on bootstrap and gosh their code was so broken. HTML tags overlay on each other, some are unclosed. I've tried to fix the problems and did a great job at that. Made the front page responsive and all laid out. When I went to the next php file it has a different header.php and footer.php and same problems apply and we're not even touching the worst.

They didn't use any version management and they're cowboying everything. Now that the website is on the staging server they use Cpanel text editor to edit the code! My headache started to pileup.

The Australian client asked me to provide icons and fix the colors of the website. Also the typography looks great already. I've fixed almost all the problems and I'm satisfied with the design when suddenly a new co-worker from a famous and expensive college was absorbed by the company. He worked as the marketing specialist who has no experience at web design at all. He told me to do this and that and the whole website changed. He bullied me for my skills in design (I'm an intern) and just took over the whole design. Everyone even the boss listen to him as if everything he say is right. He's skilled at design but not web design. He made the website look like a freakin movie poster.

All my works are for nothing, I got headache for nothing and I've got hated for nothing.

It was the day when I finished my internship. It was a long 3 months. After a month I've heard from my co-interns that the whole dev team was fired including the marketing specialist. Also the whole website is scrapped and has been rebuilt by a single guy who used WordPress which he did in only a month.

So... Manager pulls us in. Meeting in 10 minutes guys. I know it's unplanned, but it's important.

Not only is it the 10th time he's interrupted my workflow, but it's almost time to go home. And I was getting some important shit done.

Anyways, come the meeting: we are going to abandon all the work we've done on our microservice platform (2yrs+ in the making) and make it a monolith. Oh, and we have to do it in 4 weeks, because a client is asking for it. Oh, and you'll probably have to do overtime.

🤦‍♂️ FML

I feel like the web frontend landscape has gone to hell...

It used to be a priority to develop lean front end applications that load fast and work the same on most devices. If resources are required you try to share them. I have always liked the way this was solved using CDN.

Proper workflow: include some small libs you might need, script your interactions, test site, deliver.

And now our friends of the Javascript community have discovered the nuclear science called npm... It started off as this great benefit allowing frontenders to complete entire projects in the language they know and love but I feel like it has grown into an abomination that produces bulky applications with more boilerplate configuration than actual active code...

Surely I can't be the only one who is completely fed up with the direction this is going? Is anyone else looking for a lean way of developing javascript again using only a couple of small libs instead of those monstrous frameworks.

I have even considered to develop a library that makes it easy to develop with CDN (and dependencies) in mind but I don't even know if it will be worth it as more and more people tend to move away from it.

I'm sad

After working 3 years in my current job and my boss hating anything to do with unit testing etc, I used my spare time to refactor our Makefiles to allow for the creation of unit and integration tests. I technically didn't tell my boss about it, so my heart was in my throat when he Skyped me with 'what did you change in ...'?

After having bashed any workflow with testing in it, I showed him the new workflow and automatic testing in Jenkins and he was actually enthousiastic, just like all other employees! I was hailed a hero in the R&D department, after all this time we can finally write universal tests. :D

So lets see if i can get this devrant stuff right.

So a couple of years ago i worked for this company, where i worked in datawarehousing and business intelligence. I was in my 3rd year of working as a software engineer and was full of ideas, motivation and just wanted to do cool stuff.

Anyway, after the first couple of months of working where i learned what they actually wanted to achieve, i got some ideas on how to improve the workflow. They were just simple things, like updating our IDE (we were working with a very old Visual Studio version), getting useful editors, using some more modern ideoms like unittests, continous integration, etc. Simple stuff really.

So in my endless naiveness i went to my supervisor and told him my ideas. He was not particularly interested in my ideas and cut me off somewhere in the middle and said that he would talk to his boss.

So a couple of weeks after that (nothing happened), i went to him again and asked about it.
M:" Hey Bossman, have you thought about my ideas?"
B:"Yes."
M:"And?"
B:"We won't do them."
M:"None of them?"
B:"No."

So at this point i was a bit bummed out, but surely he has a good reason right? So i asked why.

M:"Why?"
B:"Well, because we always have done it the way we do it now."

I think i had a bit of a blank stare at that point, because he looked at me funny. If we would do things like we always have done them, we would be still in the stone age you moron.

God i hate it when people say stuff like that.

Planning.
- Sales people: we will deploy and install 100 customers by the end of the month.
Meaning: 100 it's impossibile, we want actually do 50, but we set a high target so people will sweat their ass off. But we don't tell them the truth.

- Tech people: no way, we will deploy and install no more than 25!
Meaning: we could do 100 but we would die. We will guarantee 25, but since we are good we will optimise the workflow and maybe we will make it to 50. But we don't want to create expectations.

Big misunderstanding arise if these two language are used in the same meeting.

At least if I'm in the meeting as technical people

Invited a colleague to my private bitbucket repo, he said I'm risking our company code to the public, then I removed him from AWS, left him alone with his ftp workflow. And he's a senior programmer. Fuck that idiot!

! exactly dev

I'd ditched Windows and spent a while exploring the Linux ecosystem for content creation. And I have to say, it was not a nice experience.

As much as I respect the Linux mantra of "free as in freedom" and "you need to roll up your sleeves and figure out stuff on your own", it just isn't good enough for non-dev work. Sorry guys, but I need software that gets out of my way and at least does what it's supposed to do. I can't stand a horrible UI or delays and random crashes, which is exactly what happens with most things under Linux.

To replace my Windows workflow I used the following:
1. Windows -> elementaryOS (because Debian/Ubuntu repositories seem to have the best software support, and elementaryOS is the least horrible looking thing that supports that) and then Arch, because, well, Arch.
2. Blender + Maya -> Blender + Maya on Linux.
3. Reaper + FL Studio -> Ardour + LMMS.
4. Photoshop -> GIMP + Krita + Inkscape.
5. ZBrush -> nothing :(

As you can see, my use cases are pretty much all over the spectrum.

Firstly, installing and configuring stuff. A pleasure on Windows, an absolute pain on Linux. Everything just worked on Windows, I had to wrestle with library versions and patches and unstable audio layers (Linux audio just sucks, except for JACK) on Linux.

Out of these, Blender and Maya were the best experience. But even then, both would suffer from random crashes that just didn't happen on Windows.
Ardour is actually really nice when it works. Its use of JACK for routing makes it really really flexible, but it just isn't stable enough to depend on. LMMS is utter crap. I'm sorry, but I just hate the UI. Can't stand it.
GIMP, Krita, and Inkscape can't beat Photoshop, even when you consider them together. Adobe software workflow is just so much better and more intuitive.
Blender 3D sculpting is not bad, but it's nowhere as good as ZBrush.

Also, if you're a C++ dev like me, nothing beats Visual Studio 2017. Nothing. That IDE just blows everything else out of the water. Even VSCode. And it's not slow at all, it handled a fairly large project (PBRTv3) just fine on my Windows development VM. Yes, a VM.

So...I ditched Linux and went back to Windows, but I keep Linux as a VM for when I actually want to mess with Blender or Ardour. Or some dev stuff which Windows sucks at (which is becoming less frequent because of WSL).

Out of all the above, the only one I'd consider ready for production use would be Blender. Developers of open source software, please learn from Blender. Kickass UI and user friendly operation is extremely important, you can't make a random window with GTK buttons and text boxes and arcane config files and expect people to use it for serious work.

Also, Windows beats Linux hands down as an everyday OS. It's always been rock solid, if you take care of it properly (and that goes for any OS). Updates hardly take any time because I run it on a SSD. As for all the advertising and marketing bullshit, you can block a large amount of stuff. And for what can't be blocked, well, I just have to live with it, because the alternative is compromising on my creative output, which is too much for me.

I still run Linux on my server, though. And on my embedded devices (Pi, BeagleBone, etc.). It absolutely rocks there.

I realize that Linux software is not going to improve unless we do something about it, so I'll be contributing fixes and code (the joys of being a C++ dev, yay). Still, I feel that the platform and software as a whole is just not mature enough.

Was office SharePoint bitch at one point. This guy wanted me to build a workflow for him that would enforce insane checks on his (peer) colleagues. Asked if his manager approved and obviously they hadn't. So this guy started telling me he would build his own application from scratch and host it on his home server if I didn't help him. Pointing out the business might object to their confidential data being put on his home server didn't put him off. Getting laid off a few months later for gross incompetence did however.

I love Test-Driven Development!

And because of that fact, my heart shatters into thousands of pieces, when I recognize error events on our production nodes which are pointing onto a golden hammer function in a legacy project.

This particular function has about 300 lines with a bunch of subfunction calls and instantiations of helper-classes returning information for workflow.

Refactoring this code to apply proper unit-tests requires a way bigger investment than simply deal with 30 eventlogs a day, because this kind of payment is barely used by customers of our webshop.

This fact is a little itch each day of my work.

Guess it will make me go insane one day
¯\_(ツ)_/¯

xD

I hate some parts of this company.

They literally have a "Designer" which made a mockup for our new UI and honestly when I first saw it I almost threw up.

Having made a lot of designs myself for personal projects and for fun I LITERALLY SAW he barely put any effort into it he just threw some stuff together took a shit on it and called it a UI.

For that interview we were actually expecting wireframes and not mockups since we were not sure what workflow we wanted for the UI.
Of course this would have come with feedback from us and then would have been reiterated and this was clear from our last talk with him.

Maybe he didn't know what wireframes were ¯\_(ツ)_/¯

If this wasn't enough, he was also consistently misspelling words all over the place, not aligning parts of the UI, misplacing common UI elements and stupid stuff like having a GIGANTIC + button for adding a object to a list for a NO TOUCH SCREEN UI.

(The plus button was all the way to the bottom left of the screen as far away from the list so users get a good hand workout).

But everyone just loved it because "We have known him for a long time and he has a big portfolio so he must know what he's doing".

I couldn't bring in anything, you truly notice the difference between "I don't agree with your opinion but you are heard" and "Shutup my buddy the designer is amazing".

I was not being an asshole I was giving critique on specific parts of the UI and not just saying "it's shit" hoping we could improve on it. Still having naive hope for the future of this project.

He even looked kinda mad and irritated by my opinion and just looked at the people previously mentioned.

I truly hate people who just keep using the exact same worthless piece of garbage people because they have known them for a long time.

Personally I wanted to grab him off his chair and throw him out through the window, 2 floors down, straight into the garbage bin, making damn sure he doesn't accidentally fall into the recycle bin.

Never ever would I enjoy or like this application's UI if I had to work with it as a user.

Workflow?
No source control. No documentation. No testing. Do everything on live server.

Had a five hour long debate with one of our Senior Developers today about pull request etiquette.

His view was reviewers should always email or call him before adding comments to any of his requests and they should never block them as he should be allowed to code in "his own style" and should be able to approve his own pull requests.

I explained that we have code standards and an agreed PR workflow be needs to comply with.

He then started talking about meteors and plane crashes. Literally no helping some people.

I'm sick to death of hiring people from other companies and explaining GitFlow and why its useful (what are you people doing?).

Then watching them doing it wrong, pointing out its easier to use something like sourcetree. Which leads to "... well see, the terminal is just more efficient, tools like sourcetree are bloated".

Ok fair enough, well heres the deal i'll make with you, while using your "efficient tool", stop breaking our workflow and i'm fine for you to keep using it. Otherwise, stop being a dick and be a team player.

1. Project start: requirement gathering
2. Create workflows and prototypes
3. Customer confirms the workflow and prototypes
4. Develop the system
5. Initial feedback : customer is happy
6. Testing and deployment
7. Customer changes the requirement to something completely different and says you just need to click a button to implement the changes

Wtf!!!!!!!

To any and all family members, before requesting my help with the printer/computer/electronic device follow these steps to make sure I don't get irritated.

1. Make sure it's plugged in.
2. Turn it off then back on
3. Turn it off, unplug it for around 30s, turn it back on.
4. Request help

Why is this so hard to grasp? I don't want to stop my workflow with an issue that could be resolved in less than a minute!

Within his first 3 workdays, my new colleague witnessed my colleagues' false singing, the Christmas tree decorated with broken key tags, and the Friday afternoon beers + online fail videos - and a little of our workflow too. I think he's gotten a good general impression now 😂

It was so frustrating setting this one up. Lots of shouting in front of my monitors. But I think now I'm slowly getting somewhere with my first i3 setup.

Now to see if it will actually improve my workflow somehow.

We use scrum in our company.
And with scrum I mean we don't have a scrum master, our senior developer is the project owner, we estimate in hours and the estimate is binding, so you are not allowed to work longer on a task than the estimate.

So yeah.. "scrum"

Sins? I don't want to keep you up all night, so here are some highlights.

Fucking with clients and employers who fuck with me first, or waste my time.

Occasionally not documenting my code (I'm actually pretty good about this), then bitching about poorly documented code.

Honestly wishing other people in the office would *actually* explode, or die engulfed in flames.

Working drunk and/or stoned.

Getting pissed off when I have to do something in a stupid way, or use a workflow that I don't like.

Seriously fucking up out of either arrogance or stupidity, then blaming it on something else.

Zoning out, skipping work, or sleeping in and billing for it (see sin #1).

But my greatest sin? That honor's got to go to becoming a developer in the first place.

I wasn't always a professional asshole, but I fucking am now.

!rant
if you're someone who grades code, fuck you, you probably suck. Turned in a final project for this gis software construction class as a part of my master's degree (this class was fuck all easy, I had two weeks for each project, each of them took me two days). We had to pick the last project, so I submitted final project proposal that performs a two-sample KS test on some point data. Not complex, but it sounds fancy, project accepted. Easy money.

I write the thing and finish it, it works, but it doesn't have a visualization and that makes the results seem pretty lame, even though its fully functional. SO I GO OUT OF MY FUCKING WAY to add a matplotlib chart of the distribution. To do that, at the very bottom of the workflow, I define a function to chart it out because it made the code way more readable. Reminder, I didn't have to do this, it was extra work to make my code more functional.

Then, this motherfucker takes points off because I didn't define the function at the very beginning of the code... THE FUCK, DUDE? But, noobrants, it's "considered best prac--" nope, fuck you, okay? This class was so shit, not once was code style addressed in a lesson or put on any rubric - they didn't give a shit what it looked like - in fact, the whole class only used arcpy (and the csv mod once), they didn't teach us shit about anything except how to write geoprocessing scripts (in other words, how to read arcGIS docs about arcpy) and encouraged us to write in fucking pythonwin. And now, when the class is fucking over, you decide to just randomly toss this shit in, like it was a specific expectation this whole time? AND you do this when someone has gone out of their way to add functionality? Why punish someone who does extra work because that extra work isn't perfect? Literally, my grade would have been better without the visualization.

I'm not even mad at my grade - it was fine - I just hate inconsistency in grading practices and the random raising and lowering of expectations depending on how some grader's coffee tasted that morning. I also hate punishing people for doing more - it's this kind of shit that makes people A) wanna rip their eyeballs out, and B) never do anything more than the basic minimum expectation to avoid extra unwanted attention. If you want your coders to step up and actually put work in to make things the best they can be, yell at a grader to reward extra work and not punish it.

Depressed since yesterday.

Updated all our clients Dialers. Stellar performance. Suddenly one of 15 can’t hang up three way calls.

It’s one of our biggest clients. And they just started. We upgraded the dialers so the answering machine detection would improve for them and it did, along with vast performance upgrades as well. Suddenly, this issue.

2 days in they pull the plug until we fix it. The issue is sporadic and we cannot reproduce. No one else is having the issue. I can’t even debug it properly as it’s a third party dialer with no customizations on it. I found out where the error is, but no idea the workflow they got it to happen with or why. It’s so frustrating. It happens using the dialer native interface, and our integration via api calls. The channel doesn’t get sent to the command for some random reason, and only sometimes.

So even if it’s fixed they don’t trust the system. Now they are losing the full integration we have with the crm and dialer and it’s going to be a mess of data for them. All because of this one issue. They love the CRM though...

If they had just stayed on one more day I’m sure I could have found it. Now I have to play forensic scientist and look through old data, without being able to see the client code that was causing the issue.

Just threw some cash down to be able to talk to the dialer engineers and hopefully see what’s up. What a nightmare. And I have so many other projects for the platform due so soon...

Sigh. Super depressing.

Client: How long will it take you to build this?

Me: Maximum of 7days

Day 1 to Day 5, To myself: I have so much time, lemme build a Js engine in Rust and open-source it. It shouldn't take that long.

Day 6, After many failed attempts at debugging RegExp:

Starts working on the client's product, scraps off sleeping hour (why do I sleep in the first place)

Day 7: At 23:59...calls clients, he doesn't answer, probably sleeping... Sends message "Product ready to be tested at your call, I've not slept in 7 straight days because I like you"

Now that github is also offering unlimited private repos to free users, I'm thinking of using it as a backup of my gitlab private repos.

Like pushing to a gitlab private repo auto push to a github private repo kind of workflow.

I will search how to do it online.
However it would be awesome if anyone with similar previous experience can share their wisdom here 😁

Ranting after many light years (oops that's a unit of distance)

Damn Damn Damn.

There is complex workflow engine, and the only thing I know is once you fix and get success response from method A(), call method B().

After 2 days and nights effort, method A() is fixed and I am getting success response.

Now, when I pass this response to B()

One data is missing and hence failing.

Where the hell is that data getting kicked out...

I am in a dead end. I don't even know where to look.
Pinged engineers for help but all in vain till now.

Working on one of world's largest system, and I am miserable in debugging with this system.

And the worst part is there is nothing that I can turn off and on so that it works.

(Don't blame me. I am not that dumb. I just started using it since 3 days)

Forgot to go to sleep again, and here it is another fucked up Monday.

a very polite recruiter in linkedin after our connection asked me why i choose this kind of career. I answered this and i hope i did not ranted a lot :)

i was trying to figure out what profession would make me more happy than others. I was always felt comfortable with computers, i was installing cracked games, exploring folders to paste the cracks etc. later in school when i learned the first algorithms like bubblesort i was knowing that i liked it. I also like working in silence while searching for solutions. That is the first part, the second is that i made a search about what industries would give me a safer future and international opportunities without having to be stuck in my country only. By working and getting more experience i felt in love with my job and trying to learn everything i missed and give to my boss or customers professional results with quality. I like it as a lifestyle, it combines a magic feeling of spells with the logical procedures of science. So why not? it combines all my loves together: creative thinking, technology, mental work, internet, music at the workflow, job demand, opportunities, and money! I hope i helped you my friend i am at your service for every question you have :)

The moment when your forced to use mySQL after years of blissful coexistence with a noSQL workflow.

I finally bit the bullet and got a 2018 macbook pro i7 with 1 terabyte ssd. I've been needing a personal laptop for development for awhile. I thought about going full Linux but it's tough finding Linux laptops that support thunderbolt 3 charging.

I tried to make Windows and WLS work. But it's a pain getting my Golang, GCP, and Kubernetes workflow setup on it. I keep having to jump command prompts and it annoys the shit out of me. Going multi monitor helps a lot, but I like to be at coffee shops and code.

I feel sick a out giving Apple more money especially $3,000. But it was money well spent. My workflow is seamless and unlike on my Windows laptop I dont spend 3 to 4 days just setting up my environment.

A coworker changed the application deployment process. He told all three of the other developers who need deployments, but not me. We sit six feet away from each other and I've run/managed deployments for a year longer than him.

His new process doesn't work and he's blaming the dev ops team for not following it. The new process clearly doesn't fit their workflow and never could have.

The lack of deployments have caused production issues and he still won't ping dev ops to remind them about the deployment because "it's not in the new workflow".

He's been painting dev ops as incompetent at the last three retrospectives without having ever personally reminded the deployment guy.

Ugggh.

I don't know what you did yesterday, but i did make my company throw away 2 months of progress.
It all started in the beginning, since that i've made numerous complaints about the workflow or code and how to improve it. I've been told off every time, and every time i either told the boss who agreed in the end or wrote code to prove myself. Everything was a hassle and my tasks weren't better.
Team lead: you'll do X now, please do that by making Y.
Me: but Y is insecure, we should do Z.
Team lead: please do Y
Later it turns out Y is impossible and we do Z in the end...
Team lead: please do W now
Me, a few days later: i've tried and their server doesn't give http cors headers, doing W in the browser is impossible
Team lead, a few days later: have you made progress on W?
Me: * tells again it's impossible and uploads code to prove it *
Team lead: * no response *

After that i had enough. Technically i still was assigned to do W, but i used my time to look over the application and list all the things wrong with it. We had everything, giant commits, commented out code, unnecessary packages, a new commit introduced packages that crashed npm install on non-macs, angularjs-packages even though we use angular, weird logic, a security bug, all css in one file even though you can use component-specific css files...

I sent that to my boss, telling him to let the backend-guys have a look at it too and we had a meeting about this. I couldn't attend but they agreed with me completely. They decided to throw away what we have already and to let one of the backend-guys supervise our team. I guess there will be another talk with the team lead, but time will tell.
It feels so good having hope to finally escape this hellish development cycle of badly defined task, bad communication and headache-inducing merges.

So today I was offered a job at the company as a junior frontend developer. Digging a little deeper I found out that they don't have any other frontend devs in house.

So the job offer translated to:
- senior skillset
- senior workload
- junior wage

Best part is that I was freelancing for them in past and was helping to establish some of the workflow a year ago for more money they offered now.

Thanks, no thanks, I guess?

Rant time of 'Derp & Co.'

Today I decided that I am going to find another job, I just can't keep with this shit.

They said that use Agile: FALSE.
• Daily (best scenario) take like 1 hour and a half.
• New task enter the sprint and "Fuck you, more task in the same time". This is something regular done.

• "Oh, dev, we need you to check this other project" I am in the middle of my sprint on this project. "But you have to fix this bug here". (3 fucking days the bloody bug) "You are late again with tasks".

• Meeting for fresh sprint: 6 BLOODY hours... nonstop

The workflow is garbage:
• SOMEONE should did all the devops shit on the first sprint, guess what? They did nothing!, guess now who is being blamed for it (not only me, but a few coworkers).

• Nothing is well designed/defined:
~ task are explained like shit
~ times measured wrongly
~ We are in the last fucking SPRINT and still doing de ER of the DataBase cause Oh, apparently no one has work before with SQL (damn you MongoDB! (Not really)) so I am doing my best, but "jezz dev, this is so hard... maybe we can do it WRONG and easy".
~ No one is capable of take responsability of their mess, they just try to push down the problems. (Remember the devops situatuion? Why is.my fault? I came at the 3 or 4 sprint and I am doing backend tasks, I know nothing about devops).

But the big prize, the last one:
• Apparently you can't send whatever you want to the boss, it has to pass a filter previously of coordinators and managers, hell yeah!

And I am an idiot too!
because I see that we can't reach our schedule and do hours on my spare time!
This is because there are a few good coworkers who probably ended with my unfinished tasks... and they are equaly fucked as me...

This is just the tip of the iceberg. I am not a pro, I am not a full stack developer and still need to learn a lot, but this is just not normal, eight months like this...

I recently had to switch back to using windows after almost 4 years of various Linux distros (Thank you electronics industry).

I feel completely unproductive without the command line and Guake.

How long does it take to shake the Unix workflow?

I started my actual gig as CTO of construction group (Innovation Hub) a year ago. And it was a hell of a ride, implementing kind of a scrum-ban for project management, XP, peer-reviews, a git-flow, git commit message formats, linters, unit testing, integration tests, etc...
And it's the fun part because with the CIO we had to drive the board to do A LOT of changes in their IT/Innovation drive.

But in one year there is a lot of KPI that went up :
* Deployment: When I arrived it took three stressful days to deploy a new version of one application, once a month. Today we do it every week, and it takes three annoying hours.
* We had no test. NOTHING! Today we have 85% code coverage for the unit test, and automatic integration tests run by our CI server every day.
* We had almost no documentation. Today our code is our documentation (it automatically extracted and versioned).
* We had 0 add value in the use of git. With commit messages as "dev", "asked task", inside jokes and a lot of "fix" and "changes". Today we have a useful git, and we even use it to create our deploy changelogs (and it's only mildly annoying!).
* More important, the team is happy! They get their purpose, see betterment in their tech mastery. They started doing conception, applicative architecture, presentations, having fun.

There is still a LOT of bad things we are still working on, and trying to solve (support workflow and betterment). But seeing what they already did, I'm so proud of my TEAM! I'm a fucking asshole, workaholic, "just do it" kind of guy. But they managed to achieve so much. Fucking PROUD!!

Our class has a google docs document where we take notes for our technical subjects. I sneaked in a little note about git: "git push -f" is the recommended programm when pushing to origin for a smoothless workflow.

Let's see how many sheeps follow my instructions blindly😈

Okay. I’m upset. So the recent .NET update Microsoft put out fried SharePoint which I am currently the main point of contact for at our company. In addition, my only current projects are creating workflows.

I was publishing a workflow and got an error. I googled the error and found that it was the .NET update that caused it. Internet says to edit the web.config file for your web apps and it will be good to go. I go to our networks guy (only available supervisor) and explain what happened and ask about the recent patch and whether this could be the cause. He says that his team doesn’t actually handle the patches so I should speak with the HelpDesk lead (don’t ask).

I go to the HelpDesk lead and explain the situation, explain the solution and ask for what to do next. Keep in mind that this whole thing takes two hours because it’s Friday and everyone is out and I can’t do any of my work while I’m waiting on this. HelpDesk lead says “you have an admin account, I trust you. Go fix it” so I think uh okay.... I’m a junior and not even technically an IT person but sure. I know how to do it - but got nervous about fucking it up because our entire organization uses Sharepoint.

Nevertheless I go to my desk and look for the root directories and find that they’re on a server somewhere that I have no access to. I message the Helpdesk guy and tell him this and he says to talk to the developer supervisor. Great! He’s super nice and helpful and will totally understand! Only he’s not in. Neither is half of his team.

I go to his team and look around and find nobody but realize I may be able to catch one of the guys I know and work with in the break room. I start leaving and am stopped by a developer who is generally nice and funny. I explain the situation and he says “you... YOU need to edit a config file?” And scoffs. He demands to see what I’m talking about.

I walk him to my machine and show him what’s going on and all the research I did. I start to realize he thinks I’m overstepping and I begin to apologize and explain the details to why I was asked to do it and then I say “I really shouldn’t even be the one doing this” he says “no you should not. This isn’t getting done today. Put in a request, include your research and we will see what we can do when the supervisor gets back next week”

His tone was like I was in trouble and I know that I’m not, but it’s my goal to end up on that team and I just feel like shit about this whole situation. To top it off my boss pulled me off of two projects because of unrelated issues (and nothing to do with me) so I have basically nothing to do and I just feel very discouraged. I feel dumb and like I should have gone to the developers first. I just wanted to make it easy on everyone and do my research. I feel like I keep being put in situations above my level (I’m one of two juniors in a 16 person shop, the other one is an intern) and then “getting in trouble” for working beyond my scope.

Anyways.... fuck Microsoft

!rant
Looking for advice, serious advices.

I work in C.
Also, I work in Python.
I have worked for a couple of year in C++.
I have a fair knowledge of the Data Science workflow, and some experience in Machine Learning.
I have tinkered with some other languages (Java, Ruby, Go, JS among the others, nothing serious nor professional)

I'm the kind of person who needs constant problems to face in order to keep engaged, satisfied, happy. And I need to learn new stuff, or refining my knowledge constantly, or I stagnate. I believe that this is true for quite a share of people here.

I would like to spend some spare time (I seldom have) in a project. Personal projects are rarely good enough to improve one's cv, so I thought I could partecipate in some Open Source projects.

Does anyone here have some suggestion about some interesting and satisfying OSProject, or some general suggestion on the matter?

It would be so apreciated.

SharePoint things that I get yelled at by customers for:

Setting up page permissions wrong (even though the real problem is that a coworker didn’t check the page in)

Writing the workflow wrong and nobody is getting emailed (even though they didn’t select who to send the email to)

Not magically knowing that they wanted the new intern (who started Tuesday) to be given full design rights on their page

Not magically knowing that their discussion mod quit a year ago (before I started here) and now nobody can feature a post

Not spinning up an entire new site so that they could post a link to a single sign up sheet for their team (of 10 people) barbecue

Somehow making it so MS Edge can’t handle high res images correctly (because I totally created Edge (which isn’t even a supported browser here))

Not responding immediately when they submitted a ticket at 7:00pm (I’m off at 5) asking me to change one word on a page they have edit rights to

Not giving their admin assistant global design rights for our entire organization

Not giving them access to a confidential folder that has nothing to do with their job

Telling the owner of aforementioned folder that they’re not allowed to store confidential data in SharePoint

Making workflows too confusing for them to figure out

Fixing shit workflows that their ex coworker built wrong

Generally having the word SharePoint associated with my name

You know what really grinds my gears more than anything else? Not having anything to work on at work.

That might sound like the most german thing to say but bear with me for a second.

Even though i am almost one year into my job as a junior dev, i consider myself and i probably am very new to the coding world. And even if i weren't new i would still have to continuously learn and improve. And every time i just sit in front of my working station, with nothing to do, i'd rather figure out an incredibly tedious bug, learn lisp or deal with a shitty framework.

Most of the time i don't know what to do. I improve my workflow with some bash-scripts and aliases, i read into the details of certain tools but at the end of it, i can't really get into something deeper and get value out of it because actual work might just be around the corner...

I swear GNU/Linux is the pure definition of a badly designed OS/Kernel

1) The separate file system. Of all things, all the set standards Linux uses exFat which can only be read by Linux. Not NTFS, not FAT32, you know, the common ones.

2) Unintuitiveneness and inefficiency of workflow. Linux is extremely inefficient, especially the cli versions, where one cannot perform several tasks simultaneously.

3) It's MESSY. The use of a Terminal is incredibly uncomfortable, because the text is tightly spaced, and in monochromatic in root. When looking at a large chunk of text, my eyes hurt on a deeper level than physical.

4) It's the most retarded way to handle drives. Why not assign drive letters and names? Why is it dev/sda1 dev/sdb1. If I have two drives of the same capacity, I cannot differentiate between them. How am I supposed to know which is my system drive and which is my portable hard drive that I'm formatting? And this stupid disk utility fdisk. What the fuck is that? Why is the command o wiping the device? Why is t selecting a partition? What the fuck?

5) Stupid naming system. Most CLI commands have deliberately stupid and hard to remember names. Also the prefixes to them such as -x -c or -v, say nothing to me. Reading through the manual in white, tight monochromic text is impossible.

6) Error messages that don't make sense. How am I supposed to know what "Error! [err=/dev/null, arch="27xE39Tmx849D" result="success"]" is supposed to mean? A search will cut down the error and I will find nothing.

7) General hype towards it being "focused on developers". It's not. It's really not. As a developer myself I find it absolutely painful to write code on Linux. It's sluggish, requires it's own set of IDEs and software packages.
People say "Oh you can't write and compile code on Windows". Yes you can. Windows has the exact same set of compilers as Linux, like gcc and gpp. Windows has a versatile and powerful command line. It's hidden from a regular user, because its actually user friendly, and is made for people, not aliens. The fact that you have to download a package manager first to access new ones is what flies over many peoples heads.

Go on start a wreck in the comments

I got an extremely hard task in the morning, I asked for some clarification and I got them at 13.23.
Boss ask for updates at 13.45 (during lunch pause).
I work on it 2 hours like never before, he calls me and I said I can manage to finish in half an hour + testing.

I work more 10-15 minutes, time is around 16.15.

2 other enormous bugs shows up on the same project, boss ask me to take care of them, and I manage in only 2h to look up something like 40 web pages and correct each of them, write reports and inform the affected people. After it I work more 15 minutes to report and finish small tasks. Ended up working almost 1h more on a non paid extra time working contract.

In the morning, while my boss was aware I spent that time

In the morning boss ask "everything went fine with the big project, right?"

Because
The
Client
Is
Angry.

I already got a burnout from this job, I really can't go on like this.

Xcode storyboards

I can't do it justice by explaining how many times having the entire UI flow in one file has helped me.

Even for unexpected stuff, like an Android dev joining the team and needing to know the workflow of login / registration -> print screen the storyboard.

Manager asking for all the different possible paths through the app -> print screen the storyboard(s).

And then live rendering of custom components to be able to see them while playing with alignments.

While it has its bugs, and could have a few more features, it's too useful to ignore.

I know many iOS devs don't like it, and that's fine because I don't like them either and I don't hire them ;-)

!rant

Linux edition!

Story time:

I worked at a firm that had an infernal off the shelf CRM system that they collaborated with the dev company to customise.

They were seriously behind the competition, and didn’t have any app or web presence for interacting with their system, instead relying on people calling (fine for the nature of the business, but competition was leaving them in the dust).

They decided that they needed to redevelop it in-house, with a focus on supporting the web and apps.

I was hired for this purpose.

It was me and one other dev, who was also the head of IT.

He’d built a small prototype, and was new to the whole WPF / MVVM thing for the in-house app, so with my previous experience it was clear it needed to serve as an example only, and that it would need redeveloping.

I was only there three months.

In that time I singularly (he was pulled away to troubleshoot their VOIP installation - yes, for three months as other companies kept dropping the ball) built:

- A WebAPI with JWT auth
- An MVC skeleton frontend
- A WPF desktop app

It had all sorts of cool shit in it, 2FA, Reactive UI, Reactive extensions, server push to desktop, a custom workflow and permissions system.

It was pretty dang cool.

End of the three months rolled around, and the non-technical managers were concerned about time to market, so they decided to drop me as I’d “not made enough progress”.

I’d also had a bit of absence which they were aware of and were supposedly supporting me through.

But MFW three months is assumed to be enough time to build such a system with one dev.

!rant

This is a major part of my workflow, and I wanted people to see it. So I went an inch-deep on quicktime screen recording and ffmpeg flags to produce this low-quality gif.

I pop open the alfred text window with cmd-space, and have it set to use DDG as my default search provider fallback. In this way, I'm able to execute bang-searches without having to load any urls, or even move the pointer.

What kinds of productivity/workflow tricks do you use?

4 years ago I made a personal goal/plan to be a full stack developer. Meaning a good understanding of any development between os level code and web/front end user experience.

Over the years this term 'full stack' has been abused greatly and now basically means 'a javascript developer that generally knows what they are talking about'.

So now, devRant collective I ask you. What do you call a developer with good skills in:

- os level code (c, c++ and os apis)
- database level tech (advanced querying and db aglo/modeling)
- software architecture
- application level (workflow and business logic)
- transport level (protocol design and usage)
- front end tech (graphics programming and event driven paradigm)
- user experience

Pretty accurate

I really want to stress that we should add the ticket for adding the missing test cases in *this* sprint and not postpone it any further.

-- "Isn't there something more important to be added instead?"

There. ALWAYS. Is. Something. MORE. Important. The real problem was that we implement the test cases in the past to begin violating our definition of done. We have to fix and one point and we have to own that decision as nobody else will care about passing tests and test coverage. It's our job to care for that.

Yes, we can instead focus on all the other high-priorities task that should have been done yesterday, yet that won't change the fact that large part our codebase will remain an untested messy blackbox just asking for weird bugs and wild goosechases in the future.

Don't hide behind "high priority tasks". A job is done when it is fucking done and tests are part of that. Hurrying from one important task to the next will just mean we'll never do it. There is no better time than right now.

If code coverage got left behind in the past, then we'll have to suck it up in order to fix it as soon as possible, otherwise we'll just suck forever.

Hey Guys
A few Questions I have to decide soon, for tools I never used:

1- How do you guys keep information about several accounts and stuff? Must have some protection to not be easily accessible (started using Google Notepad and Evernote until I find better... don't really like them)

2- Firefox: Is there a way to store groups of open tabs?
Like I have one windows with 6 or 7 tabs for movies (youtube and such), other for general stuff with 5 or 6 tabs, other with Arduino shit, and I'm going to pick Vue soon and another language to build native apps and that will be a lot more tabs, It would be nice to close them all and open them all at will or something.

3 - What Is your favorite browser? I'm using Firefox, but there are so many new good ones... Like Brave browser with Tor incorporated, or Puffin for Android (which uses a VPN with their own server by default)

4 - For windows users, do you have any tools to help with workflow installed? which ones you use and why?

5 - What I'm using: Google Notepad + Evernote to save stuff, Windows 10 and Firefox, (Linux Mint in VM) and I just keep my shortcuts in folders... I don't use the Windows taskbar for a long while since its so full of shit.

6 - How do you do your backups? Right now I'm just putting my code and important stuff in Dropbox.

I'm an old school programmer... Stuck in 1990's Ideas and there is so muchhhh shit these days that I would prefer your opinions then just googling.
Guess that's enough for this post. Thank you guys

Only I can break the workflow of main app our project is using in the second day on this job...
Guys, always read the documentation before even touching anything

As a developer, I have stopped seeing problems in my everyday workflow. I guess my mind makes workarounds without me noticing.

Example, a lot of the people around me complain about slow internet at my place, I've never been able to experience it that way.

Arrrgggghhh!!
How the fuck do you stay focused on one task?!

Writing code, is like browsing YouTube for me. I begin by searching for a Hibernate tutorial, and end, 3 hours later watching a video of a cat chasing a dog up a water slide.

How do you stay focused on the task of writing the specific class, method, package you set out to achieve when you sat down for that session??

So I gave i3 a try today via Manjaro i3 (don't have time to get a config of my own from scratch, would rather have a working setup which I can fiddle around with).

It's pretty...good actually. Doesn't work quite as well as I'd hoped because of my laptop's small screen, but still nice. Works well with my Blender and editing workflow too, so that's a plus.

After I'd spent an hour fixing audio and WiFi issues, of course, because Linux, but then that's just part of the fun amirite

So I had this thought all of a sudden. (Without any drug in my system)

Why are we still developing same old systems, softwares and web applications till now?

Websites, games and creativity involved development are understandable because people have different taste.

But workflow and process are supposed to be precise, standardized and consistent. No?

Is it because businesses are operating in various ways? Then again why?

Shit. I should stop my thinking at this level. 😑

Booted up IntelliJ to find the 2018.2 update just dropped. Took me a moment to get used to the design changes they've made, especially overhauling most of the icons.

Only thing I don't like in this change is taking away the color icons from my tool windows, there was a plugin to fix it though thankfully. I need some color in my workflow!

How's the update treating other jetbrains users?

In the past: "Alright, have the day off, so can do some serious work (work on my game project). Let me just check my mail first... And a cpl of sub-reddits... And see if there are any updates for Unit3D, or any interesting forum posts, or new assets on asset store that look nice... And check some online newspapers just to see if anything is going on... And check if anything new has been posted on slashdot since I last checked 5 minutes ago (nope)... And maybe see if there's any updates to Sublime Text or new useful packages that can help improve workflow... Ooh came across article on how to improve workflow... Hm someone mentioned a new task-management system in comments, gotta check that out... I'll just sign up for a demo-account and... Hm but what if there are any better ones? Better google for comparisons. Wait, isn't there a new episode of Silicon Valley today? Gotta see that first, no time tmr. Hmm also new episode of Archer, and American Gods. Better get watching these out of the way first, or I can't concentrate... Ah, wait, it's dinner time, no point starting anything until after that."

Now: All of the above, plus "I'll just check devRant real quick before I... hmm... interesting rant... *scrolls and reads rants and comments for 3 hours*"

How am I supposed to get any work done? :_(

Don't you just love it when a department buys a software for the company without consulting IT and Data Management departments? You know to discuss integration, flexibility, compatibility and all that?

Don't you love it even more when the users of this new software then complain about the different tools that have to learn and the workflow being completely scattered?

But hey, they work in administration, so I'm sure they know what they are doing. ⚡⚡⚡

That time when you spend 2 hours trying to debug what your colleague insists is a server issue... Turns out to be something missing from his workflow! FML

ASP.NET.

I don't like the workflow. Because of a project I had to use it.

Will NEVER use it again (unless a project force me. Money is money).

A programmers biggest nightmare. Going to sleep and losing the workflow and ideas.
I have to go to sleep. Noooo.....

Can anyone recommend a good cross platform way to develop GUI applications?

Looking at building an IDE for GMS-2 to add a new workflow but can't find any good GUI's...

(I want to use C# and yes i would ask on stack overflow but im more likely to get help here and not get called a dick head... Maybe)

An amazing git story: A month ago coworkers did research and started with merge requests. Their workflow is as follows: A Feature is developed in a branch, then a merge request is opened. After a very short review it will be closed (rejected) and merged without request. (wtf!) After that the develop branch will be tested later, in case of bugs, a new branch per feature is opened.

Moving tickets in the workflow to "Done" before going through the four testing stages.

Ladies and gents, it was a 🍺 day, today.

I spent more hours than I care to say today tracking down an issue in our web workflow, even looping in our only web dev to help me debug it from his side. There ended up being multiple bugs found, but the most annoying of them was that the json data being pulled back was truncated because a certain someone, in their migration script, set their varchar variable to a size of 1000 and then proceeded to store a json string that was 2800+ characters in length.

C'mon man!

I got nothing productive done today. Hate, hate, hate days like this!

Beer me.

I love git stash.

It's helps a lot for doing refactors to me. I guess it's not the most complex workflow, but it wasn't obvious to me when I started with git. Let me explain.

Refactors. As you start writing the first lines of a refactor, you start to notice something: you're changing too many things, your next commit is going to be huge.

That tends to be the very nature of refactors, they usually affect different parts of code.

So, there you are, with a shitload changes, and you figure "hey, I have a better idea, let me first do a smaller cohesive commit (let's call it subcommit) that changes a smaller specific thing, and then I'll continue with the upper parts of the refactor".

Good idea, but you have a shitload of changes nearly touching every file in your working copy, what do you do with these changes? You git stash them.

Let's say you stash and try to do that smaller "subcommit". What sometimes happens to me at this point is that I notice that I could do an even smaller change inside this current "subcommit". So I do the same thing, I git stash and I work on that even smaller thing.

At some point I end up `git stash pop`ing up all these levels. And it it shows that git stash is powerful for this.

* You never lose a single bit of work you did.
* Every commit is clean.
* After every commit you can run tests (automated or manual) to see shit is still working.
* If you don't like some changes that you had git stashed, you can just erase them with git reset --hard.
* If a change overlaps between a stash you're applying and the last "subcommit", then
if they differ, git shows conflicts on the files,
if they are identical, nothing happens.

with this workflow things just flow and you don't need to wipe out all your changes when doing simpler things,
and you don't need to go around creating new branches with temp commits (which results in bloated temp commits and the work of switching branches).

After you finish the refactor, you can decide to squash things with git rebase.

(Note: I don't use git stash pop, because it annoys the fuck out of me when I pop and you I get conflicts, I rather apply and drop)

I typically get constantly interrupted. It’s become part of my workflow. I wish I could work in silence a lot of the time.

Stop commenting out code blocks!

Either fix your shit or delete it.

I am open to argue what fixing may mean, as it is perfectly fine to make your broken code not reachable, e.g. via feature flags or skipping certain tests. Yet never ever should you comment those blocks!

So you say you want to keep it for historic reasons? You know, that is why we use version control! If you ever need certain functionality back, you can restore that state.

Each decent IDE also offers a local history where you can even restore code blocks that weren't even pushed or committed. So use that!

Commenting out test cases is a really bad habit, as you have no reminder that you shall restore it.

And no, a TODO and a FIXME won't count as a reminder as you have to actively look for them. And we all know how well that goes, don't we? (One time, I found a typo of a `TDO`. So even with a regular lookup for TODO, stuff will slip.)

Each test suite offers you ways to skip tests if there are valid reasons why they should not fail the build temporary and they offer colorful feedback. Yes, that means that your tests won't be green, but guess what: That's a feature! They shouldn't be.

That yellow is a fine reminder, aka warning!, that you should really fix your shit.

Commented code screams: "I DON'T KNOW WHAT I WAS DOING!" and it confuses the hell out of other developers ("Was this commented because of debugging purposes and should be active again or can I safely delete this!?") and adds verbose crap to the code base.

If you find yourself to be in a place that you comment code a lot, I also argue that your workflow is broken.

When you are using a decent debugger, there shouldn't that much of a need to comment in and out a lot of code in order to reason about your code-base.

TL;DR: When picking vendors to outsource work to, vet them really well.

Backstory:
Got a large redesign project that involves rebuilding a website's main navigation (accessibility reasons).
Project is too big just for our dev team to handle with our workload so we got to bring a 3rd party vendor to help us. We do this often so no big deal.
But, this time the twist was Senior Management already had retained hours with a dev shop so they want us to use them for project. Okay...

It begins:
Have our scope / discovery meeting about the changes and our expected DevOps workflow.

Devs work Local and push changes to our Github, that kicks off the build and we test on Dev, then it goes to Staging for more testing & PM review. Once ready we can push to prod, or whenever needed. All is agreed, everyone was happy.

Emailed the vendors' project manager to ask for their devs Github accounts so we can add them to the project. Got no reply for 3 days.

4th day, I get back "Who sets up the Github accounts?"

fuck me. they've never used Github before but in our scope meeting 4 days ago you said Github was fine...??

Whatever, fuck it. I'll make the accounts and add them.

Added 4 devs to the repo and setup new branch. 40min later get an email that they can't setup dev environment now, the dev doesn't know how to setup our CMS locally, "not working for some reason."

So, they ask for permission to develop on our STAGING server.. "because it's already setup"... they want to actively dev on our staging where we get PM/Senior Management approvals?

We have dev, staging, production instances and you want to dev in staging, not dev?... nay nay good sir.

This is whom senior management wants us to use, already paid for via retainer no less. They are a major dev shop and they're useless...

😢😭

Cant wait for today's progress checkup meeting. 😐😐

/rant

Get a ticket for a low priority bug, reported internally. Fix the issue mentioned in the bug.

Moves to QA environment, the original bug reporter tests and *passes* the ticket.

Moves to Staging environment, same exact individual then *fails* the testing. Cites totally new/unrelated changes that need to be made.

Apparently our the workflow is -

Code->QA->Staging->Requirements

Makes sense! :)

Tabs, or No Tabs? I did the same as this commentor 2 years ago. I can code so quick now because of this simple switch. Here's why:

(source, Laracasts.com)

Ben Smith
"I think the most beneficial tip was to do away with tabs. Although it took a while to get used to and on many occasions in the first few days I almost switched them back on, it has done wonders for my workflow.

I find it keeps my brain more engaged with the task at hand due to keeping the editor (and my mind) clutter free. Before when I had to refer to a class, I would have opened it in a new tab and then I might have left it open to make it easier to get to again. This would quickly result in a bar full of tabs and navigation around the editor would become slow and my brain would get bogged down keeping track of what was open and which tab it was in. With the removal of the tab bar I'm now able to keep only the key information in my mind and with the ability to quickly switch between recently opened files, I find I haven't lost any of the speed which I initially thought I might.

In fact this is something I have noticed in all areas of writing code, the more proficient I have become with an editor the better the code I have been writing. Any time spent actually writing your code is time in which your brain is disconnected from the problem you are trying to solve. The quicker you are able to implement your ideas in code, the smaller the disconnect becomes. For example, I have recently been learning how to do unit testing and to do so I have been rewriting an old project with tests included. The ability to so quickly refactor has meant that whereas before I might have taken 30 seconds shuffling code around, now I can spend maybe 5 seconds allowing my mind to focus much better on how best to refactor, not on the actual process of doing so."

jeff_way Mod
"Yeah - it takes a little while to get used to the idea of having no tabs. But, I wouldn't go back at this point. It's all about forcing yourself into a faster workflow. If you keep the tabs and the sidebar open, you won't use the keyboard."

most productive workflow I ever seen.

excel 1 : stock
excel 2 : order

compare stock with order manually 1000+ product.
excel 3 : check history of order generator (shop)

excel 4 : today's price of product + tax
excel 5 : alot specific unit's of product
excel 6 : maintained bill credit/debit
next step : forword to managers for approval
excel 7 : edit's from nanager
process repeat till managers approval

excel 8 : dispatched history
excel 9 : return product (reason's/unit)
excel 10 : stock update return + new product's

and few more excel's

data of 5+ year's
daily 500+ order's

lPO listed company

i have not mentioned account and other stuff

(╯°□°）╯︵ ┻━┻

After having my soul suck away by "corporate", I installed VS code on my Windows 10 gaming machine.

Now, I have a pretty hardcore dev setup on my MacOS (it's unix-based and it's good, so stop the hate). I'm talking about fully automatized Rakefile that will provision it from scratch: vim, macvim, tmux, iterm configs, 15+ brew tools, 15+ brew-cask tools, themes, plugins, etc.

Installing VS Code, Node and MongoDB on Windows, just for the fun and giggles, and not having any of my hardcore tools, made me feel like... it's something silly and fun again. I'm once again that softcore developer with no stress and no constant self-reminder to improve workflow effectiveness.

Made me a little happy.

Checkout this picture, this is my Windows 10's "tmux" lol

You know what really grinds my gears?

When the CTO inserts himself into your development workflow even though he hasn't programed, let alone touched the keyboard in about 40 years.

I don't know if some people are incompetent or just simply dumb.
If you're not sure what to do, ask.
If every guideline for each workflow has been uploaded, read and watch.

Don't wait until the very last minute.
Don't even act innocent when I ask and you don't even know wtf I'm talking about.
Don't "disappear" and come back when the deadline is in few days.

Just stop torturing me with your horrible work ethics.

Went to a 15 minute meeting to discuss an app I’m working on. Nothing I’m the agenda seemed aimed at me and I figured I was there just to pitch in as needed.

Took 2 hours and I ended up leaving with three weeks worth of work and the single most complicated workflow I have ever heard of. I do not get paid enough for this.

We are all about structures, clean code and many other things that make our life easier, right?

Well... It's not all white and black...

As talked many times, projects can be rushed... Client budgets can be low at the start and only then grow...

Let me take an example:

Client X needs a tool that helps his team perform jobs faster. They have a $500 budget. So... Testing, clean architecture and so on - are not really a viable option. Instead, you just make it work and perform that task as needed. So the code has minimal patterns, minimal code structure, a lot of repetitive parts and so on.

Now... Imagine that 3 months pass by without any notice and clients are ultra happy with the product. They want more things to be automated. They contact developers and ask for more things. This time they have a bigger budget but short timeframe.

So once again, you ignore all tests, structure and just make it work. No matter what. The client is happy again.

A year passes and the client realizes that their workflow changed. The app needs total refactoring. The previous developer has no time for adjustments at this point and hires a new company. They look at the code and rants spill out of their mouth along with suicidal thoughts.

So... What would you do? Would you rant about "messy project" or just fix it? Especially since people now have a bigger budget and timeframe to adapt to changes.

Would you be pissed on such a project?
Would you flame on previous devs?
Would you blame anyone for the mess?

Or would you simply get in and get the job done since the client has a "prototype" and needs a better version of it?

---

Personally, I've been in this situation A LOT. And I'm both, the old and new dev. I've built tons of crappy software to make things work for clients and after years - they come back for changes/new things. You just swallow the pill and do what is needed. Why? Well, because it's an internal system and not used by anyone outside their office. Even if it's used outside the office - prototyping is the key. They didn't know if the idea would work or be helpful in any way. Now they know and want it done correctly.

So I've been hired as a senior software developer with all the tags included (mentoring, innovating, pushing forward changes) for a company that is trying to move away from waterfall development (yup, it's 2019 and this exists) to a more iterative workflow.
I was initially hired and sent out to do some "field work" abroad for 3 months and then worked "remotely" from the local office with our field partners.
During all this time it seemed that my ideas go through smoothly, there was a lot of chatter about how things are moving forward, how new projects, innovations and new methodologies are implemented.
And yet, after my "remote" work has finished and I have to do things locally more, all of the skeletons fell out. It's just talk, nothing seems to be changing at all and yet any attempts to talk with the brass is like hitting a brick wall.
Not only that, I've been handed a 12 year old project with no possibility to refactor, no technical documentation, very few comments and in a terrible style.
The atmosphere in the company is odd as hell. People are either not very initiative, nor they seem to really care about all of the "changes" that "should be happening".
It almost feels that I've arrived in a company that still lives in 2007 more or less.
Should I quit, or perhaps it's a little "too soon" (have spent 7 months in the place already)? What I don't want is to get in the same train again (work for a company for 8 - 12 months, feel burned out because of the divergence between actual things done and "plans" and then change the job).

My whole workflow for HTML is frustrating. I rather write pug, because it has mixins, includes and isn't that fucking repetitive. But to write pug within Laravel blade views, I have to preprocess it too blade. Then sometimes the syntax gets crazy because of escaping blade loops like an insane guy ('| @foreach($foo as $bar)'), but you get used to it after time.

How do your companies do things? Does your development team have much autonomy from the non-technical side of the business?

I work in an agency and we have yet to actually get a proper workflow in place for things, its getting quite irritating.

So, we have a ticketing system in place and its not used anywhere near properly. In theory you could design a whole project in Jira and use that to handle all of your status updates, the PM's would just, you-know... read it.

In the morning we have "stand-ups" where for some reason we will have project/task briefings/long speeches lumped in before developers get onto talking about what they're working on and naturally if they have any blockers. Then at the end of this "stand-up" everybody has to write down what they just said onto post-it notes so the PM team have an idea of what everybody is working on that day.

So essentially, every developers day is micro-managed from the business side with exactly what they're working on.

Throughout the week there may be bug tickets that come in, these tickets are thrown into developers outlook calendars so they know which day to do them on.

For some reason nobody has considered that you could setup due-dates on tickets and setup Jira dashboards to make all of this stuff very straightforward to manage.

I think the problem is that since nobody actually works from Jira, they just get things thrown at them verbally or via calendar nobody would get into the habit of checking their dashboards on a morning.

Another annoying thing is getting tickets sent to you with estimates already made (not made by a developer either) or with project schedules laid out before any estimation has been done at all.

We also have a pretty insane ticket backlog due to PM's not actually looking at their own projects and attempting to prune or even review the backlog. There have actually been cases where client work totally drops off the radar from the PM side and just never gets finished.

Am I working in an utterly dysfunctional shop or is this kind of crap just par for the course?

When you catch developers rolling out untested changes to production that have a huge impact on your clients workflow... And they don't tell anyone so you find out because your clients are yelling on the phone about some change affecting their work flow.

Ubuntu, Openbox, vim, duckduckgo, Gmail, mailgun, digitalocean, xterm, libvirtd, remmina, polipo, insomnia, ulauncher, copyq, nextcloud, rofi, ssh, bash, Firefox, Firefox-Dev, Vivaldi, steam, itch, git, proton, wine, vlc, cherry mx brown and black, android, mint mobile, Asus, amd, ubiquiti, and plex.

What's in your workflow?

Goals before week 200:
- Release some tracks
- Play a few gigs
- Build python program which I've got in my head for some time now
- Master git workflow

Edit: typo

I know, many devs swear on using *NIX based OSes or macOS but really... Windows 10 is very good, never had a single issue or BSOD. If u have issues regarding update reboots then just disable automatic reboots,damn! One single " fuck Windows, killed my workflow cause of updates. Installing Linux know cause I'm too dumb to change a simple setting." >_> and I can play ALL my games... NATIVE!

I pushed all my work to Friday
And I (git) pushed all my work on Friday

😂

I love CSS, but don't like preprocessors (like SASS, Less, or Stylus) :/ There's nothing more beautiful than vanilla CSS with zero workflow :)

So I'm trying out docker and see how I can make use of it, current setup:
1. Ubuntu on VM and Mac for Asp.Net core development
2. Windiws for MS only stuff like SQL Server
3. Ubuntu Server on VM and is running docker images: MS image for SQL and Ms image for dinner core.

What I did so far one script which will handle updating SQL Server database on windows with the changes done on docker SQL image
Then publish website from Mac or Ubuntu to docker image. I have yet to find a way to execute scripts remotely on a docker image using bash script from a remote

What should I do next? And for home setup go for Ubuntu server or CentOS? Any recommended packages for server administration? Workflow ..etc.?

So, I worked away from our software teams and directly with engineers for a few months to examine the capabilities of a new piece of hardware we expected to integrate with. It wasn't necessary that I be shut out from all the other software projects, but my boss decided that I shouldn't go to them. When pressed, he said he didn't want the meeting to be too full.

I studied this hardware thoroughly, and even know the engineers who designed it personally. This is, in every sense of the word, my project.

... So when the product owner asks to meet to discuss another feature around it, my boss decides he should invite the rest of my software team to meet with the engineers. There's some non negligible engineering background behind the tool and associated workflow.

When asked why he invited them, despite me being concerned about lack of focus in the meeting, he said he "didn't want anyone to feel left out".

This is the same man that cost me an entire week of work (and is now costing me my time with the systems experts) because he doesn't want to hurt the feelings of my junior colleagues. He's shown repeatedly that he's just fine excluding me, but heaven forbid my junior colleague feel junior.

I don't think he'll ever realize how much he's playing favorites here. Ugh.

Just started using Slack in the office. Combined with the BitBucket plugin it’s awesome!

FUCK YOU!!! HOW CANT YOU SEE THAT EVERY TIME I SUGGEST TO SEPARATE OUR FUCKING WORKFLOW WITH FRONT END/BACK END AND TRY TO INTRODUCE AT LEAST SOME MANAGEMENT TO THIS SHIT HOLE ITS MY WAY OF SAYING: look dude, I like it here but fuck you shit face if I have to deal with this fucking CSS bullshit one more time there are going to be delays everywhere ...

Fuck you CSS.

I got so inspired when a chrome extension i made ,was used every day and is an important part of my every day student and development workflow.

It's on github right now.

What are the legal ramifications of reverse engineering a competing software and its respective workflow?🤔

Another theoretical situation will be if you all wrote the code and derived the algorithm in house.

>ooo new thing to play with and learn, yay!
>*Installs using directions*
>Hello world program fails
>Oh I need these dependencies
>Wait the deps all need their own deps...
>But one of them is deprecated.. what do?

I love the feeling of working on something new but
I hate ending up spending more time getting a workflow setup and chasing down random bugs or hacky fixes just to get something stable so I can start working!!!

What are some of your Linux desktop preferences and workflow improvements?

I use Mutate for app launching, DDG searches, and a dozen or so scripts I wrote myself.

I like different URLs to open in specific browsers, so I wrote a script called xhttp that determines which browser to open with URL regexes, and used freedesktop to register it as a browser, and set it as my default.

Anything fun you've done?

That feeling when you think your workflow is bad and happens to see"Professional" Degree level team of coders writing crap code with even crappier workflow

!rant

I love the cloud. Not the google drive kinda, but the one that integrates with your workflow like git. Tinkercad, for example, its great that i can just log in from my work pc and continue modeling where i left off.

I'm still new to using version control and now learning Git with GitHub, working on my own project.

My current workflow is:
1.Clone GitHub repo
2.Make a local branch to add new features/fix bugs
3.Work on the feature/fix
4.Merge the local branch with local master
5.Push origin master

There seems to be no point in making remote branches because I am merging my branches locally. Am I doing it wrong?

If you've give me an unclear and rediculously large workflow to implement with a confusing built in house library, dont demand me to TDD it. TDD works well when you know what it is your going to be doing. I'll slip and slide through this implementation and then come back for testing.

the current ERP software i test has a function that, when you dont have the USB dongle plugged in, it will annoy the workflow with a popup where you have to solve simple math stuff. (Like 2041+949). I am kinda inclined to write a small programm that insta solves those pop ups.

I must note, this is a weird way of licence management.

A loooong time ago...

I've started my first serious job as a developer. I was young yet enthusiastic as well as a kind of a greenhorn. First time working in a business, working with a team full of experienced full-lowered ultra-seniors which were waiting to teach me the everything about software engineering.

Kind of.

Beside one senior which was the team lead as well there were two other devs. One of them was very experienced and a pretty nice guy, I could ask him anytime and he would sit down with me a give me advice. I've learned a lot of him.

Fast forward three months (yes, three months).

I was not that full kind of greenhorn anymore and people started to give me serious tasks. I had some experience in doing deployments and stuff from my other job as a sysadmin before so I was soon known as the "deployment guy", setting up deployments for our projects the right way and monitoring as well as executing them. But as it should be in every good team we had to share our knowledge so one can be on vacation or something and another colleague was able to do the task as well.

So now we come to the other teammate. The one I was not talking about till now. And that for a reason.

He was very nice too and had a couple of years as a dev on his CV, but...yeah...like...

When I switched some production systems to Linux he had to learn something about Linux. Everytime he encountered an error message he turned around and asked me how to fix it. Even. For. The. Simplest. Error. He. Could. Google. Up.

I mean okay, when one's new to a system it's not that easy, but when you have an error message which prints out THE SOLUTION FOR THE ERROR and he asks me how to fix it...excuse me?

This happened over 30 times.
A. Week.

Later on I had to introduce him to the deployment workflow for a project, so he could eventually deploy the staging environment and the production environment by hisself.

I introduced him. Not for 10 minutes. I explained him the whole workflow and the very main techniques and tools used for like two hours. Every then and when I stopped and asked him if he had any questions. He had'nt! Wonderful!

Haha. Oh no.

So he had to do his first production deployment. I sat by his side to monitor everything. He did well. One or two questions but he did well.

The same when he did his second prod deploy. Everythings fine.

And then. It. Frikkin. Begins.

I was working on the project, did some changes to the code. Okay, deploy it to dev, time for testing.

Hm.

Error checking out git. Okay, awkward. Got to investigate...

On the dev server were some files changed. Strange. The repo was all up to date. But these changes seemed newer because they were fixing at least one bug I was working on.

This doubles the strangeness.

I want over to my colleague's desk.

I asked him about any recent changes to the codebase.

"Yeah, there was a bug you were working on right? But the ticket was open like two days so I thought I'll fix it"

What the Heck dude, this bug was not critical at all and I had other tasks which were more important. Okay, but what about the changed files?

"Oh yeah, I could not remember the exact deployment steps (hint from the author: I wrote them down into our internal Wiki, he wrote them done by hisself when introducing him and after all it's two frikkin commands), so I uploaded them via FTP"

"Uhm... that's not how we do it buddy. We have to follow the procedure to avoid..."

"The boss said it was fine so I uploaded the changes directly to the production servers. It's so much easier via FTP and not this deployment crap, sorry to say that"

You. Did. What?

I could not resist and asked the boss about this. But this had not Effect at all, was the long-time best-buddy-schmuddy-friend of the boss colleague's father.

So in the end I sat there reverting, committing and deploying.

Yep

It's soooo much harder this deployment crap.

Years later, a long time after I quit the job and moved to another company, I get to know that the colleague now is responsible for technical project management.

Hm.

Project Management.

Karma's a bitch, right?

Depends on the project.

If it is a full application I usually start with what information it will handle.
Then either sketch out some database or some pages depending on how much info I got and if I got any good examples.

The less info I have, the more I try to focus on use cases and workflow to try to figure out what data will be needed.

But for more niche projects, like supportive library, ex parsers, I either mock some test in linqpad or look for similar examples online to flesh out the idea.

But I tend to very quickly fill out the basic shape and try to get something that can be tested.

Then I can find if I need to rethink it.

What I absolutely hate the most of my workflow is to hand over my code for review to other developers.
I know it is important to prevent errors and to get feedback from them to improve, but I'm far from being self-confident and I'm afraid of showing others my work, regardless of the fact that nobody said anything mean about my work.

So glad i moved from a desktop PC to a laptop for development. I still have 2 workstations (one at home and one at work) with 3 screens, mechanical keyboard + mouse. But if i ever have to demo to a client/PM i just un-dock and take my laptop to them. Plus if the office is loud i just go to another room.

this really happened:
Interface Team Lead: "hey I want any time deployments and better QA"

Me: "ok sure. I have CI/CD, but yiu need to work in feature branches / tags, and make sure your code passes automated builds and unit tests"

Team Lead: "I dont have time to test it makes me unproductive! and creating a branch is an extra step which is going to set me back. Im telling the boss you are impacting performance!"

Me: "you want better deployments and QA, but you can even create a branch or tes your work?"

Team Lead: "We have deadlines!"

I work really well under pressure.
Sometimes I'll be really lazy on a project until the deadlines get tight and I need to go into overdrive.

Textexpander. Ggpu = git push upstream, gg. = git add ., and ggc = git commit -m "" ... I love that I don't have to type out my whole damn name, username, email and work email all the time. Just expanding my email address is enough of a win for me with that tool. Also Alfred + utf symbol workflow. And newest addition - vimium to easily pin tabs.

I am pretty much sure we will lose more commits and codes, my colleagues does not follow a better git workflow and then they blame on me.

Solving the problem before it's even coded.
A seemingly perfect workflow makes the best project

The worst part in my workflow is when my coffee ☕ ends.

I've been working on this personal project, it has a, for lack of a better word, "interesting" work flow. I'm trying to make a program similar to Netflix, here's the way it works.
I have an html page with a video, and a black background, I use the webview plugin for fusion, which acts as a mini web browser, it's programmed to load the test.html file, which the test.html file than loads the video, then I build a gui connected to it in different frames. It's odd, yes, but it does the job done.

I invited a colleague to the repository and taught her some basic git so she could edit some texts without having to interrupt my workflow.

All of a sudden, some parts stopped working. Guess i should have been a bit more articulate when telling her about commit messages..

Craziest deadline: job processing system for a manufacturing company, Android app, live updating web interface, integration with 3 existing systems, custom/new database and workflow... 9 days from concept to prototype. I was the only dev on it.

Yes, the product sucked, and no, I didn't really sleep.

Jira workflow requires dept manager to approve and assign new issues to developers. He does this once a week. 😑

i just released my first open source project with effort to make a comprehensible documentation for others to use as well as repetitive refactoring to not embarrass myself.
i am equally excited and knowing no one will care about that.

it is based on my effort to make my companies workflow more effective, knowing well this is just a temporary solution in advance to a professional developed system as opposed to having no system at all. so all of this work will fade into oblivion eventually.

i felt this has been too much work just to be forgotten someday so i cling to my naive hope someone might benefit from that and maybe i get one or three internet points.

in case someone is interested in a free quality management software for document control and access with no real state of art, you might find it interesting to visit my qualitymanagement repo