The project where I realized I wanted to go from chemist to pro dev.

I built a flow-chemistry spectrometer with monitoring backend in Haskell.

Spectroscopy is where you add a reagent to a glass tube, it changes color, and by measuring the exact color it tells you how much of something (for example, a toxin) is present in the sample.

I had to do that a lot on factory samples, writing down measurements using pen & paper.

I'm lazy so I decided to do the logical thing: Automate it. I bought a second hand spectrometer, stripped the casing, did a shitload of glassblowing and hooked up tubes to the production pipelines, so I could get samples, mixing them in the correct ratio with reagents in continuous flows using valves.

I ended up using 2 home-crafted arduino-like boards (etching PCBs is fun!).

One to calibrate the mixture against known samples and control solenoid valves to continuously cycle through various reagents and deionized flushing water, the other to record the measurements and send them to a server running a Haskell/Yesod API.

The server collected the information into InfluxDB (A time series database), displaying all data on a graphite dashboard.

Eventually I wrote Haskell plugins for most of the chemistry processes, from pH & temperature measurements to polymer property and pigment tests (they made a lot of printer ink).

Then I was fired because they didn't need chemists anymore, and the code "could be maintained by the intern" (poor guy)...

But I did find out that I loved functional programming, chemistry automation projects, and crafting my own electronics during that time.

When you're trying to optimize a process and a team members gets upset because "that's not the way we've done it before!"

No fuck. That's why we are fucking improving it.

Long rant ahead. Should take about 2-3 minutes to read. So feel free to refill your cup of coffee and take a seat :)

It turns out that the battery in my new Nexus 6P is almost dead. Well not that I didn't expect that, the seller even explicitly put that in the product page. But it got me thinking.. why? Lithium batteries are often good for some 10k charges, meaning that they could last almost 30 years when charged every day! They'd outlive an entire generation of people!

Then I took a look at the USB-C wall charger that Huawei delivered with this thing. A 5V 3A brick. When I saw that, I immediately realized.. aah, that's why this battery crapped out after a mere 2 years.

See, while batteries are often advertised as capable of several amps (like 7A with my LiitoKala 18650 batteries that I often use in projects), that's only the current that they can safely take or deliver without blowing up. The manufacturer doesn't make this current rating with longevity in mind. It's the absolute maximum in current that a given battery can safely handle.

The longevity on the other hand directly depends on the demand that's placed on the battery. 500mA which is standard USB 2.0 rating or 1A which is standard USB 3.0 rating, no sweat. The battery will live for at least a decade of daily charges and discharges like that no problem.

But when you start shoving 3A continuous into a battery, that's when it will suffer. Imagine that your current workload is 500mA and suddenly you get shoved 6 times that work upon you. How long would you last?

Oh and not only the current is a problem, I suspect that it also overvolts the battery to maintain a constant current all the way till the end. When I charged my lithium cells with my lab bench power supply, the battery would only take a few milliamps when it got close to the supply voltage. Quick bit of knowledge: lithium cells are charged at constant current first, then when the current drops below that, it continues at constant voltage - usually 4.2 or 4.35V depending on the battery. So you'd set your lab bench power supply at 4.2V 500mA. But in that constant voltage mode, as the battery's voltage and the supply's voltage equalize, the current drops because the voltage difference becomes lower. Remember, voltage is what causes current to flow. Overvolting at the supply to stay in constant current mode all the way till the end speeds this process up but can be dangerous and requires constant monitoring of the battery voltage.

So, why does Huawei and a bunch of other manufacturers make these 3A power chargers? Well first it's because consumer demands ever more, regardless of the fact that they can just charge at 500mA for the night (8h of sleep) and charge a 4000mAh battery from 0 to 100% no problem. Secondly it's because sometimes you need that little bit of extra juice fast, like when you forgot to plug the damn thing in and you've got only 30 minutes in the morning to pour some charge into it.

But people use those damn fucking things even when they go to bed, making that 3A torture a fucking standard process!! And then they complain that their batteries go to shit?!

Hopefully this now made you realize that the fast charger shouldn't be used as a regular charger ^^

Smart India Hackathon: Horrible experience
Background:- Our task was to do load forecasting for a given area. Hourly energy consumption data for past 5 years was given to us.

One government official asks the following questions:-
1. Why are you using deep learning for the project? Why are you not doing data analysis?
2. Which neural network "algorithm" you are using? He wanted to ask which model we are using, but he didn't have a single clue about Neural Networks.

3. Why are you using libraries? Why not your own code?

Here comes the biggest one,

4. Why haven't you developed your own "algorithm" (again, he meant model)? All you have done is used sone library. Where is "novelty" in your project?

I just want to say that if you don't know anything about ML/AI, then don't comment anything about it. And worst thing was, he was not ready to accept the fact that for capturing temporal dependencies where underlying probability distribution ia unknown, deep learning performs much better than traditional data analysis techniques.
After hearing his first question, second one was not a surprise for us. We were expecting something like that. For a few moments, we were speechless. Then one of us started by showing neural network architecture. But after some time, he rudely repeated the same question, "where is the algorithm". We told him every fucking thing used in the project, ranging from RMSprop optimizer to Backpropagation through time algorithm to mean squared loss error function.

Then very calmly, he asked third question, why are you using libraries? That moron wanted us to write a whole fucking optimized library. We were speechless at this question. Finally, one of us told him the "obvious" answer. We were completely demotivated. But it didnt end here. The real question was waiting. At the end, after listening to all of us, he dropped the final bomb, WHY HAVE YOU USED A NEURAL NETWORK "ALGORITHM" WHICH HAS ALREADY BEEN IMPLEMENTED? WHY DIDN'T YOU MAKE YOU OWN "ALGORITHM"? We again stated the obvious answer that it takes atleast an year or two of continuous hardwork to develop a state of art algorithm, that too when gou build it on top of some existing "algorithm". After listening to this, he left. His final response was "Try to make a new "algorithm"".

Needless to say, we were completely demotivated after this evaluation. We all had worked too hard for this. And we had ability to explain each and every part of the project intuitively and mathematically, but he was not even ready to listen.
Now, all of us are sitting aimlessly, waiting for Hackathon to end.😢😢😢😢😢

Do NOT be overwhelmed nor discouraged when you realized how little you know.

after all software dev is still a work in progress :)

Looks like I'm getting fired on Wednesday :)

Long story:

*I add first unit tests to project.

*Boss adds new functionality and breaks all the tests so I can't compile and write more for what I'm working on.

*Boss is very fragile and cannot handle any comment that can possibly be taken as a slight against him.

Me: "I wanted to ask what our policy on unit tests is please? Because we haven't really said how we are treating unit tests, and everyone myself included is not thinking about them. I also haven't added tests when I fixed bugs and this time your changes broke the tests"

Boss 10 minutes later: "I want to speak to you in private".

Boss: "you are too forceful and direct. You said I should have added tests."

Me: "yeah but I didn't mean in a nasty way"

Boss getting louder and more aggressive: "You are too forceful"

Me: "I didn't mean it in a bad way"

Boss: "I didn't want to add tests for that!"

Me: "then why add any tests?"

Boss: "Fine we are not having this conversation now!"

*Boss storms out

I decided I can't speak to the guy about anything without upsetting him spoke to the manager before I quit because I can't work like this.

That resulted in a meeting with my boss, his boss and the head of HR where I ended up savaging him and told them I can't bring up anything as I can never tell if it will offend him and that I spend ages writing emails and trying to document communications because I just can never tell if I will upset him. Also that I cannot bring up any ideas because I can't tell if he will somehow get offended and that I can't even write code because if I change something he wrote at some point he will get angry.

My boss claims that I am extremely forceful and disrespectful and that I am constantly insulting him and his decisions.

We go back over a ton of shit and I refute everything he says. In the end I have to have a meeting with him on Wednesday where we either get things straight, he fires me or I quit.

I think at this point that our relationship is too fucked for him to be my team lead on a 6 man team.

Side note I keep bringing forth ideas because we have one database shared between 6 Devs, no pull requests (apart from mine and another new guy), no test driven development, no backlog, no team driven story pointing, no running tests before merging, no continuous integration setup, no integration tests, no build step on merge, no idea of if we are on track to our deadline other than his gut feeling, no actual unit tests backend - just integration with a test db, no enthusiasm to learn in the team and no hope.

Imagine if a structural engineer whose bridge has collapsed and killed several people calls it a feature.

Imagine if that structural engineer made a mistake in the tensile strength of this or that type of bolt and shoved it under the rug as "won't fix".

Imagine that it's you who's relying on that bridge to commute every day. Would you use it, knowing that its QA might not have been very rigorous and could fail at any point in time?

Seriously, you developers have all kinds of fancy stuff like Continuous Integration, Agile development, pipelines, unit testing and some more buzzwords. So why is it that the bridges don't collapse, yet new critical security vulnerabilities caused by bad design, unfixed bugs etc appear every day?

Your actions have consequences. Maybe not for yourself but likely it will have on someone else who's relying on your software. And good QA instead of that whole stupid "move fast and break things" is imperative.

Software developers call themselves the same engineers as the structural engineer and the electrical engineer whose mistakes can kill people. I can't help but be utterly disappointed with the status quo in software development. Don't you carry the title of the engineer with pride? The pride that comes from the responsibility that your application creates?

I wish I'd taken the blue pill. I didn't want to know that software "engineering" was this bad, this insanity-inducing.

But more than anything, it surprises me that the world that relies so much on software hasn't collapsed in some incredible way yet, despite the quality of what's driving it.

Me: *Installs travis*

Dev: oh what's travis?

Me: it's a continuous integration tool I wanna setup.

Dev: ... contin.... ?

Me: continuous integration, a tool that performs builds.

Dev: ah!, is it the new version of that deprecated tool we were using "client access"?

Me: ... no ... that's an authentication service that generates and stores oauth tokens. This is the continuous integration tool I told you about yesterday (and last week and the week before).

Dev: ... contin....

Me: ... con ........ continuous integration. It listens to branches on GitHub, downloads, builds, tests and then deploys the code.

Dev: ah ok ok, cool.

I would bet my monthly fucking salary he can not repeat what I said, tell me what oauth is, or explain what he's working on at the minute.

Jesus at this rate I'd bet my salary he can't tell me my name.

DST is my arch enemy.

"Why did I get paid for 7 hours instead of 8?"
"Because you worked from 1:00 till 9:00"
"Yeah, that's 8 hours"
"No it wasn't"

"Why does this input field say invalid time for 02:00?"
"Because that time doesn't exist"

"Why are so many tests failing"
"Because they check timestamps and durations which don't make sense in non-continuous time"

October is even worse...

IF LIVES DEPEND ON A SYSTEM

1. Code review, collaboration, and knowledge sharing (each hour of code review saves 33 hours of maintenance)

2. TDD (40% — 80% reduction in production bug density)

3. Daily continuous integration (large code merges are a major source of bugs)

4. Minimize developer interruptions (an interrupted task takes twice as long and contains twice as many defects)

5. Linting (catches many typo and undefined variable bugs that static types could catch, as well as a host of stylistic issues that correlate with bug creation, such as accidentally assigning when you meant to compare)

6. Reduce complexity & improve modularity  -- complex code is harder to understand, test, and maintain

-Eric Elliott

