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.

True!

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

Scrum they said.

Credit from imgur

-Let's start making the game!
-Yaay
-We should focus on performance optimization!
-But we don't have anything to optimize yet..
-Performance optimization!!!

1 month later

-OK you were right, we can't focus on performance now. We need to start making this game!
-Finally!
-So we're in pre-production now, let's do some R&D!
-Awesome, I wanted to start designing our workflow for adding new content, and maybe also loca..
-NO! That's unimportant! We must do R&D!
-OK what should we Arr-and-Dee?
-Performance optimization!!!

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.

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 -_-

You know what? Fuck it. Git CLI. Hot take.

Question is "least favorite". Not "worst". Not "least important".

Git is great, essential, fantastic, whatever. But I hate interacting with the CLI. I can never remember the stupid fucking commands, I always mess shit up if I need to do something outside of my normal workflow, and honestly, usually the correct way of doing shit looks fucked.

So fuck git CLI and its learning curve

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

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 :)

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

Awesome!

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...

What workflow?

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

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.

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.

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.

I finally stopped being lazy and wrote 31 unit tests for my Discord bot.

Nothing is more satisfying than seeing them all pass and the GitHub workflow working without any problems. :)

devrant now is really integrated in my workflow

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

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...

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..

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

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.

Not sure if thats just me, but I absolutely can not stand watching people work on a computer slowly. Like: Watching people copy a text into a different window be like:

Select text with the mouse...
Move mouse down for 20 seconds until everything is selected ..
Right click
Copy
Click on Taskbar to open different program.
Right click in program
Click paste....

I .... just ... can't man.
Its: Ctrl+a, ctrl+c, alt+tab, ctrl+v

(And that is just one example, there are worse ones)

Maybe that just me, but I am so used to using my computer fast, and I optimized the shit out of my workflow.

Me: why are we paying for OCR when the API offers both json and pdf format for the data?
Manager: because we need to have the data in a PDF format for reporting to this 3rd party
Me: sure, but can we not just request both json and PDF from the vendor (it’s the same data). send the json for the automated workflow (save time, money and get better accuracy) and send the PDF to the 3rd party?
Manager: we made a commercial decision to use PDF, so we will use PDF as the format.
Me: but ...

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 make a presentation to explain to the boss why we had to tweak around the requirements in order to keep backwards compatibility and stuff. I take 15 minutes explaining how our system currently works and how these requirements would change it, etc etc.

"So... is this workflow okay for our customers?"

They stared into the presentation slide for a good minute.

"I think we should align this row over here with that square over there."

"Oh don't worry this is a demo. But do you think our customers will still be okay with these changes?"

"Yeah, but these two elements are unalligned and they look pretty bad."

I'm starting to think that fancy speech can deter people from questioning or complaining to you. I'm pretty sure they don't know their own product as well as I know it.

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

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

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

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.

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!

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!!!!!!!

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.

I dont know what to feel anymore.

Got hired directly without an interview into 'Data-analytics' department in fortune 500 company. This is my first job. Got hired because this company want start a website that cost millions.

Even though I am junior, I can see that this company has no idea about software development at all. No git server, no code review, no quality assurance and no proper workflow. No senior developer to guide us (junior dev) too.

There is one 'senior' consultant that work on automation project here but he just focus on his work and don't help us directly too.

The contract is about 1 year. Still got 11 months to go :/

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.

Lead messed up the Git workflow (New repo), ask me to fix it. And when I said that we better do it from first properly, asked me if I even know git 🙄 Feel insulted.

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

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"

So I'm tasked with rewriting the old software my employer uses to track basically anything in his company. They want to stick quite close to the old workflow as much as possible, I get that.

"Why exactly do you need access to the system? No you don't need to look at it just recreate the flow. I'll give you the sql structure is that OK? Oh and this won't take long, you can copy from the old code can't you? Wait why do you need access to the code? No. "

🙄

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.

!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.

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.

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 😁

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

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

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"

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.

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.

!rant

Linux edition!

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?

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

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?

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😈

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...

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

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.

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

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.

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)

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?