Quick recap of my last two weeks: 15 year old production server is basically dead, boss has taken over calls and claims credit for "resolving" outages (even though my coworker and I did the work, but ultimately the traffic died down enough to where it wasn't an issue anymore).

I go to a meeting to plan migration to a better server, boss bitches about not getting invited, I tell him I invited myself, and then he lectures about how that's not our job.

Different boss says we're migrating a schema for an application that should have been decommissioned 5+ years ago to use as a baseline. I explain what's going on, he says he understands, and proceeds to tell higher bosses it's perfect because there will be no user impact. OF COURSE THERE'S NO FRICKING IMPACT, YA DUNCE! there are no users!!!!

I merge two email threads together, since they discuss the same thing, but with different insight, and get yelled at, even though they requested it.

The two bosses I like are OOO for the next week, too, so I'm just sitting here hoping I don't say something that'll get me fired or sent to sensitivity training.

I'm just starting my on call rotation and don't know that I can do this. I cry when my phone rings, now, because I experience physical pain with how hard I cringe.

I got yelled at today by a guy because SOMEONE I DON'T KNOW assigned a ticket to him directly, rather than to the proper team (not his team). So I had to look into that, which at least had the benefit of preventing a catastrophic outage to our customers world wide, but no one will know because I don't brag at work; I'm too busy doing my job as well as most of my division/section/larger team, whatever the hell it's called. I saved us probably 25+ hours of continuous troubleshooting call from noticing something tiny that the people "smarter" than me missed.

**edit: sorry for typos; got my nails done yesterday but they feel like they're a mile long and I have to relearn how to type**

My devGoals for 2018:
- Build a RESTful API with NodeJS just for learning.
- Finish my first product (electronics sideproject).
- Convert more people to use CraftCMS or at least not use Joomla or WP.
- Get a raise.
- Add Continuous Integration to more projects.
- Add more unit testing where appropriate.
- Create and release a mobile app.

To be continued...
*playing to be continued meme sound*

Congratulations on a great year of continuous stress and being successful. As a reward here's a 50 bucks increase to your salary.

Yeah... great.. fuck you!

Feeling like I've gone back in time about 15 years!

Just told my CTO about various improvements we could make to the development process. Things like git, continuous delivery, agile project management apps such as Jira, task management such as Gulp, etc.

His response - "never heard of them. I bet they'll pass in a few months. Just another round of fads".

Project manager: We have 13weeks for this project. We have promised the client.

Me: okay, why wasnt I consulted on that commitment?

Project Manager: yeah.... we have to do it

Me: okay, if we have 2 dedicated backend and one full time frontend - ONLY on this project.

Project manager: (with the face of lies) yes yes sure we can do that.

6 weeks later, after continuous interruptions. Frontend is behind because he was only on the project to an amount of 2 weeks of the 6 weeks.

Project manager: Are we still on time?

Me: *looks around for prank cameras* no the f#*k we not

Project manager: can we put in weekends?

Me: its 2019 bro, that ain't happening

*But because I am a nice guy, and dont like taking Ls, we will have it ready. Just not gonna tell the project manager, he deserves a few sleepless nights *

After deciding to do what I love every day nothing feels like work any more, because continuous change and improvement is what I live for.

That is all. ✌🏼

Find a place where management is able to handle some criticism.

I personally think Agile/Scrum is holy, and I don't mean "yeah we kind of do our own version of it", no, fucking do it by the book. The PM shouldn't assign estimates. Developers shouldn't receive bugfix requests from anyone other than the scrum master. The CTO can't be your scrum master... etc.

If a company can't answer the question "What were the points of feedback during the last retrospective(s), and how are those points being picked up?" -- Don't work there.

Many other things are optional in my opinion. I could work at a company without QA, without fruit baskets, table tennis, without Friday drinks. I could even live without git & continuous integration, just emailing patches to a patch integrator. I don't care.

But maintaining a safe bubble of serenity and sanity for devs to do their work in, that is an absolute must.

Also, option to WFH as much as wanted. Offices are nice for social bonding, but they kill productivity for me.

In Italy (Milan)🇮🇹, job hunting is a fucking hell for misfits like me:
• Young(26)
• 1 year(working) experience + continuous learning/improvement at home
• Skillful and adaptable full-stack
• Willing to do greater things with software without being payed like a monkey

This is the last week working at my current company (from which I rejected the renewal of the contract for 26K€/13 months) and almost every time at a new interview everyone tries to down sell me by default or because of the fucking little time that I've been inside companies without even looking at my skills/capabilities.

Also many little companies made by the CEO and a technical manager that are looking for someone from which being provided food 😒(metaphorically).

(On another side, in one month, me and my gf need to move to a new apartment, the renting process sucks, and she has issues to find a non-slavering job because she is a foreigner(with good knowledge of English and Chinese) with very basic understanding of Italian and I see her crying often in my arms because it's hard and stressful for her to become economically independent as she would like to be)

!rant

Yesterday I got a pretty straight-forward task of fixing SASS linting errors from our project. I thought, "How many errors could there be?" Turns out there were just around 2000 errors across 109 files!

I was almost like, "Man, this is going to take a lot of my time!"

So, I started fixing the errors one-by-one with my headphones on and switching music genres after every 2 hours.

After almost 6 hours of continuous bug-fixing, my mind kind of became repellant to the possibility of the outer world and my fingers automatically fell on the right keys in almost no time. My brain was functioning like a computer itself.

And after the end of 7 hours, I reduced the number to less than 1000 errors.

Today, I continued the task and found out that there were some scoping errors I made yesterday (web developers would know this pain of '&').

And after working for almost 6 hours today, I got the number down to 500.

Not a rant, but I felt extremely content with what I did today.

I guess every day is not just about programming, sometimes, it's also about making your code better.

Thanks for reading! :)

A little late, and similar to other lovely ladies on here, but the greatest influencer for me is my husband.

He's always pushed me to learn more and be a better, cleaner coder. He taught me continuous integration, introduced me to the Atom editor, and showed me that my nerdy interests and choice of career can actually be quite attractive and not "intimidating" or "inappropriate” for a woman.

He's my go-to hackathon partner, my strictest code reviewer, and my life long teacher.

Ich liebe dich, mein Schatzelein! 😍

I've been fired today and somehow it was an relief :)
As I know that I am pretty much the only one who knows how the infrastructure works and I am the only one who actively tried to get the company to a better level of coding (tests, code reviews, proper deployment / continuous integration,...) It somehow feels like that gif.

There is nothing sexier than a well designed CI pipeline....i have wet dreams about that green check mark.

Imagine this clusterfuck:
A small company creates its own CMS on PHP 5.5 and MySQL, coded by fresh junior devs who apparently just got into coding.

My new employer sadly is one of their customers and now I got the task to migrate a group of tightly linked websites on subdomains to an actually sane and maintainable CMS...

Fuck me...

Apparently the continuous extension of the websites over the years got so labor intense, that the mentioned company lacks the manpower to fulfill further development wishes.

I've looked into the code today... let me tell you, PTSD is helluva thing.

- Each subdomain has a complete copy of the Crap Management System, there is no use of composer packages and each of the 50 folders in the webroot contains a mix of source code and images or other resources.
- LESS is transpiled into CSS by PHP on requests.
- There is no central file for environment variables like a ".env".
- Each website uses at least 5 different versions of jQuery, of which some jquery.min.js files were manually modified.

Don't get me started on how the DB is organized...

My work on this has just started, there will be more I've yet to uncover.

"C'mon, man! Gimme a break!"

I know people complain about Android Gradle takes so long to build (and I know the reason why, thanks to @DRHAX34) but for me that isn't what I have to wait for.

It's the shitty WiFi at work that causes issues/bugs I'll never experience normally lol

When my app builds I have to also connect to the internet and check for updates against the umbraco server, and it works if it fails to connect (naturally) but our internet somehow manages to stay connected enough to trick the app into doing continuous checks or some form of tiny and long downloads

I've been tempted and sometimes do use my own mobile data which would waste my tiny data (at the time)

Anyways fuck you shiternet lol

"Who needs a staging server, test suites and continuous integration anyways haha"
-company i just joined

I forged a katana once, under the supervision of a swordsmith. Nothing super special like damascus patterning or anything, but the cutting edge was pretty sharp.

Ugh sorry, lame word jokes.

In terms of software...

Microsoft Office Ribbon (cutting edge at the time, lol). Only as a maintenance drone on a bunch of manual search-and-replace work and merge conflict resolving.

Ariane 6 family of rockets (Welding X-rays and other DICOM quality assurance).

Software for continuous flow chemistry, developing microfluidic PCBs to perform Elisa immunology assays during the Mexican flu outbreak. Idea was to eliminate the need for microplates, expensive robots, microwell washers, etc — just have blood plasma, enzymecoated nanoparticles, antigen, conjugated detection reagents and substrates flowing programmatically through a PCB with a spectrophotometer built in.

and this is why continuous integration exists

A meeting about defining the
definition of done (…)
I know I mentioned it before, but it’s beyond stupid.

- Lasted 2.5 hours
- Didn’t solve shit
- Could have been solved by adding a freaking column in our Jira, but someone wanted a physical board cause let’s waste paper I guess.

Just imagine 2.5 hours of continuous suggestions and stupid reject reasons.

Fun fact: it was called by a “senior” dev which rejected every single purposal cause they also didn’t want to change the process.

Idfk why I didn’t leave the company sooner, had to get a massive burnout before realising my sanity is worth more than being paid the minimum in the office.

So I was talking with a coworker about a difficult situation I had with a manager years ago. It came down to how to interpret the company rules. The issue was about schedules and not being allowed to modify those schedules permanently. Say always leaving at 3pm on Friday every week kind of thing.

It came up because I wanted to work through my lunch to make up an hour. So my manager went pouring through the company rules and found this one phrase "you are not to modify your work schedule on a continuous basis". I was like what does that have to do with me working through lunch. He then told me that would make my work schedule during the day without a break to be a continuous day. Which to him was not allowed. I was flabbergasted at how insane the interpretation was on his part. It was not worth fighting it at the time.

Back to my current coworker. We keep talking for a while and he says to me: Was that manager an adversity hire?

I have been chuckling about this all day.

> at my previous job as mechanical engineer at an HVAC company
> was given recurring monotonous task
> decided to start a sizeable side project to automate it
> people got pissed at me because it worked too well, i.e., took their jerbs
> decided automating things was more fun than actual current job; also, people should be more hyped about continuous improvement
> switched careers into web-development

i.e., my most successful project was the one that changed my life for the better.

Boss just gave me a bonus out of the blue for my "continuous show of dedication and engagement". Not sure what I did specifically to deserve it, but pretty happy nonetheless!
Not really a rant, I just wanted to share. Spent the whole day smiling like a retard :)

SCREWED OVER GOOGLE WITH MICROSOFT!!!! YES!!!

So as I'm deaf, I've always had a problem with captions or lack of them.

I thought Live Captions would fix it but it's only supported on selected devices and not enabled for calls and conferences like Zoom, WhatsApp.

I tried hooking up my sound card with an audio capble to my phone which has LC and also Live Transcribe... but somehow wouldn't pick up the audio.

Then today I was like wait... I could just install a Pixel emulator... excepy seems Google thought of that...

(I installed VB Cable virtual sound card and routed sound out to mic in).

Well first apparently, the emulator does not actually identify as Pixel... it identifies as an Emulator that sorta looks like Pixel...