My work gave me three laptops because not one of them can access all the resources I need. So I have to balance my workflow around these three machines.

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)

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??

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

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).

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? :_(

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

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

We don't have a designer yet in the team so we had to learn Adobe XD on the side to prototype our ideas. After months of getting the hang of it thinking this semi-free tool will work for us to save some money, Adobe decides to change their pricing plans starting in April 2020 and it will no longer be free. It feels like Adobe trapped us to get used to their platform and then secretly slap us with a price tag halfway. We can't blame them since we're all trying to put food on the table here. We started exploring Figma today and oh boy was it a gift from the gods! The features are so much better. They make our workflow faster!

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.

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.

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! :)

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.

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

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)

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.

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

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. ⚡⚡⚡

Our publish workflow had to much manuell steps in it. Wrote a tool to publish a new version with one button click.
My Colleges thank me with tears in there eyes 😄

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.

>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!!!

typescript is awesome. it brings type safety into javascript which speeds up my workflow because I always find myself running into typing issues at runtime

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?

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.

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?

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.

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.

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

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 have been working with git for years now, and I could never work on a project (regardless if big or small) without it. Its great.
However, just a couple of days ago I learned about the git flow branching model.
Even tho I also worked with branching on a daily basis for years, I did not know about this model. And I have to admit: Its awesome.
If you don't know it, I highly recommend you to look it up. It really improves the already organized workflow with git even more. :)

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

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

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

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

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

(╯°□°）╯︵ ┻━┻

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.?

Fucking hell it pisses me off when you go to so much trouble to streamline processes, set up systems that improve workflow and solve issues, find better solutions and show how they make life easier... and people are like "yeah nah let's just do things the same old shitty way we've always done things".

(╯°□°)╯︵ ┻━┻

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?

Today I played with GitHub Actions. Since I couldn't test anything without making a commit and pushing it to GitHub to trigger the workflow, my commit history now chronicles my slow descent into madness. Thank God it's a private repo. I'm gonna squash it if I ever make it public.

This gem is from hour two of my four-hour struggle:

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.

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.

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!"

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 pushed all my work to Friday
And I (git) pushed all my work on Friday

😂

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.

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."

*launches devrant: * almost everyone talking about types of IDEs to use, while I sit here with just a text editor in my own farts contemplating how much different will my workflow be.

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. 😑

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?

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.

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.

GitHub or Bitbucket for CD/CI?

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.

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.

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.

All my resolutions:
- Finish my fully FOSS gamedev workflow and start working on my game by March, have a concept demo by May when my matura exams come round.
- Do good on said exams and get into a good university.
- Do some political or social activism
- Learn the guitar to a campfire level
- Drink til I pass out if trump wins again.
- Make close friends with at least 10 new people
- Go on at least 6 dates

You know something's truly off when you're being challenged for all the wrong reasons. When all it seems you ever do is apply a band-aid every time instead of making the time to fix it properly and for good. Or when the people who should be making your work easier to do instead suggest new tools and features to integrate into your workflow or project because they plug the holes in their management process and can ignore the leaks for the time being.

I need to push myself out of this place and ramp up my skills and update my personal projects so I can prove myself capable and move on to a better employer. Because I'm starting to hate the stopgap short-term approach that keeps getting shoehorned into our work, and only proceeds to make us look bad even if it's the whims of our bosses causing it in the first place.

Thanks for reading.

Weekly summary: 1 of your workflows have failed

- shit

The below workflow had an unusual number of failures:
Workflow X
Failed 1 times

- oh so it is failing since yesterday?

*swaty click*

8 h ago - Succeeded
1 d ago - Succeeded
[...]
6 d ago - Succeeded
1 wk ago - Failed

- Oh. Great. Perfect time and way to notify me.

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.

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.

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

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

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.

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

Hey this is my first post on This new fitness-tracker-app community

I will tell y'all my workout :)

-programming a parser

FUCKING HELL PLEASE STOP ALREADY THIS IS THE WORST SHIT IVE EVER DONE EVERY WHERE IF STATEMENTS JUST TO CONSUME FOUR FUCKING TOKENS I DONT WANT TO DIE BUT I'D LIKE THIS PROJECT TO BE FINISHED ALREADY BECAUSE THIS IS ANNOYING AS FUCK I REALLY WANT TO KICK MY COMPUTER WHILE TELLING IT TO BE THE MOST STUPID BRAIN ON THE WORD AND THEN REMEMBERING THAT ITS NOT A BRAIN FUCK MY FUCKING FUCK HELL THEN I WOULD KILL THE PEOPLE WHO THOUGHT THAT MAKEING std::vector::end() RETURN AN ITERATOR WITHOUT ELEMENT WAS FINE AND THEN I'D KILL ALL THOSE WHO COME INTO MY ROOM THUS DISTURBING MY WORKFLOW

Enough rage.

Removing SASS from workflow.

!rant
TL;DR: New(-ish) dev looking for advice to improve workflow and new languages. Hopefully worth a read though :)