Which means no LC...

I installed LT and also a sound meter which confirmed it was getting the audio but no transcription...

Though I tried GBoard and it sorta worked..
But I would like continuous transcription... and so I open the app store and try all the apps until I hit MSFT Translate...

Which has a convo mode which seems pretty much designed to screw Google over lol. Just need to start a Convo with myself...

Me: has continuous mental breakdowns and health issues because of stress@college
Mom: if you dont finish college you wont get a good job
Me (already earning more than my parents together): yeah u r right
Me: *continues college*

Can i just die

"Get a job doing what you love, you'll never work a day in your life" they said

What they didn't tell us is that it would lead us to babysitting/troubleshooting continuous deployments at 3 am on a Sunday with a black Irish coffee and a manic look on our faces

How to get investors wet:

“My latest project utilizes the microservices architecture and is a mobile first, artificially intelligent blockchain making use of quantum computing, serverless architecture and uses coding and algorithms with big data. also devOps, continuous integration, IoT, Cybersecurity and Virtual Reality”

Doesn’t even need to make sense

Programmers nowadays have to...
… write 100%-covering unit tests;
… set up continuous integration, linters, hinters, style checkers, …;
… follow style guides for every language;
… meet impossible deadlines;
… meet impossible management/customer/end user expectations;
… read through terrible code others made;
… read through terrible documentation others made;
… make terrible documentation themselves;
… fight with the IDE;
… fight with the build tools;
… deal with unreproducible crash reports coming in from everywhere;
… debug code written at 2am (by themselves AND others);
…
…
…
… KNOW HOW TO PROGRAM.