Newbie developer here, I took a web applications development class this year since I could take that at another campus rather than do general education courses at my home school, and I have learned and earned a CIW Certification for HTML5, CSS3, and JavaScript, though I know the certificates do squat if I can't apply myself to them, and I have learned PHP and MySQL.

I want to learn more, technically-applicable languages.

My setup is barebones (to a Linux diehard's eyes), with a gaming laptop that I do a lot of workstation stuff on, an RPi 3 B that I do some Linux-y stuff on, and a less-powerful Development Laptop (that I call a devtop) that I occasionally do work away from home on.

I'm sure most will cringe and weep at my workflow, as I use Windows 10 on both systems and the standard NOOBS software on the pi, and I use Brackets as my text editor, as well as the XAMPP AMP stack for testing.

My biggest questions are what could I do to improve my workflow, and what languages should I learn/apply myself to for real-world application (such as Node.js for live-updating server-side applications or C# for Windows applications)?

Thank you for taking the time to read this, any feedback is helpful! I'm just a high school student with a lot of enthusiasm for development!

Most the devs are yelling Linux is best and blah. But since I installed eOS on my new ideapad my productivity is zero.

I'm just solving problems with the OS or other software. It seems some of the drivers are missing, because sometimes this fucking piece of shit just don't boots or just hangs. Installing node and npm was definitely one of the worst experiences because I messed up sudo privileges... I had to change my workflow because node-sass wasn't able to compile because of this.

And still I kind of feel more comfortable with eOS. 😥

Was wondering what kind of workflow you use.
My team is currently a big unorganized chaos...
Our manager wants us to take the form of:
Feature idea -> Design -> Build -> Test -> Train (explain to users how to use it) -> Deploy

The `Train` step is something rather odd to me, as that would mean teaching every single employee how to use the product we're making.

Wouldn't it just be better to skip the `train` section (and maybe use some kind of wiki?) and try to make everything as clearly labeled and obvious as possible?

1) Read the ticket.
2) Create a branch with ticket number in name.
3) Move ticket to Working now section.
4) Make some changes according to the ticket.
5) Commit changes to branch. Than pull it.
6) Create pull request and submit it.
7) Move ticket into In review section.
8) Move to another ticket.

Tickets:
#7 - Change background size in product item.
#8 - Add icon to info flash message.
#9 - Add adaptiveHeight parameter to the slick slider.

Done, now another 30 tickets...
Yep, this is my workflow i'm forced to now.

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..

Just read a rant about webpack and suddenly the hate boiled up again ...
Why is it just so damn annoying to configure?

Just make it like gulp or so where you have an actual idea on the workflow, rather than just throwing in plugins at random and let magic happen without knowing wtf is going on.

Tried to update an ejected Angular4 project to angular 5 ... after 2h i gave up and dropped some stuff to use angular-cli again.

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.

rant/!rant

So I just started working at the beginning of January and I have no fucking clue about anything especially Web development.
But now I have a week to figure out how in the world I am going set up a workflow for some secretaries so that the higher ups get a printed coupon with a password on it, so they can log into our WLAN via a captive portal that I also need to set up.
I am thinking about a website that takes a list of names and settings (probably excel or smt) passes them to the WiFi management softwares API and then generates some PDF file for download that just needs to get printed.
Did I mention that I have no Dev tools (I have notepad, yeah the one without ++), no test environment, no prior experience and no clue how to do it?
But somehow I love this challenge and am glad that my colleagues don't send me to get coffee but let me work.
Am I insane?

I'm currently the only dev that works with a client's dev team. That's not really how we usually work, usually it's a whole team of ours.

Three aspects why this sucks:

1) the client's dev team is made up of juniors and junior to intermediate devs. All of them are new to scrum. I therefore have to constantly support (dev & agile workflow), check all the PRs and have to think of everything in Refinement meetings.

2) the client's based in another timezone and the PO is super busy because we're the only agile team in their company. Therefore this is going to be the third Friday in a row where I have meetings until 6pm.

3) I also have a specific time frame I have to start working for my company, so I constantly work extra hours due to the time difference.

I'm just tired.

I just built a website with Hugo. And I love it. Got a request for a certain set of pages but because of the workflow the one thing I could dynamically load wasn't worth a whole wordpress site.

So I built it with Hugo instead. I played with it a little last week so I could get around but I got good this week and damn it's powerful.

I think I'm in love. I wish more projects at work could be built in Hugo.

Context: ive been porting a single threaded D.A.G scheduler into a lockless multithreaded one. Point is its an objectively complicated project where theres lots of overlap in the code and architectural boundaries are very fuzzy.

My boss: "Can you just make new branches for every 'large' change youve done. Its too hard to merge this one giant branch youve got"

Me: "Fuck bro, but this is 2 months worth of significant refactoring where the commits are not atomic and you told me way back then that it was cool to work in my own repo. Now ive got to go redo half my work"

Boss: "Well yea but isnt it so much better to work with clearly seperated histories"

Me: "yea its great if you tell me thats the workflow you want upfront. This is gonna suck but ill but my balls and dive into this pit of lava if u say."

!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.

Working for a large client converting paper forms to the web. Stated goals, simplify data entry for clients, improve data quality, reduce resourcing in backend human processing.

We met to review prototype and discuss workflow questions. Crazy deadlines, with the usual changing scope creep.

We start to point out the need for data validation, to shorten # of questions based on answers.

Business says no. All forms should be submittable regardless of what user enters, don’t put validations in because all that warning messaging confuses them and takes up more time.

Web form should behave like the paper copy....

Welcome to 1975!!! This is why 2018 won’t be like 2018...

I'm only a humble customer service representative in Amazon, I really hate the email editor we use to mail the clients after they call or chat with us. This, of course, means I need to include Emacs on my workflow so I can suffer less, let's Elisp the heck out of this problem!

I am so fucking sick of daily stand ups. What a fucking waste of my time, even if it’s only 15 minutes, it fucks up my workflow and is just generally fucking annoying

Does anyone work on a bunch of local NPM modules wanna describe their workflow for local dev vs deploy?

I’ve got mine but it feels a little trashy. It’s basically one npm script to link all the local modules for dev and another which will npm install them in prod - is there a better way without adding more build tools?

Question for WSL users.

What's your workflow?
How do you edit the code from your IDE on Windows while the application is running in Linux?

Is there a team that works truly productive and happy via an agile (scrum) workflow?

Or does it always distill down to an excuse for a chaotic workflow?

My experience and cynic nature has let me to assume the latter.

(That being said, I never had a dedicated scrum master to work with. So that may be the first of many problems.)

I used to hate the idea of using the terminal. This year, however, I decided to go full monty and there's no looking back. I've written scripts to reinstall oh-my-zsh, GUI apps and everything I need to work including workflow tasks. Reinstalling used to take me a week, I've effectively reduced it to 1 day.

IDE battle--- what is everyone using?

My main languages are- C# - laravel - node/angular - HTML/ CSS. And use git / aws.

I have used the following- and like / hate them all. :) but I want to see what others are using and opinions on them.

Visual studio- bla...
Sublime 2 & 3
Atom
Coda(s) 2 - 2.5
Phpstorm
IntelliJ
TeamCity
Mono develop
Eclipse

We often give access to a product owner from the customer on our Jira to keep up a good communication and everyone stays up to date as everything is on the board and not hidden in emails or paper notes on the desk of the guy that is on vacation.

So far, so good

Our customers really like this as they can comment on tickets and they are integrated in the workflow because they can push into the backlog and can review finished tasks.