Being a self taught programmer ( self teaching? don't know the continuous form :P) , I get really frustrated when my friends encounter a problem and just give up , I mean come on , Google it , ask on SO , ughhhhhhhh

I thinks I've figured out jAsE — the elusiveness, obscurity, secrecy, continuous re-spawning is to hide that it's really "Jeff Atwood, Stack Exchange" 🤔

Just received a test for a job I'm interviewing for. I was interviewing for a C++ position. Practice test: Create an REST API using SpringBoot, Spring Data, document with Swagger and implement continuous integration testing.

To be fair, I also mentioned I'm fluent in Java. But I've never touched SpringBoot or done any backend webdev, since my intention was to never get near it.

Deadline: Sunday. Game on...

Programming should be like art, where you try and learn different skills and tools to get better over time.... Not a continuous game of whack-a-mole where your try to hit everything with a hammer...

¯\_(ツ)_/¯

When good developers are afraid of refactoring and adding new classes is something to be feared, you need to rethink your architecture.

In fact, if there's ever that "dark corner" of code that no-one likes to work with, you've got to fix it.

It's like continuous deployment. We do it often because it's hard and having to deploy regularly forces us to make it easier.

Man, as much as I love reaping the benefits of Continuous Integration, I sure fucking despise having to set it up.

By the way, hi devRant!

devops guy: "Shut up, Perl is awesome. It is the best Swiss Army knife language."

I agree. Let us observe the architect in our metaphor, in charge of building our new building, insists on doing it ALL with a Swiss Army knife.

Yes, I agree with your comparison very very much.

(translation... I want to use Docker, a temporary db, and continuous integration. He wants to continue writing and reading tons of shit to a mess of JSON text files all over the place.)

You either die a good test
OR
You live long enough to become the bug

just received an email about a "hiring tournament", didn't know that was a thing... soo disgusting

"Hello John

How are things going in your career? Are you interested in remote work, at challenging projects in big companies such as Google, Pinterest, Udemy, eBay, and groundbreaking startups within a warm and continuous improvement environment?

BairesDev is holding an exciting hiring tournament, an online competition where you will fight against other developers for the chance to get hired and win incredible awards with the opportunity to be a part of great projects. We would love to see you there!

It will take place on Saturday, November 28th" (but the image says 12th 🤪🤪)

So you are "fighting" other developers for the chance to get hired, what the heck

This one is interesting

- 9 to 5 (including breaks) aka WLB
- Building products in my area of passion (Music, Art, or Travel)
- High paying (I don't care for those perks like free food or bean bags)
- Enough vacations without judgement
- Continuous innovation (fuck your 1830s product)
- Good social capital (teams should trust me for my decisions)
- WFH where I can opt to go in to office whenever I want (so that I can build my awesome battle rig at home)

Know your shit people!

Can we please stop using continuous delivery on mobile. I don't want to update your app every other week just because you decided to change a comment.
Also Bugfixes and improvements doesn't say anything as a changelog!

Perfect for continuous ingestion/digestion 😏👌

Stress made me fall into old habits of instead of saying stop and letting my team now that I was falling apart (not realising it myself even) I just kept saying "Yes, I fix that." to every single request that was made in the project.

The closer we got to the deadline, the more I hyperfocused and ignored the signs. I just kept working. The last two days I didn't even sleep.

Of course the launch botched. I finally broke down and both my mind and my body have given up, since yesterday I'm in a mental feedback loop causing continuous anxiety attacks and migraines. I literally CAN'T do anything but trying to not go back into fight- or flight mode and remember to breathe.

I FINALLY made my project manager aware (something I should have done days ago) that I am incapacitated and now I am waiting for medication (Oxazepam) to be picked up at the pharmacy by my husband.

I almost literally worked myself into the ground.

I've been here before. Never again.

This is what happens if you don't listen to your mind and body and put up a white flag in time.

First company:

- being sat at an office that didn't have chairs with proper back support. It would kill my back every day. Like sitting on a bar stool coding.
- not having access to basic resources (cafeteria, salary bonuses)
- being seriously underpaid ($200 under)
- not having an IT process pipeline (yeah, this is a huge one): no JIRA, no git, no VCS, no continuous integration, etc. I fucking spend 45% of the time fixing coding-unrelated shit.

Second company (very aggravating):

- dumb frontend bitch and privileged colleague who both kept telling me months on end to shut up and who wouldn't listen to my advice on anything, while my advice would actually help the company advance in productive ways. The key here is being told to shut up while stagnating. i.e. dead end job.
- people advancing in the company based on nepotism and favoritism, based on having tits and ass, rather than skills and independence.

- pointlessssssssss meetings where decisions are made solely based on the opinion of Mr. favorite senior dev. The rest just sits there like a bunch of sad saps and yay-nodders. Incompetent PO's who "would like to hear your input" but then when you give it, they completely dismiss you.

- pointlessssssssss monthly meetings with stakeholders, where the dev teams do nothing but clash and act like pussies in front of the PM just to get in his favor, but behind scenes continue to make the same mistakes and telling the CEO everything is fine. Goodness, how can it get more unproductive.

- completely antisocial and nepotistic 'colleagues' who won't even talk to you, let alone smile at you or be friendly. You saying good morning and them pretending you're vapor that doesn't exist. Go go company atmosphere! Especially during lunch, those are the worst times. Imagine sitting at lunch where everyone looks like you killed their dog and the rest is huddled up in little high school groups.
What else? The incessant and pointless smalltalk that makes me want to bang my head against the wall. Talking about dogs, kids, what show was on tv last night. The fuck man, do you have a brain?!

Third company:

- HR bitches who think they are the shit and developers are antisocial, helpless misfits, but they work with computers and they don't even fucking know what a status bar is! The irony!

- forced socializing and stigmatization for the opposite. Imagine coming into a company and you don't say good morning. Should that be a problem? No. Instead, everyone starts dogging on you and hating you just because you didn't smile in their faces and said: hiiiiiiiiiiii how did you sleep? Did you feed your dog? Fuck you.
Elliot (Mr. Robot): "Wouldn't it be awesome if there was a mute button for life?" -boop, boop, boop, boop...- Ahh.. there.. that's much better."

- CEO's sucking up to you but when it comes to salary increase, they say shit like: "Ahhh ya know, it's kinda difficult." Yet another dead end job.

Me: I don't understand, why is this not working?

After a few hours of debugging and continuous re-starting the server and most important praying to GOD

Me: F**k! how is this working? Ok let's not touch it, it's working

So I am finally plunging into continuous integration. If I make one more deploy script mistake, I've lost enough time to merit having learned a better solution than bash scripting calling git and rhc and py files I wrote. I have failing tests that are failing because they weren't updated after the million and a half urgent changes in the past 2 months, so it's time to act like I am a TDD fanatic and write the tests correctly. So much work. All from me listening to the constant req changes, listening to the urgency, letting non-devs get under my skin if you will. I'm optimistic in all the wrong places - I think I can write that by end of day let's try it. I'm lazy in the wrong places - I think that I can write that test later, because all I changed was XYZ (which took all night but I said I'd get it as close as possible didn't I?). And I think these handful of bash scripts are good enough to make sure I run tests? But remember, I didn't write the tests or I didn't go back and update them. Or the tests that fail, I'm too lazy. And so much of the tests, I would need to use, idk selenium for, and damnit if I really don't want to dig for element IDs to wait for every time I need an AJAX call.

Okay wow, I really did rant here. And discredited myself a bit lol I need to ignore the wrong lazy and embrace the right lazy. Protect myself from myself and from contributors. It really is, up to me now, to rescue myself from my bad habits. Bad habits perpetuated by clients urgency every day, to change things, that should have been finalized in November if we wanted a stable flipping system in January. It feels like the blind (client) leading the blind (me, when I do dumb shit like rush features out the door half tested).

Anyway all this came out, because I have been reading about continuous integration and stumbled upon this quote. And thought someone might laugh at the anachronism like I did

The client asked me today to include Internet Explorer to the compatibility list. After 5 minutes of continuous refreshing, Internet Explorer finally shows me in developer tools that it does not support Promises and Object.assign().

At that moment, my Promise to the client also failed.

So you heard from that awesome tool that apparantly everybody uses.

Go to the web page:
One single continuous page in 90ies style with random blahblah targetting expert users and various edge cases without context. Some lines about arcane build commands in an unfamiliar language.

Not even a single, comprehensive line, what it does, what it is good for, no minimal example or hint even how to run it.

So you write thousands of lines of dense code, but are not able to drop some first lines of plain, understandable english for people just visiting the first time? How hard could it be? Fuck you, srsly.

Was talking to a cousin of mine who's a priest and who spent 10 years in the Vatican, apparently they have 2-3 servers devoted specifically to acting as a firewall processing the data coming in and out of its network and it's a continuous stream of people trying to hack it, like think it would be pretty cool to see what way they have to whole thing set up, might see if he could take me on a tour (might even get a look at the private archives, though apparently it's mainly boring letters about popes meeting their mother and stuff

procrastinating by getting drunk since 11:00 AM, and writing specs for my (hypothetical) language/os/platform.

feeling righteous retribution because the client made me be stressed for 3 hours due to an issue that THEY caused but for 3 hours the only info I had was "there's a critical blocker issue and we're convinced YOU caused it"

well... no... i did NOT cause the fact that you UPGRADED PHP DURING THE WEEKEND BEFORE MONDAY'S PRESENTATION TO CLIENT (while waiting for an urgent commit from me).

seriously.

also, germans. i've heard many times from other people that they're... basically racist towards us (slavic nations), thinking of us as untermensch, coal-miner peons, but I didn't realize their passive-aggressive covertly smug demanding attitude is due to this, I just assumed it's a reaction to me being incompetent.

so yesterday when we finished the call (in preparation for which I tried to switch to their "client demonstration" branch since that's where the error was, and I wanted a headstart on fixing it, ended up in a place that my today's whole-day task should be "rebuilding the DB into working condition", because there's about 10 "core" sql scripts in two different folders, which need to be run (in a very specific order, of course, which readme tells you, but what it tells you has been outdated at least for 3 months, of course), and

...THE MAIN CORE SCRIPT THAT IS THE FIRST TO RUN, THAT CREATES THE DB schema, HAS THREE SYNTAX-LEVEL typos which fail it mid-way...

...the joys of continuous deployment via scripts, I guess? I would love to challenge any person from them to screenshare to me, manual deployment of the current version from zero, and I would be willing to give the person 20% of my monthly salary if they would be able to do it within 20 minutes.

but... well...
the point is, i should be doing not entirely bullshit stuff.
but yesterday's 6 hours of being in "at full attention because it seems we fucked up" totally convinced me, that today I'm taking a break.

So I'm gonna go buy another 3 beers and continue writing the specs of my dream language/os/platform.

We were a small startup with only 5-6 developers. I had to design the UI and develop most of the Android frontend, It was quite an easy and fun job for me because I don't get to see people rant about the design that needed to be implemented so, usually I design something that can be easily implemented.
We got 2 projects with a tight deadline and I took care of both project's design part and after completing the design I took the entire frontend of one project and rest of em started working with the other one. Usually we were a strong team and was able to deliver things real quick because we were expert in our intrested fields, I had a fast start in my project where the other project lagged a lot because of the desifn which was hard to implement by them, and the frontend was bo where near to get completed by the deadline and I couldn't help them out because it was all messed up shit handling both projects together.

Finally we were in a situation where none of our project are ready and the deadline was about to hit within a week, so we halted the other project and asked them to join me to complete the project am Working on, I had built most of the Android part and these fellows had a hard time figuring out stuff I made up (yeah, documentation was shit while you go agile), and finally things messed up and I had to work 2 continuous day and night without any sleep just to get the app ready 10 minutes before the official proto presentation.

The best part is I couldn't even get up from my chair and had a headache, fainted instantly when I took a few steps, but the product launch went good.

We fucked uo the code and both the projects just because we weren't available for each other considering the size of the team. Anyway we completed the project but It was a huge failure for us being first time to manage a startup.

Learned a lot of lessons,
Always make a team with people who are good at each of the aspect of development and never divide it to get shit done faster.

> be me
> be developing a react native app
>realize the iPhone X notch is clipping your content on the first/home screen of the app
>google says: simple fix
>find a built-in react native thing to add safe area padding
> refresh the app
> ohno.png
> the other screens with navigation bars already have built in padding
> TOOMUCHPADDING.jpeg
> remove safe area thingy
> finds a clever, not particularly hacky way to pad the home screen without showing the header bar by setting its height to 0 and the color to match the content background
> more-problems.app
> there’s a small 1–pixel light colored line separating the header from the content clearly breaking the otherwise continuous single color background
> google.sh
> wtf.txt
> stackoverflow.html
> no responses except something I’d already done
> keep experimenting
> tries basically everything to figure out where that line is coming from
>sets borders to thicccc and bright red
>no bottom border? Ok that’s not it
>opacity?
>forgetaboutit.mov
>try shifting the header position around by a few pixels? Maybe it’s misaligned with the white parent layer underneath?
> nope.jpg
>it’s past bedtime
>Sleep.jpg
>thenextday(today).zip
> what about the content? Is that misaligned?
> nope2.jpg
>Maybe its an iOS feature not a react thing?
> make a test Xcode project, completely native to test
> negative.dng (pun intended)
> more-furious-googling.mp3
> find a native iOS stackOverflow question with the same issue (1px line)
> realize your Xcode test wasn’t done properly.
>atleastimmakingprogress.iso
> start looking into the SO post
>it’s native so I have to find out how to do it in react-native
>invent a bunch of style parameters that don’t exist in the documentation to see if there’s an undocumented thing
>loadsaloadsaerrors.log
>googles for a react native version of the iOS only SO post
> somethingpromising.tar.gz
> *tries it*
> “Haha nope” -my code
> whataboutthisotherthing.bin
> KENSISHSBUCNEGWISBVSIDNRVSIDNFIRJRBDKFNFIDJFIFKFNR
> HOLY FUCK
> IT WORKED
> AFTER TWO FUCKING DAYS OF SHITTERY AND SHENANIGANS
>AND MANY STACKOVERFLOW EDITS TO A NOW VERY MESSY POST
>THEREISNOMOREBORDER(final).zip
>*screams of relief*

After continuous coding for more than 4 hours. Your brain just go .....

Do you think you can start all your weekdays' 730am to 9am with continuous honk noises every 5 to 10 minutes interval?

If you think you can, please teach me how to survive that shit. This much craps on daily (and especially as the start of the day) is definitely killing my mind and productivity for the rest of the day.

Firefox's Responsive Design Mode is shitty. After 2,3 refreshes, it just stops loading new changes. And hang like a drug overdosed whore who got continuous gang bang.

It just stops.

I have to turn it off and on again to be able to use it.

After about 7 hours continuous work in any one day, I’ve kinda had enough and noticed that work beyond this point is usually shit. I stopped trying and think fuck it now. Deadlines are mainly bollocks anyway. My life is a lot better because of it. Don’t do today what you can put off til tomorrow.Who’s with me?

Continuous emails from recruiters:

"I saw your profile on LinkedIn and wanted to see if you were interested in a career as an Area Sales Rep for [cell provider]. Here's the benefits!"

degree says IT, past jobs say IT, hobbies say IT, interests say IT. Do they just send that to everyone no matter what the profile says??

I need to convert lots and lots of lengthy hard-coded entities into backend objects, as I'm tired of pushing new commits every time something superficial needs to change.

Also, I need to figure out continuous integration. The guy who was going to help with that just left the company, and I was using his eventual forthcoming help as an excuse not to take responsibility for learning about it myself.

I need to learn golang and start converting some code to it, to see if the performance compares to the perl that's currently in place. Perl is brilliant, but aside from me, only old people know it, at my office. That definitely creates a longterm supportability issue.

My boss told me to dismantle the continuous integration server for me project and document how to do those manually.

Continuous integration is an example that failure is the piller of success :)

Testing? Continuous Integration? Watdat? Never heard of it
: ^]

Well I can say one thing for sure. The tooling found for Flutter in the form of IntelliJ and Android Studio is far superior than fucking around on a text editor das for sure.

Not really into the continuous nesting of widgets. But then again I was not a big fan of having jsx either.

Both options still better than fucking around with the Java Android api....and I fucking love Java.

Still feels like Google realized that such approach was better, else I don't think they would have justified the creation of the Flutter lib. And yes. I know that it is not a complete replacement for Android Java, but the interfacing between Dart and the Java api feels more natural at least to me and the widgets look native af so we go on with them big plus digits.

Tl;Dr Im the one of the few in my area that sees sftping as the prod service account shouldn't be a deployment process. And the ONLY ONE THAT CARES THAT THIS IS GONNA BREAK A BUNCH OF SHIT AT SOME POINT.

The non tl;dr:

For a whole year I've been trying to convince my area that sshing as the production service account is not the proper way to deploy and/or develop batch code. My area (my team and 3 sister teams) have no concept of using version control for our various Unix components (shell scripts and configuration files) that our CRITICAL for our teams ongoing success. Most develop in a "prodqa like" system and the remainder straight in production. Those that develop straight in prodqa have no "test" deployment so when they ssh files straight to actual production. Our area has no concept of continuous integration and automated build checking. There is no "test cases", no "systems testing" or "regression testing". No gate checks for changing production are enforced. There is a standing "approved" deployment process by the enterprise (my company is Whyyyyyyyyyy bigger than my area ) but no one uses it. In fact idk anyone in my area who knows HOW to deploy using the official deployment method. Yes, there is privileged access management on the service account. Yes the managers gets notified everytime someone accesses the privileged production account. The managers don't see fixing this as a priority. In fact I think I've only talk to ONE other person in my area who truly understands how terrible it is that we have full production change access on a daily basis. Ive brought this up so many times and so many times nothing has been done and I've tried to get it changed yet nothing has happened and I'm just SO FUCKING SICK that no one sees how big of a deal this. I mean, overall I live the area I work in, I love the people, yet this one glaring deficiency causes me so much fucking stress cause it's so fucking simple to fix.
We even have an newer enterprise deployment. Method leveraging a product called "urban code deploy" (ucd) to deploy a git repository. JUST FUCKING GIT WITH THE PROGRAM!!!!..... IT WAS RELEASED FUCKING 12 YEARS AGO......

Please..... Please..... I just want my otherwise normally awesome team to understand the importance and benefits of version control and approved/revertable deployments

Does anyone else feel that "retirement" is an outdated concept? Our generation will probably never truly retire, not in the same sense that this word meant in 20th century.

Considering how much the government-mandated retirement age went up; most of us will prolly die from continuous stress way before the day of "retirement" comes

Inspired by a programming is a constant/continuous thing. Every small and big achievements, from squishing a bug, finding a workaround, pressing the "Build" button and the programme runs. Each time the brain feels expanded like when a baby discovers new things, a tiny creature in a gigantic Universe of endless possibilities.

I hate the fact that our university is hiring ex-developers from the year 1990-2000 to teach us. They are knowledgeable about many stuff like datastructures and algorithms, but when they force a project on us where we have to use some new tech, the students become the teachers. Heck, one of the requirements of the project was to set up a continuous integration server and we had to explain to them that we needed a server and how git was part of it. (classmate even had to explain how git worked to them).

I know that adapting and learning stuff yourself is part of the education, but why are we the ones who should explain the stuff we MUST know to get our degree to the teachers who are supposed to actually, in my opinon, be experts and knowledgable in what we have to know and learn..

java app continuous deployment via ftp :-|

This is so nice..💙😄

<Heading> 
Synopsis of Gita (religious book of Hindus)

<Stanza 1> 
Code is an illusion
Today you are coding
Tomorrow someone else would do it
Thereafter someone else

<Stanza 2>
What did you learn
That is helping you in this Project
What are you learning
That will help you in your next Project

<Stanza 3>
Bug is the truth of life
It is today, and will remain forever
You think you have debugged the Bug
You are wrong

<Stanza 4>
It is continuous
In various new forms
It pops up
Recognise it Parth (Son of Hindu God)

<Stanza 5>
That's why go on making Codes
Don't think about the Bug
They will come to you
On their own

Just realized that after 3 months of continuous samsung s9 use my phone is still as fast as it was when i got it out the box.

Man I love this stupid phone so much. Everything opens up so fast and this sob is as smooth as an iphone when it comes to the speed.

Pure goodness. Still would like to try a more pure Android environment u know? Like back when nexus was still a thing. I don't really dig the pixel phones too much but know that I am on a more open carrier and I can use phones like the one plus series I think i know what my next phone would be.

Nothing personal samsung, you have been good ans loyal, but i want to play with more phones.

I really love smartphones.

Stop wasting time setting up continuous integration environment and get on with real work.

2 days later: why aren't we using continuous integration, the plan says we have to.

What the fck is CI/CD?!! Hmmm 🤔 I don’t know, but it sounds trendy so might as well pretend to know it to sound cool.

When my tests pass AND CI succeeds. Or just when my php code works haha

I HATE the idea of only releasing on pre-determined schedules despite work being completed and just waiting for that day to arrive.

I'm a co-founder of a small software company. We have partnered with another particular company that also writes software. Some of our clients have access to paid content of that company's services through our application.

Every once in a while, our clients will report issues with that company's service to us, because they access it through our application. They think it's our issue.

We then pass the report on to the partner company, telling them that their stuff is broken. Their reply goes like this:

"Ok. We'll get the bug fix scheduled, and we'll release it next Thursday."

"Next Thursday? The issue is now, they can't use the service."

"That's our scheduled release date."

O.M.G.

We voluntarily walked away from our safe, cushy jobs working for other people, taking enormous pay cuts to start this company. Now, we're 6+ years in, disrupting established fat-and-happy competitors in this space. I GUARANTEE you that if we had that same attitude, we would have been absolutely obliterated early on.

We are quick. Guided by kanban boards, our suite of unit tests and integration tests is vast and kick-ass. With continuous integration and the click of a button we know if we broke something or if the piece we're working on is ready to be pushed to production, IMMEDIATELY. Our "release schedule" is when the damn thing is complete.

It isn't all bad. Our integration with them has been beneficial for both of us. I just loathe their snail's pace which negatively affects our mutual customers. It can make us look bad, and we can do nothing about it.

Blah.

So here's how the story goes.

I was in my academic writing class the other day and we were learning about APA formatting for our argumentative essays. We have a blackboard, whiteboard, projector connected to a pc and even a lovely projector screen to present with in the classroom.

I sit at the front right of the room. Closest to the window(it's behind me as all the desks face inwards)

Professor walks up to front of class and says we are going to learn how to format our typed essays properly.

Awesome, I thought. Pulled out my XPS laptop and fired it up. As I was making a new Word document, I hear scratching. I look up and the professor is writing with CHALK on the BLACKBOARD. I was astonished. Making matters worse, she started from the far left of the board from which the glare from the window was the greatest. I could not see anything. And from that point on I knew this class was going to be abysmal.

What was so depressing was my professor never once touched the projector. Scraping and erasing. Over and over. Couldn't see if it was a period or a comma after the first initial.

My eyes were never so dry from squinting, rolling my eyes and face-palming over and over. After an hour and 15 minute class, I was not far away from drowning my XPS in my tears.

Recently I have started working with a company with a codebase older than I am. Hundreds of different projects with GoTos everywhere, and all error handling rendered useless by the continuous use of On Error Resume Next.
I feel like a mixture of Indiana Jones amd Gordon Ramsay...

That feel when your job's codebase is well-maintained, extensively covered with unit, integration and full product automated tests, everything is run through continuous integration, and every change has to be scrutinized and reviewed by multiple people; so you have barely anything to devRant about :(

I am amazed at human stupidity.

I always enjoyed the idea of DevOps: to use virtual machines and constant integration in order to avoid errors and free the developers of hard-to-setup environments and somehow-it-works compilations.

I am amazed how [company I used to work for] managed to turn this into a nightmare.

Just imagine: silent forests, the smell of flowers, no developer trust to the point your devs can’t either make docker environments cause reasons nor they can access your actual machines programmatically because they are filthy peasants, forcing them to do everything manually: every deployment will be a frustrating editing process which takes up to an hour, but here lies the trick... it will still have continuous integration... or better: every feature will be deployed as if it was a release.

The true peak of illumination:
Turning a tool into a disease.

Take a sip of tea, manager... you deserve it.

Just thought about this job because I keep being tempted to just start my own company. The more I think about it, the less being employed makes sense, given my end goal.

Been worrying about this for a few weeks now.

As a junior dev, how do I continue to improve (with respect to coding style, technique, etc.) when my seniors are only slightly better than me in a technical regard? I feel like I'm improving at a drastically slower pace than when I first started.

🐢

Teach students the importance of clean code/architecture and testing. Even if they dont yet understand the more complex topics such as architecture, they should understand why quality is important and that software is a craft more than a science. You cant just apply principle X and insert design pattern Y and profit++. You actually have to think and constantly improve. AND TEST.
Think I would probably also cover things like build automation and continuous delivery. These are now important things for junior devs to know about going into companies.

Two (2) senior developers and one (1) senior tester left our team and I am left with two (2) Java legacy applications that are hard to maintain. Here is a list of things I hate about these old webapps (let's call them app A and B):

1. App A depends on 80% web services. If one web service for a product or warehouse goes down, work flow is impeded while prod support team checks with the core services team for repair

2. App B is a maven project with multiple modules dependent on libraries that are dependent on company's internal libraries. So if we want to upgrade to OpenJdk 9 and up, the project will definitely produce a lot of errors due to deprecated/unsupported codes

3. App A is dependent on Tibco and I have no experience on that

4. App B's continuous integration build tool is Jenkins and the jobs that build it has a shell script that wasn't updated during the tech upgrade enhancement. The previous developer who did the knowledge transfer to me didn't tell me about this (it should be considered a defect on her part but she already resigned)

5. App A when loaded in eclipse IDE is a pain to work with since it is only allowed to build a war file using ant. I have to lookup in quick search instead of calling shortcuts (call hierarchy) because the project wasn't compiled via eclipse.

6. It's impossible to debug app A because of #5

7. Both applications have high priority and complex enhancements and I have no other teammates to help me

8. You never know what else can go wrong anytime

Killing people is bad. But, there should be a law to allow killing people who don't write proper unit tests for their code. And also those "team leaders" who approve and merge code without unit tests.

Little backstory. Starts with a question.

What is the most critical part of a quoting tool (tool for resellers to set discounts and margins and create quotations)? The calculations, right?
If one formula is incorrect in one use case, people lose real money. This is the component which the user should be able to trust 100%. Right?

Okay. So this team was supposed to create a calculation engine to support all these calculations. The development was done, and the system was given to the QA team. For the last two months, the QA team finds bugs and assigns those to the development team and the development team fix those and assigns it back to the QA team. But then the QA team realizes that something else has been broken, a different calculation.

Upon investigation, today, I found out that the developers did not write a single unit test for the entire engine. There are at least 2000 different test cases involving the formulas and the QA team was doing all of that manually.

Now, Our continuous integration tool mandates coverage of 75%. What the developer did was to write a dummy test case, so that the entire code was covered.

I really really really really really think that developers should write unit tests, and proper unit tests, for each of the code lines (or, “logical blocks of code”) they write.

I have officially decided to use CI (Jenkins) at work because "apt-get update && apt-get upgrade -y && composer self-update && composer update && npm update -g && npm update && bower install --allow-root && gulp" after a pull doesn't seem healthy 😂

When ever I need to get a passing build quickly...

I kinda missed the continuous struggle around the r8169 driver and Nvidia drivers. Thank god the Arch ISO has this problem too.
These two companies should be fined out of existence, there's no reason not to open source the driver, and this renders the product useless.

pandas can suck my balls.

N
I
H

I'd rather roll my own.

edit: but also xgboost can suck my balls.

Treating every OBVIOUSLY continuous-valued entry as a 'category'.
All searches for this problem turn up tutorials and documentation on how to CONVERT continuous and numeric values into classes or categories.

Not a single fucking document addresses the problem of when pandas or xgboost refuses to treat numeric inputs as numerics and insists on pushing an error that your data is categorical when every fucking inspection shows the type as numeric.

We had a project where we had to code in c# and setup a continuous integration server and create some tests for our application.

Our teacher asked:"Are you guys using junit?

He was serious.

1st. Put my Razor Blackshark Aviator headset on. Noise cancellation the low-tech way with full earcups.

2nd. I go on music genre binges for weeks at a time. Lately I've been listening to Viking inspired Dark Folk music like Wardruna, Fejd, Corvus Corax, and Forndom. That came after I did a month of proto rock n roll blues from the southern United States like Leadbelly, Blind Willie Johnson, and Mississippi John Hurt. I also drop some liquid DnB on a bender here and there.

3rd. I set up Hyper.is terminal to use the power plugin that makes sparks fly off of each keystroke.

4th. I set up Atom to work similarly with a continuous code counter that keeps a score of how long and fast you type continuously when coding. It also throws sparks off of the cursor as you type.

5th. Pop my neck and fingers and geterdun.

What's your experience with continuous delivery? On every push to the master, the complete current codebase goes to production.
Of course not visible to all the users, but hidden behind feature flags.

Story of my first successful project

Being part of a great team, I've shared in a lot of successes, one I am particularly proud of is my first attempt to use agile methodologies in a deeply waterfall-managment culture.

Time was June/July-ish and we applied for a national quality award where one key element in the application stated how well we handled customer complaint resolution.
While somewhat true (our customer service is the top-shelf good stuff), we did not have a systematic process in resolving customer complaints. Long story short,
the VP lied on her section of the application. Then came the 'emergency', borderline panic meeting (several VPs, managers, etc) to develop a process to better manage
complaints before the in-house inspection in December.
As most top priority projects go, the dev manager allocated 3 developers, 2 DBAs, and any/all network admins we would need (plus all the bureaucratic management that wanted their thumb in the pie).
Fast forward to August, after many, many planning meetings, lost interest, new shiny bouncing balls, I was the only one left on the project. The VP runs into the dev manager in the hallway and asks "Is my program done yet? If its not ready before December with report-able data, we will not win the award."
The <bleep> hit the fan...dev manager comes by...
Frank: "How the application coming along? Almost done?"
Me:"No, haven't really started coding. You moved Jake and Tom over to James's team, Tina quit, and you've had me sidetracked helping other teams because the DBAs are too busy."
Frank: "So, it's excuses. You really think the national quality award auditors care about your excuses? The specification design document has been done for months. This is unacceptable."
Me: "The VP finished up her section yesterday and according to the process, we can't start coding until the document is signed off."
Frank: "Holy f<bleep>ing sh<bleep>t! No one told you *you* couldn't start. You know how to create tables and write code."
Me: "There is no specification to write to. The design document is all about how they plan on reporting the data, not how call agents will be using the application to serve customers."
Frank: "The f<bleep> it isn't. F<bleep>ing monkeys could code against that specification, I helped write it! NO MORE F<bleep>ING EXCUSES! This is your top priority from now on!"

I was 'cleared' to work directly with the call center manager and the VP to develop a fully integrated customer complaint management system before December (by-passing any of the waterfall processes that would get in the way).

I had heard about this 'agile' stuff, attended a few conference tracks on the subject, read the manifesto, and thought "I could do this.".

Over the next month, I had my own 'sprints' and 'scrums' with the manager (at the time, 'agile' was a dirty word so I had to be careful of my words and what info I shared) and by the 2nd iteration had a working prototype.
Feature here, feature there (documenting the 'whys' and 'whats' along the way), and by October, had a full deployed application.

Not thinking I would get a parade or anything, the dev manager came back from a meeting where the VP was showing off the new app to the other VPs (and how she didn't really 'lie' on the application)

Frank: "Everyone is pleased how well the project turned out, except one thing. Erin said you bothered him too much with too many questions."
Me: "Bothered? Did he really say that?"
Frank: "No, not directly, but he said you would stop by his office every day to show him your progress and if he needed you to change anything. You shouldn't have done that."
Me: "Erin really seemed to like the continuous feedback. What we have now is very different than what we started with."
Frank: "Yes, probably because you kept bothering him and not following the specification document. That is why we spend so much time up front in design is so we don't waste management's time, which is exactly what you did."
Me: "We beat the deadline by two months, so I don't think I wasted anyone's time. In fact, this is kind of a big win for us, right?"
Frank: "Not really. There was breakdown in the process. We need better focus on the process, not in these one-hit-wonders."

End the end, the company won the award (mgmt team got to meet the vice president, yes the #2 guy). I know I played a very small, somewhat insignificant role in that victory, I was extremely proud to be part of the team.

The conversations that come across my DevOps desk on a monthly basis.... These have come into my care via Slack, Email, Jira Tickets, PagerDuty alerts, text messages, GitHub PR Reviews, and phone calls. I spend most of my day just trying to log the work I'm being asked to do.

From Random People:
* Employee <A> and Contractor <B> are starting today. Please provision all 19 of their required accounts.
* Oh, they actually started yesterday, please hurry on this request.

From Engineers:
* The database is failing. Why?
* The read-only replica isn't accepting writes. Can you fix this?
* We have this new project we're starting and we need you to set up continuous integration, deployment, write our unit tests, define an integration test strategy, tell us how to mock every call to everything. We'll need several thousand dollars in AWS resources that we've barely defined. Can you define what AWS resources we need?
* We didn't like your definition of AWS resources, so we came up with our own. We're also going to need you to rearchitect the networking to support our single typescript API.
* The VPN is down and nobody can do any work because you locked us all out of connecting directly over SSH from home. Please unblock my home IP.
* Oh, looks like my VPN password expired. How do I reset my VPN password?
* My GitHub account doesn't have access to this repo. Please make my PR for me.
* Can you tell me how to run this app's test suite?
* CI system failed a build. Why?
* App doesn't send logs to the logging platform. Please tell me why.
* How do I add logging statements to my app?
* Why would I need a logging library, can't you just understand why my app doesn't need to waste my time with logs?

From Various 3rd party vendors:
* <X> application changed their license terms. How much do you really want to pay us now?

From Management:
* <X> left the company, and he was working on these tasks that seem closely related to your work. Here are the 3 GitHub Repos you now own.
* Why is our AWS bill so high? I need you to lower our bill by tomorrow. Preferably by 10k-20k monthly. Thanks.
* Please send this month's plan for DevOps work.
* Please don't do anything on your plan.
* Here's your actual new plan for the month.
* Please also do these 10 interruptions-which-became-epic-projects

From AWS:
* Dear AWS Admin, 17 instances need to be rebooted. Please do so by tomorrow.
* Dear AWS Admin, 3 user accounts saw suspicious activity. Please confirm these were actually you.
* Dear AWS Admin, you need to relaunch every one of your instances into a new VPC within the next year.
* Dear AWS Admin, Your app was suspiciously accessing XYZ, which is a violation of our terms of service. You have 24 hours to address this before we delete your AWS account.

Finally, From Management:
* Please provide management with updates, nobody knows what you do.

From me:
Please pay me more. Please give me a team to assist so I'm not a team of one. Also, my wife is asking me to look for a new job, and she's not wrong. Just saying.

So, right now we upload production code by means of FTP.
I said it would be better to use continuous deployment using Docker, but they said it was overkill (I work at a small company).

Because manually uploading by means of FTP is so much better right...

Learning to tech to speed up learning.
Using a new cooperative learning technique, AI Lab researchers cut by half the time it took a pair of robot agents to learn to maneuver to opposite sides of a virtual room.

A combination of deep learning and reinforcement learning algorithms are responsible for computers achieving dominance at challenging board games like chess and Go, a growing number of video games, including Ms. Pac-Man, and some card games, including poker. But for all the progress, computers still get stuck the closer a game resembles real life, with hidden information, multiple players, continuous play, and a mix of short and long-term rewards that make computing the optimal move hopelessly complex.

Image: Dong-ki Kim

the one that exists (c#) seems underused compared to where it could (or even should) be used. and the place that uses it the most (enterprise) butchers and mangles its use, just as enterprise tends to do with everything.

the one that i'm designing... the fact that it doesn't exist yet, and that even as i'm zeroing in on syntax and philosophy that i'm very much starting to be proud of, i still don't have a proper idea of how to implement even the most basic parser/interpreter for it, not because it's in any way difficult or unusual, but just because... i've never done that before, so i get into weird circular thought paths that produce weird nonsensical code...

... on top of that, i still only have a very, very fuzzy idea of how will it (sometime in extremely distant future) actually implement the most interesting and core feature - event-based continuous (partial) re-parsing of the source code and the fact that traversing the tokens at the leaf level of the syntax tree should result in valid machine code (or at least assembly) that is the "compiled" program.

i *know* it's possible, i just don't yet know enough to have a contrete idea how exactly to achieve it.

but imagine - a programming language where interactive programming is basically the default way of working, and basically the same as normal programming in it, except the act of parsing is also the (in-memory) compilation at the same time, so it's running directly on the hardware instead of via interpretrer/vm/any of that overhead crap.

also then kinda open-source by definition.

and then to "only" write an OS in that, and voilá! a smalltalk-like environment with non-exotic, c-family syntax and actual native performance!

ahhh... <3

* a man can dream *

PM: "We would like our automated testing / continuous integration in AWS"

Me: *Army crawling towards Jenkins with my last dying breath*

<<prev. #wk235 advices>>

~ Study the Error log deeply, Google each line if needed. Don't give up.
~ Learn by doing. Don't just read/watch.
~ Practice breaking down the problem statement first in different components and hierarchies. Don't jump into coding right away.
~ Write some, review some. Don't put off review for later.
~ Even if you don't exactly follow the best security practices - always ensure that your program is safe for use. Especially for user-inputs, etc, pay attention.
~ Never distribute code with passwords/keys written in it.
~ Don't hard code stuff, use Config file, environment variables, etc.
~ Try to automate repetitive stuff like build and deploy etc
~ Save and backup you code.
~ No one knows everything, also, today's knowledge gets outdated tomorrow. Continuous learning is synonymous with this field.

<<next #wk235 advices>>

You can't do both Continuous Delivery and Code freeze.

!dev
After 2 weeks of continuous efforts, I surrender

I'm at this magnificent company, working scrum, doing continuous integration which is really very cool. But although the features we develop are really nice it is sooooooo boring.

One of our team members emphasized that we should not pick up new stories if we haven't finished previous stories yet. I agree to some extent but think it is ok to pick up new stories if you have nothing to do. But we may not.

So, here I am now. Literally waiting for the day to pass. This sucks sooooo much!

I'm a hard worker and perform at my best under pressure with many things to do. Now, I just deployed one tiny little story today. I can do much much more. I feel so useless and cannot believe that my client pays so much just for me being at the office. And occasionally clicking a button and writing a line of code. This is so fucked up.

OMFG. So my isp sucks. Like most isp do now adays. I was watching TV and I was trying to find a specific channel. I look for the channel list online. And oh my fucking God the site is horrible. They have some continuous loading script so I don't have to load all 2500 channels at once. But... It's fucking horrible I got to channel 120 then tries to scroll back up to see if there was a search bar. But guess what... It kept scrolled bg me down. Then I thought maybe if I refresh the page. Nope... It does not send me to the top it sends me to the fucking bottom. Since I can't clear cache on mobile im stuck scrolling up. Why can't they have a site that just fucking works.

When your senior says he may as well stops working as I'm always refactoring his code...

Same sentence says I copy what you've done in other places so I don't see why it isn't good enough. By copy he leaves redundant code in there too.

Am I a being a douche is he just being over the top?

- He writes code and expects it to live for a long time.
- I write code and will go home and refactor my own code.

are you able to give 1/+ hour to any hobby project/self learning (technical, that could help you in infuture switch) ? if yes, HOW??

I want to create this website , but i keep on delaying that. i just have a faint idea of how the assoc technologies would be used , but putting even 1 hour aside becomes difficult once i come back from the gym in the evening. plus the effort to open laptop, refocus self and do something only to close laptop after an hour feels very less rewarding. I can't achieve anything in 1 hour, i need a continuous slot of 6+ hours to achieve something and plan for the next day.

do share any better mind makeup

A few weeks ago I finally got buy in to migrate our web team to GitLab for CI/CD.

All week GitLab has been having issues, pretty much rendering us unable to deploy anything with confidence.

Can't wait for _this_ to come up. haha

So.. i have been doing internship with a good startup for last 2 months. It was supposed to be a 3 month internship and then maybe a job offer. I accepted this , but with a disclaimer that i will be taking leaves for exams.

They looked like they didn't liked this condition, saying "we won't be giving pay for those days" , "you will need your manager's approval", etc, but later i took 5-6 continuous leaves for my papers and my manager( aka the ceo) wouldn't even read my approval mail ( i did got deductions for those leaves tho, but i was fine with it )

Now the situation is that my final end term exams are coming up. They are supposed to go on for 15 days somewhere in December beginning, but i also need an extra 10-15 days to cover the syllabus for it. Apart from those, there are other college stuff like Second Sessionals, internal practicals ,minor project report submission , etc are also coming up, that are supposed to take anywhere from 1 to 5-6 continuous days in the first weeks of November.

So i asked my company for 2 months of leave to handle my college environment. The tasks assigned to me are incomplete , but i am well versed in those and might complete it if i had more time. I gave them an option that i will resume my work from January and complete my 3 months of internship ( i currently am about to complete 2 months , November would have been the 3rd) , but they said that they are "freeing me" in the October only ( i guess this means that my internship is being terminated and am off from company's payroll). They also asked me to contact company once all exam stuff is over, but yesterday i got suddenly removed from the company's slack group. I am not sure how to look at this.

They have also asked me to prepare a report on what i have done. Now i can send them a report like what i would have given to my college : containing more useless info and a few points on my work . Or i could provide them with a deep report on what i did each day, what are the bugs , what are the resources that i found , what are the things that need to be enhanced, links to important groups and people... Etc . I have so much of information that i fear they might hire someone else to complete all stuff that i have started and my material would give him a kickstart.
But on the other hand , it was their office that i worked in, their ideas that i built upon, so i feel a moral obligation to provide all assistance to my replacement.

What should i do?

(tldr : company asking for a report on work you did during internship that was supposed to be converted to job . wwyd?)

For all the effort it takes to setup CI/CD it's totally worth it. My god this is marvellous I've wasted over 40 build minutes already just to see a spinner spin until it turns green :-D

Every time we have a release, "Release Engineering" stops building our test environments from master. I've been preaching Continuous Deployment for months and here we are with the most broken system. The build actually builds all test environments AND prod from the same branch because "it's easier" for "Release Engineering". So now I have to wait for the code freeze on release and hope RE doesn't fuck up and deploy an untested branch to prod... AND hope we're given enough time to test and debug the next release since we can't right now...

How often does this happen to you?

Just updated our continuous integration and for some reason the BuildAgents, who update independently, just kept failing to update.

Tried every trick in the book, debugged everything.
Kept complaining about being unable to delete files, frigging Windows file system being an idiot as always...
Was about to give up and migrate everything to a fresh system until I realized...

*reboot*
Ah, it works now!

... Why does it always take me so long to realize that's an option!?

The struggle continuous... should I work on my personal website or just PlayStation all night long?

I feel like being a contractor who can get continuous work would be a great job

Wallaby is a pretty awesome tool that facilitates continuous testing in editor as you code.

While it's not cheap, it has been a great investment in my stack.

Every day I ask myself at least 5 (not too difficult) questions about programming (for instance "Can I compile Java in runtime?")
If I don't know them - I find their answer somewhere
It is like continuous integration, but with my knowledge - small portions of info are saved well in my brains))

Business managers not taking ownership for quality of data. If systems are not designed with proper data validation controls at each upstream data entry point them downstream processes and revenue will suffer. You will have a continuous data cleanup black hole.

Continually continuing my continuous integration

Okay...So is it a good thing or a bad thing then?

Today one of the guys at work said

"The dev server goes down because we make changes all the time - continuous disintegration"

Not sure what I should put this under but I just had an app idea. I've tried journaling but can never keep going for more than a few days but if I have like a conversation with someone one like "how was your day?" or I start an internal dialogue, I can go on for a while and just feels natural.

So I'm thinking what would be good is if I had a virtual chat buddy/psych like a continuous QA but but also smarter then cyberduck and can save the whole chat. So it basically is/can become a journal or even a blog post.

Wondering if there's something like that already or some chatbot could help?

Think I heard something before that Facebook may have one but I think it's a huge ML program that needs to be trained on a lot of data.

Any your thoughts on this idea?

Okay, my initial revulsion for ABI has receded. All things considered, my options aren't that bad. I just had to change my perspective from "huge downgrade from static linkage" to "huge upgrade from a message channel".

Just like a web API, I have to draw a continuous line through the program that separates specific concerns of interest that must fall on one side or another, and which can only cross through things with specific properties.

There are several crates shipping a number of different binary-compatible types, even generic types. Not everything can cross, sure, but maybe not everything should cross either. Maybe a DLL should receive an opaque handle for certain things, such as interpreter internal code representations. Maybe having these separated is important enough to justify having a translation layer.

I'm sure there's much woe ahead, but I'm learning to stop worrying and love the ABI.

I realized that using hilbert curve, I can draw one continuous line on a closed mesh surface that has no holes, I’m not sure if it’s going to be beautiful though, but I’m gonna try it anyway

I once was working on my family's business during summer and was doing something on the laptop that was there (according to the owner, it was in a "good shape" - oh my god that laptop nearly gave me cancer: an old Toshiba, running W10, with half the F keys not working - specially F5. I CAN'T LIVE WITHOUT F5 OH MY GOD -, and also the ➡ key (arrow keys). It was bought in a flea market and some IT guy, a friend of the owner, repaired it a bit and installed the OS because a laptop that old ran WinXP or Win Vista for sure) when suddenly it died on me.
I rebooted the thing and right before the time it should be showing the windows logo, the screen froze (on a black screen with some text) and it started to beep. Loudly. A loud continuous beep. I turned it off and on some times after that, seeing if turning it off and on did something (as it seems to work LoL) and it continued with the beeping. After a quick search I found out that that was a common problem with Toshibas that old, and that I needed to press F2 (that key worked thank god) when the black screen with the text showed up (I don't remember what was written there, it were some booting instructions, I think).
It worked. Great. Now the N key doesn't work when I press it. Greeeeeeeaaaaaat. Also it seemed that, when I opened the start menu, it would automatically write "nnnnnnnn(...)" without me pressing any key (pressing any key would make it stop though, maybe it was stuck).
Then I told the owner not to turn it off, because the laptop would start beeping and such (and I know he'd panic about it).
From then on I think it went off for good and now he's been using his own Toshiba, that runs Vista and is slow as all hell.
Moral of the story: he should have been used his crappy PC from the beginning, at least all its keys work

(Note: watching him type hurts my soul. When one is used to use both hands to type, and is fast-ish on the keyboard and uses tabs to change fields, watching someone type with only one hand every 2" or so and using the mouse to change fields hurts. So much time wasted 😭)

A home hosted build server for continuous integration is always crap and a blocker for everyone. If you don’t have 5(yes, five) full time admins/devops to support that, forget about building the infrastucture yourself. There are companies whose business is to provide CI as a service, why do you think you can beat them with your crappy Jenkins installation?

I’ve seen a 200 company failing with 2 people. I’ve seen another one completely failing, because the admins didn’t know what CI meant, and a small one failing with 0.5. The only place where it kind of worked used Gitlab.

my employer moved our company to the UAE. we were in a dying and collapsing country. Now we are in a stable and great place to be. We are even paid about double the average salary here.

But...

He now seems to believe we all owe him. so every time a long weekend / holiday comes up he tells us you have a week to deliver X or ur career will be in danger.

I have been living the past 2 months with those continuous threats. In utter anxiety over possibly losing a job i love because of him.

Before the weekend started he tagged us and said you have 48 hours to fix X. and here i am on a weekend working 10 hours a day as a result.

But i have been pulling 2 day shifts in one day. spending nights, weekends and holidays working on the project he wants fixed. and he still seems very angry at me and my team all the time. very unappreciative. and just very hurtful.

im just scared shitless because i have a family i support and have Just moved to a new country and paid thousands of dollars to rent and furnish my new place. If i get fired now i would be ruined...

!rant
For the past weeks I've been reading about continuous integration and today I finally decide to dive into Gitlab-CI. After a couple hours I finally managed to have a working pipeline for one of my project using a self-hosted runner and holly shit that was satisfying. Now I just don't see myself not using this in the future

Microsoft: Do you know dateadd from SQL?
Devs: Yes of course.
Microsoft: Well you can also do that in our brilliant DAX language.
Devs: Ohhhhhh.
Microsoft: It only works with a special date table, though, and it doesn't work with a non-continuous set of dates, so please don't filter too much.
Devs: Please what??? 🤯😵

Why Microsoft, why?

I don't understand how I/O streams work. I mean as a userspace developer i saw the stdin/stdout streams as magical objects that i could read or output infinetely in a continuous way, without caring how much data i write or read (ok, not entirely true because overflows)... But now i'm making an os kernel and i really don't know how i'll implement them..... :(

The term 'continuous rot' just came to mind as something like this: A lone/sole developer is hired to implement a solution but dispite the illusional good intent shared by everyone at the beginning, time constrains will soon come into play and the code deteriorates at a rapid pace until the developer can't handle it anymore... But someone else comes to continue the work... And the rot continues... And once again... And again...again....

Anyone?

Im beginning to think im stuck in an infinite loop of learning. This fucking bullshit never stops. I just continuously keep learning new shit and the more shit i learn the more i realize how much bullshit i still have to learn

It creates an illusion as if i know nothing

Just when i thought i see the end of the horizon and reach it only then i realize it just keeps on going into oblivion, as a sphere

Its like im trying to catch and find a corner of a sphere

There aint none

Its pointless

Is it also pointless to keep learning like this?

Perhaps this whole existence is pointless

Real talk now whats the point of existence bro

No matter what you do or dont do it doesnt matter

No matter if you're successful or not it doesnt matter

No matter if you learn all the bullshit in the world you're still gonna die and it wont matter

No matter how much i learn, it still and will always appear as if its not enough to these shitface recruiters and companies, to them it doesnt matter

Nothing matters. Everything is empty and meaningless. The entire life itself is. I dont value life. I dont care if i live or die. I feel no joy when i succeed and i feel no sadness when i fail

The tiny little bit of joy or success cannot outweight the years of sadness depression emptiness and failure the life has dumped onto me in spite of my hard work and continuous learning

Hhhhhhhhhhhhhhhhhh

Just 3 letters I'm trying to replace with 2:
FTP => CD

Guys, about Continuous Integration with SVN, what is the best approach? Thank you

So we now do continuous deployment to a development environment. Once a PR gets merged it gets deployed there. We then have to manually deploy to staging every so often.

We did this because QA wined that the Dev was constantly breaking Staging, when we contentiously deployed to that.

So now we have a staging instance that is always behind. Which isn't big deal, because its supposed to be stable right?

Well now the stupid fucking QA team is always making mountains of tickets and noise for stuff that is already fixed on the development instance.

Fucking shit that they message me about, or have to call me about. "Hey let me tell me about this thing I found." And then I'm like I already fixed that thing last week.

So it seems to be wasting everyone time to not just CDCI into staging. I have to wait weeks to retest my bugs on staging. To make sure that some other stupid fuckeshir on my team didn't undo or break my fucking fix. Shit keeps getting kicked out of QA Review. Fuck. lol.

Then there like I can update the thing on the database through the front end tool. Well tough shit buddy, your going to have to wait a week unti next staging deployment to see if that tool is fixed. This is your fault for fucking up our pure CDCI with your ideas. Now everything takes longer for everyody.

To sum things up. Some dumb bug makes it into the manual staging deployment and gets fixed an hour later. Doesn't get deployed until next fucking week. QA makes a bunch of noise about it. A thing that is fixed and in the pipe-line.

Also a dumb fucking bug will make it into staging, lets say a critical front-end back office tool that needs to send numbers to the backend, they send a fucking string instead of a number and break it. Now we have to redeploy the tool and backend to staging because there related. Then if we deploy backend we have to deploy the client facing site too. since it also depends on backend.
Its a fucking hassle.

Now if the fucking DevOps guy could do his job, and make a god-damn deploy button for all the staging servers that would be great.

Any advice on how to deal with gatekeeping developers? How to deal with red tape?

I work with people that are resistant to code and process change. Continuous pedantic pushback on nearly anything; one raised a fuss over metrics not being satisfactory at a 5% threshold for alerting stating that 4.99% metrics variance wouldn't trigger an alert.

It's genuinely as though my coworkers are all scared of code based on the way they behave. They don't seem to code very often either.

I'm someone that codes quickly but I have to constantly write proposals for quite literally any change to the codebase. Even IF there were issues we could always rollback (and even then we have metrics, alerts, canary rollouts, feature flags, etc etc). As a quick aside, my pace isn't related to the pushback nor experience/skill level. Just affects my morale and mental heth to be blocked.

I can communicate effectively and I try to be as clear as possible in my proposals but this is absolutely driving me up the wall and killing my motivation.

This is a faang-level company and I would've expected better.

Any advice on how to best navigate this? Is this the norm???

I need some advice to avoid stressing myself out. I'm in a situation where I feel stuck between a rock and a hard place at work, and it feels like there's no one to turn to. This is a long one, because context is needed.

I've been working on a fairly big CMS based website for a few years that's turned into multiple solutions that I'm more or less responsible for. During that time I've been optimizing the code base with proper design patterns, setting up continuous delivery, updating packaging etc. because I care that the next developer can quickly grasp what's going on, should they take over the project in the future. During that time I've been accused of over-engineering, which to an extent is true. It's something I've gotten a lot better at over the years, but I'm only human and error prone, so sometimes that's just how it is.

Anyways, after a few years of working on the project I get a new colleague that's going to help me on my CMS projects. It doesn't take long for me to realize that their code style is a mess. Inconsistent line breaks and naming conventions, really god awful anti-pattern code. There's no attempt to mimic the code style I've been using throughout the project, it's just complete chaos. The code "works", although it's not something I'd call production code. But they're new and learning, so I just sort of deal with it and remain patient, pointing out where they could optimize their code, teaching them basic object oriented design patterns like... just using freaking objects once in a while.

Fast forward a few years until now. They've learned nothing. Every time I read their code it's the same mess it's always been.

Concrete example: a part of the project uses Vue to render some common components in the frontend. Looking through the code, there is currently *no* attempt to include any air between functions, or any part of the code for that matter. Everything gets transpiled and minified so there's absolutely NO REASON to "compress" the code like this. Furthermore, they have often directly manipulated the DOM from the JavaScript code rather than rendering the component based on the model state. Completely rendering the use of Vue pointless.

And this is just the frontend part of the code. The backend is often orders of magnitude worse. They will - COMPLETELY RANDOMLY - sometimes leave in 5-10 lines of whitespace for no discernable reason. It frustrates me to no end. I keep asking them to verify their staged changes before every commit, but nothing changes. They also blatantly copy/paste bits of my code to other components without thinking about what they do. So I'll have this random bit of backend code that injects 3-5 dependencies there's simply no reason for and aren't being used. When I ask why they put them there I simply get a “I don't know, I just did it like you did it”.

I simply cannot trust this person to write production code, and the more I let them take over things, the more the technical debt we accumulate. I have talked to my boss about this, and things have improved, but nowhere near where I need it to be.

On the other side of this are my project manager and my boss. They, of course, both want me to implement solutions with low estimates, and as fast and simply as possible. Which would be fine if I wasn't the only person fighting against this technical debt on my team. Add in the fact that specs are oftentimes VERY implicit, so I'm stuck guessing what we actually need and having to constantly ask if this or that feature should exist.

And then, out of nowhere, I get assigned a another project after some colleague quits, during a time I’m already overbooked. The project is very complex and I'm expected to give estimates on tasks that would take me several hours just to research.

I'm super stressed and have no one I can turn to for help, hence this post. I haven't put the people in this post in the best light, but they're honestly good people that I genuinely like. I just want to write good code, but it's like I have to fight for my right to do it.

3 hours later I discover why my unset destroyed our json.

"When encoding an array, if the keys are not a continuous numeric sequence starting from 0, all keys are encoded as strings, and specified explicitly for each key-value pair."

Thanks obama.

Auto Login feature enables itself when a certain config flag is present - the app will login as an admin without requiring username or password.

I pray to the Continuous Deployment monsters that the config setting never gets copied to production by mistake.

I have a spare, fully functioning i5 CPU with 8GBs of RAM.

I was thinking of converting it into a continuous integration server with GitLab.

What would you guys do with it?

!rant
What a great feeling when you push a big bunch of changes and CI makes it over the biggest hurdle (lint and test). Time for a fresh cup o' coffee while the build finishes.

instant coffee isn't reeeeally instant, is it 🤔? I guess depends on when you start timing and whether time is continuous or stops at planck's constant or so

This kind of question has been asked before.

Is coding on mobile actually a plausible idea or should I just leave the idea. I am mostly doing some c# with .net core. It is mostly console apps

I wont have access to my laptop for quite a while because I spent quite a lot of my free time on my laptop. Also me being dumb refused their offer of 1 hour of continuous access to the laptop every day.

I finally understand it. Its all about adaptability. The body and the subconsciouses mind is in a continuous adaptation to the environment it lives in. That explains why we always strive for new, better and cooler things, why we never are satisfied with what we have.

Be happy in the current position you are in, be grateful for simply living. It sounds like I'm on drugs or something, but we take such things for granted, appreciate and embrace what you have.

The integration of technologies project I have this year. Not yet finished but I already learned a lot of very cool stuff.
First, I learned a new programming language + framework (Ruby on Rails)
Second, for the first time, I implemented a continuous deployment pipeline with Capistrano and Travis ci.
Third, first time I programmed a Restful API.

And more cool stuff coming up ! :D

I freaking love learning !

If your manager asks you to write a raw algorithm based on raw data in order to properly structure, sort and filter that data, how long do you take on average to complete said task?

Example:
Here's a text file with a bunch of continuous data like: john doe 5555 my street 123 karen wiscott 12347 her street 22 peter wright

..and then you first have to start identifying boundaries for each data entry (which is a task on its own, with comparators and shit), solve its bugs.. then you have to make sure it's properly getting sorted.. sort those bugs.. Yeah, it just takes a long time for me to figure all that out.

It takes me 4-5 days on average since I'm a junior but managers expect it to only take 1-4 hours.. madness..

please i need your advice :)

I need to reform a service that offers legal advice and thus serves around 5000 Microsoft Word legal advice documents for the end user and every year there are 200 more documents created and published and changed manually.

So i had this idea to use a CMS, Git and continuous integration for

- automatic spell checking
- automatic assigning the copy text to translation bureaus, and get translations back.
- version control the texts and translations.
- document generation in multiple formats
- checking the text flow in the document (no overflown text)
- Checking for accessibility for the handy caped
- Deploying it on the Website

Do you think this is feasible? Can something that was made for code also be used to handle copy text documents? In my head this would save so much work but i'm no expert in CI/CD.
Thank you for your advice!

If you compare a software developer's job with another, let's say a doctor or a lawyer, the former doesn't require mastery and there is continuous chase on fast changing version numbers or an entire platform coming out. Former innovates without question and gets burned out in the process. While the latter demands mastery of certain fields and the specialization isn't diverse enough compared to former. Yet the pay for latter might be higher. What are the pros and cons have you felt as a developer and how do you cope to address it internally? Is it just the thrill and excitement of new things coming out? What fulfillment do we get aside from the satisfaction of clean code, unit test and successful deployments? How much impact have we really given? And is there a place for developers to final settle down? Don't get me wrong; I won't stop until death probably but I hope adulting responsibilites won't make us break.

Does the company you work at have a CI/CD pipeline (Continuous Integration/Continuous Delivery, e.g. with Octopus Deploy)?

Sometimes it surprises me how many companies don't have this..

Murphy's Law of Continuous Integration: If your code finally unbreaks the build, then the build will break because the PGP Key server didn't respond in time.

Fuck Fuck Fuck workingtime 8:00am 10:30pm

15 days of continuous work without breaks

Most of the time waiting for someone else to debug the program

I work on a larger team where we do continuous integration so there is a high probability people will be working on the same files for different features. As a result, one of the best feelings is grabbing the latest files and not having to diff first thing in the morning.

Does being dictate consciousness or does consciousness dictate being?

In this layman form, the answer is undefined. But let's dig deeper.

The layman form doesn't account for the difference between discrete and continuous. Without that difference, the paradox of Achilles and the Tortoise can't be solved. Yes, it took from ancient Greeks up until 17th century to solve it, introducing that distinction.

Both being and consciousness are discrete entities. This way, technically being was the first, because you were born to it. But when you became self-aware, your consciousness started to dictate being, and not the other way around.

If being truly fully dictate consciousness, then consciousness can be cut away by Occam's razor. In the same way, your parents are technically the reason you exist at all, but if that fact fully dictated who you are, then _you_ could be cut away in similar fashion.

Contrary to that, if consciousness fully dictated being all the time, being could be cut away too.

So, yes, being created your consciousness. But later, when your consciousness was created, it started to dictate being. This is the only way they're both can't be cut and are aligned with the timeline.

Yesterday we had discussion on with developers about continuous deployment. When I asked one of the senior developers why they can't uncommit what commits you made to integration branch and which led to integration test failures. He said it's against the basic philosophy of git to uncommit... I don't know how git works...but seriously you can't use previous version of code or can't uncommit??

Dev ranting about US foreign policy. Trigger warning!

US has a track record of funding the bloodiest regimes, funding terrorists and then using it to create problems for neighbouring regions. I'll tell you step by step how that's done.

1. Look for opposition in non-aligned/sovereign or even-allied country but opposing viewpoints. (Remember spying on German chancellor, Merkel?)
2. Covertly provide them support (providing fundings, potentially arming them).
3. Slow media propaganda, claim the country is undemocratic.
4. Opposition might stir things up.
5. Paint the current leadership in the sovereign country same as Hitler.
6. Continuous bombardment of propaganda using MSM like CNN, MSNBC, Fox, France24, or bribed insiders.
7. Once the regime is finally toppled, black out the media, and see deals can be made with the opposition (Oil, Military bases, or whatever)
8. Reality: these countries are worse now, but no media coverage because exploitation is complete and no-one gives a shit about democracy or whatever. (If you watch few videos about Iraq, Libya their own people says they shouldn't have toppled their leader.).

What is the best approach for Continuous Integration / Continuous Delivery/Deployment? I'm using SVN as code repository and I need to identify the files that goes to Test/QA env. and the ones that goes do Prod env. (by Commit message or something else) via sFTP.
Any help would be appreciated. Already tested Jenkins, GoCD and Jetbrains Teamcity.

How did you get the people from Info Security and Compliance on board this continuous delivery thing ?

I am being asked to run antivirus scans on my own code and binaries as part of build.

Is this common practice? Am I missing something?

I am going to deploy stuff on Azure PaaS. I can understand having malware scan agent on azure VMs scanning the infra, but this?

Hi everyone, I’m trying to wrap my head around dev ops but struggling with the whole continuous integration workflow. From my understanding it goes something like the following:
1. pushing a change to some repository (git)
2. Some tool (Jenkins) tries to build it and if it’s succeed, creates a image /container (docker).

These containers are hosted on some cloud service (aws)

Some workflow, walkthrough, or examples would be very appreciate.

I've been thinking about ways to improve my workflow for my personal projects.

I'm getting to grips with continuous integration and deployment etc, but I want to also automate, or at least semi automate my changeling generation.

I don't like using any sort of gitlog shenanigans, and I quite like the girls way of doing it.

I.e you run a script which generates a yaml file with your changeling info in, and then all the files are written into the changelog.md file.

How do you guys handle the generation of your changelings?

Guys, about Continuous Integration/Delivery using SVN as repo... What is the best approach? It would be nice if it could trigger the files that should come to prod by commit message or something like that...

Thank you.

I work in a BPO. I like my current assigned foreign client with continuous work and my BPO company wants me to assign to a local client to start from scratch again.

I invested time and effort for this hard foreign client then after all that they will replace me in the future with other employee? Quite sad 😞

Question directed to devs who know a bit about setting up middle sized architecture.

Prestory: Joined into development of a middle sized online game. Figured they created a monolith over the last 6 years up to a point where nothing works properly and nothing can be changed without wrecking the whole system. Figured a monolithic approach isn't such a great idea.

Current Situation: In a different, same scale online game development team, game itself working but team is struggling with architecture.
My job is to come up with an approach on how to set up masterserver/matchmaking/database etc. Reading through various articles about common principles (SOLID etc.), i figured that a microservice+event-/servicebus architecture may work for that kind of project.

The idea would be to have a global interface in which microservices can be hooked. So a client registers to a client handler on startup, then starts to queue for a game, the client handler throws an event on the bus to register the user to matchmaking. The matchmaker happens to listen to those events (Observer Pattern) and adds him to matchmaking, when a match is found it throws an event on the bus to connect the user to the server, etc. One can easily imagine a banhandler throwing in a veto to cancel such an action, metrics and logging is fairly simple to add (just another service listening to all events), additionally Continuous Delivery, FRP and such are also beneficial advantages and it is said to scale well.

The question is, would you do the same, is there maybe something i might be overlooking? Do you have better ideas?
Keep in mind that we are not too experienced and are bound to different languages (python, C++ and java mostly) and are a small (4 Devs) Team with different strengths.

Thank you for your feedback and criticism!

Fastlane st the moment... so nice working with that toolbox for Continuous Delivery #wk56