It is just getting better for everyone so where is the rant?

One project is just a dump of shitty mixed content tickets. But how? They look really neat. There are tickets like "fixes from meeting 20th of may" which are initially well structured with approximately 4 subtle changes to the UI and some explanation and screenshots.

PM says: Good ticket. There you go ticket, into the customer review loop of doom.

20 comments and 13 status changes later. Point 43 from comment 17 is referenced in comment 20 to keep on hold as a third party needs to give feedback, point 7 is still not solved correctly as dev 2 was not aware that it was already discussed and changed in the ticket "Call from 25th of may" where in addition the resolution of points 5-12 were requested with an additional excel file to import.

By now we have the 8th of august and literally 17 of these kind of tickets.

I guess we need to improve the workflow and request a new product owner. But this far I just table flip everytime I get one of these tickets assigned.

My favourite tool currently is Gulp, although that sentiment is slowly eroding as I integrate it into a project that is 10+ years old and follows few standards with regard to css and javascript files. At least it is a quiet period in my workplace at the moment and it will improve development workflow when I'm done

Working in a service based company in a project with dumb fcking manager/lead who can't plan proper workflow and design, where backend and frontend work on the same feature simultaneously and u get API's in the end of the Sprint and it has be integrated, tested and deployed in the same day...and the manager is a fcking virgin and starts drooling with backend team as they are most females and is very lenient towards them

So I've been using Visual Studio and I'm really starting to get pissed off at the key combinations.

Like Ctrl+K+Ctrl+D

Just to auto format code. So I'm now thinking of speeding up my workflow by using AutoHotKey which by the way is the best thing ever invented.

If anyone uses VS and is interested in me sharing the ahk script then let me know. I just feel like pressing 4 keys for simple tasks is just a waste of time and easy to forget.

I scratched my head when GitHub gave a name ("Flow") to a normal workflow of git. Anyone else?

My first day at my first tech job ever: I am super excited.

I was assigned a coworker that would help me get familiar with the company and workflow n stuff.

We agreed on Wednesday and Friday 08:00 - 12:00 as working hours.

Now it's 08:30. He's not there and I am waiting since 07:50.

Sorry, but fuck him.
This is so demotivating...

Bug report workflow for our customer support department.
1. Use eyes
2. Use brain

Just printed as poster

Did anyone here use sapper and svelte to build a production application? How was the experience overall?

I've been reading about it and watched Rich Harris present svelte and sapper, I like his approach but I'm not too sure about how it work in a production workflow

Is it just me or is the majority of all additional slack apps really just crap? Many cannot even be installed because the website is no longer available (WorkingOn as an example).

Not a single app really helps us in our workflow. I lost the interest to try more of them :(

!rant (I got down voted for this on Stack Overflow, so I try to discuss the issue with a more professional crowd.)

In a Software Engineering class, we had an assignment to read Parnas' seminal paper on modularization [0]. In this paper, two approaches of dividing a software into modules are discussed:

Traditional Approach: A flow chart is drawn to work out the single processing steps and the program's high-level flow. Then every processing step is turned into a module. This approach doesn't yield very good results.
New Approach: Every design decision will be turned into a module by the means of information hiding. This approach leads to much better results.

My personal interpretation of the term design decision is that the modules are identified as data structures rather than as processing steps of an algorithm. This makes sense, because data structures are much more suitable for information hiding then processing steps of an algorithm. (The information inside a data structure is hidden behind functions, whereas a function only hides more detailed processing steps and no information; the information is actually passed in as arguments.)

Why does the second approach work so much better than the first approach? Here comes my second interpretation: The single processing steps of an algorithm are not replaceable (and thus not reusable), whereas it's possible to convert data structures into other data structures.

And here's my question: Could that be the reason why software development using workflow engines (based on BPMN, for example) never really took off?

My personal experience is that the activities created in such workflows are hardly ever reused, but there often are big data structures passed around all the involved activities, even if most of the activities use only one or two of them.

My question exaggerated: Could we get rid of all those clumsy workflow engines by giving managers Parnas' paper to read?

[0]: On the criteria to be used in decomposing systems into modules (Parnas 1972)