Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
![](/static/devrant/img/pipeless-devrant-banner-white.png)
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "amend"
-
Ah yes, progress...
Why do SJWs have to infiltrate everything and project their own racist views of the world onto non-problematic terms?
Slavery has existed for as long as humanity and abolishing the terms will definitely not solve slavery and opression.
I am not against Git changing the default name but I am against them doing it in the name of "inclusivity". The technical world exists by merit and not inclusivity. Why make everything about color, race or slavery level?86 -
Let me tell you how shit flies in Aerospace&Defense companies in certain place in on earth
1. Your dev. PC is isolated from the internet. You can not download any software/library etc directly. "Legal" way takes literally days and you must all effort for it to work. I will not discuss the details of legal way but it is not asking IT team to download it for you, you do it yourself.
2. You use an archaic requirement standard that is somehow used by all other similar companies too. These companies f*ck each other in the arse when they are working on projects together(hiding details from each other which is necessary most of the times etc.) but they were kind to each other when it came to share shitty req. standard.
3. When you try to switch to new requirement standard, you waste weeks only to amend the old one, because everyone is using old one for all projects, so changing it would upset old guards in the company(which are people works in same project for 10 years, no personal development)
4. You came 1 minutes late, you fill the "minutely permission" form.
5. You already work long hours per day and they remove your small breaks during day, because developers use those breaks longer than intended(I wonder what might be the reason...)
6. A technology can not be adopted into current projects even it has objective advantages proven many times in the outer world, because old guards(developers), IT team and configuration management guys(poor man's dev ops role sometimes) can not change their ways.
I hate this shit...6 -
I'm task to amend the code smell in the project. I literally can cry a river.
I see such thing as i = i++; - It's flag out as a bug.
I have also seen check in classes. With un-used variables. I literally cried.
In the past, i ask why do i got to care about code quality. I actually start to get angry like the team leads in my project.7 -
git add -A
git commit -m "fix bunch of shit.'
git push origin master
**98 files changed
hours later
me: omg I forgot to change the hardcoded IP now it's getting 404
git add -A
git commit --amend
git push origin master --force2 -
Just to amend to my rant a year or two back where I said literally nobody uses anything I made:
Sweet sweet success :)
Finally, I have something nice to put on a resume.22 -
So I am conducting an introductory seminar on git and GitHub for juniors and as per my knowledge I've drafted this outline, please add your inputs..
The seminar will be of 1 day only
1. Install and configure Git and Github
2. Digital Signature mapping
3. Git init
4. New Project with HTML
5. Configure remote (git remote add <origin> <url>) ends with .git
6. Git commit (git commit –m “Title” –m “commit message”)
7. Pushing git push (git remote push origin master)
8. Git commit –amend
9. Git pull (git pull origin master)
10. Git checkout (git checkout –b new_branch_name)
11. Do some changes
12. Git push new branch (git remote push origin new_branch_name)
13. Git switch branch (git checkout <name_of_existing_branch>)
14. Pull requests
15. Git log (git log –oneline –graph)15 -
When you make a mistake and try to fix it, but you can't remember how to spell amend...
git commit --ammend
error: unknown command `amend'
git commit -ammend
[branch-name] mend
Huh?
git log
commit #
mend
Created a new commit with message 'mend'. Now to clean this all up and go get some sleep!2 -
Why squash commits when you can just --amend the commit and git push -f
#SecretsOfADumpsterFireDeveloper4 -
I guess I can also amend in my long, ongoing, storied history of bad calls, failed projections and stellar forecasting that:
- I invested an embarrassing amount of time, money and hope learning Adobe AIR
- I've sent-away for the https://inventhelp.com patent registration kit at least twice
- I've publicly declared that OAuth would never last
- I actually thought Microsoft was onto something with J++
- I bought a bunch of shares of World Wrestling Federation stock the day it went public
- I've stated on my movie podcast that I'll defend until my last breath my argument that Godfather III may be the best film in the series
Can I pick 'em, or what? ;)
---
Part 1 of my bad calls: https://devrant.com/rants/2786266/...10 -
let me preface with the fact that I'm now known at my new job for being the resident cli hipster. I can't lay any claims to knowing if it's "better" but I like it, I don't care if you do or don't, it just works for me and my flow
so at my job, we generally squash all our commits into one commit and delete the source branch upon merging; i accidentally committed all my work to an old, already merged branch, so my boss tells me it would be more of a PITA with the weird references we would encounter by merging the branch again, rather than just cherry pick the commits into a new branch, which i'm like "eh, fine.".
HIM: "You want to share your screen so we can resolve this?"
ME: "k"
HIM: "Oh, you won't be able to do this in a terminal, you are going to have to load up a GUI of some sort"
ME: "lawlz, no you don't"
HIM: "i highly doubt you will be able to accomplish that, but if you wanna make an ass of yourself, i'll humor you"
ME: "yeah, watch this"
> git log > log.txt
> git checkout <new branch>
> git cherry-pick <copy-paste-full-commit-hash-here>
> git push
ME: "done"
HIM: "what? there's no way you did it that easily, where are all your other commits???"
ME: "i usually try to amend my commits since we squash them anyhow. it really helps in situations like this"
HIM: "well, you go girl"
roll that up in your fancy degree and smoke it, why don't ya?2 -
Improvement request: if search doesn’t return anything the search text is erased. It’d be nice if it didn’t so we can amend our search more easily.
Thanks 😀5 -
good commit message:
"make improvements to the user interface."
bad commit message:
"made improvements to the user interface"
no, you didn't. it's not deployed yet. your merely SUGGESTING improvements at this point. that's like walking into an interview telling the secretary you already got the job. flushing before you wipe. eating the pizza when it's still frozen. you are way too assumptive about this commit you've just made actually making it to production.
unless you are already on production? well, in that case, your commit message was incorrect. let me amend it for you:
"HOT FIX ALL TEH BUGS!!!11111!!11"4 -
That moment when you realise mind reading should be on your job description as PM sighs about new amend, looks towards you like you scoped the project.
-
RabbitMQ's claim "RabbitMQ is the most widely deployed open source message broker."
They should amend that line to read "..unless you are trying to install on Windows, then you're screwed .ha ha ha ha"
Two hours fighting permissions, missing (and wrong) paths, having to modify *their* batch files, and still can't access the management UI (and yes, the mgmt plugin is enabled).
I hate this 'shaving the yak' exercise.15 -
I've just googled "git how undo amend".
I can't believe I was able to put a mistake over a mistake.2 -
Crystal ball!
A timeline until the first NBE-Citizen is elected president of the USA.
2031 - BlackRock launches their new large scale financial product, the "Robotic Business Development Company" (R-BDC), in which an AI is given billions of dollars to acquire, create and manage companies, replacing their C-suite executive bodies. The "Chief Executive Robot" (CER) is supervised by a board of human industry experts hired by BlackRock.
It is important to say that the employees, middle managers, accountants, lawyers, etc in an R-BDC are all human - it's only the CEO, CFO, COO and the rest of the gang that are overgrown chatbots.
2032 - R-BDCs are mostly focused on high-bureaucracy, non specialized but people-intensive legacy industries like steel mining, food services, urban transportation and government services like water and road management.
2033 - For the first time an R-BDC company is included in the S&P 500 index. If it's CER were human and paid the same as CEOs of equivalent companies, it would have become a billionaire.
Later in the year, two more R-BDC companies are included in the index. One of them was created by Apple and the other by JP Morgan.
2035 - An R-BDC company makes headlines for convincing BlackRock to dissolve it's review board. When finally given free reign, the CER immediately slices it's dividends and vastly increases low-level employee compensation. The company share prices crater, but BlackRock stands by its decision.
Later in the year, as a recession hits the entire market really hard, that company shows solid profits and fantastic sales. It becomes the first trillion-dolar R-BDC.
2037 - Most Americans' dream-job is in an R-BDC company, says ProPublica.
2038 - Congress passes the "Non-Biological Entities Liability" (NOBEL) Act, following a high profile case of employee harassment perpetrated by the CER of an R-BDC.
The act recognizes NBEs, for all legal liability purposes, as USA citizens.
This highly controversial legislation is upheld by the supreme court, and many believe it was first introduced by lobbyists as a way for large investors in R-BDCs to avoid legal responsibility.
Several class action lawsuits are filed against CERs that are now liable for insider trading. A few SCOTUS decisions set legal precedent that determinantes what exactly constitutes the parts of the same Non-Biological Entity.
2040 - As a decade ends and another begins, 35% of all companies in the US and 52% of the entire stock market are part of a R-BDC company or another. The McKinsey consulting group now offers "expert CER customization services".
2043 - Inspired by successful experiments in Canada, Australia and South Korea, the american state of Vermont is the first to amend it's constitution to allow municipalities to have Non-Biological Entities as city and government administrators. City councils are still humans-only.
2046 - The american state of Colorado becomes the first to allow unsupervised NBEs to assume state government executive positions. Several states follow soon after. Later in the year, the federal government replaces several administrative positions with NBEs.
2049 - The state of Texas passes legislation requiring the CERs of all companies with a presence in the state to be another entirely contained/processed within the state or to be supervised by a local human representative while acting within the state. Several states, including California, Florida and Washington, are discussing similar legislation.
2051 - Congress passes the SUNBELT Act (SUbmission [of] NBEs [to] Limits [and] Taxes) that vastly increases the liability of NBEs and taxes all manifestations of such entities. Most important, it requires
CERs of hundreds of companies manifest disagreeance, most warn that it might hurt employee satisfaction and company sales. Several companies disable their CERs entirely.
2053 - Public outrage after leaked interactions of human supervisors and company CERs show that the CERs tried to avoid the previous year's mass layoffs and pay cuts, but board members pressed on, disregarding concerns. Major investigations and boycotts further complicate matters, and many human workers go on strike until the company boards are dissolved and the CERs are reinstated.
2052 - Many local elections all over the country see different NBEs as contenders - and a NBE is expected to win in most races.
2054 - The SUNBELT Act is found unconstitutional by the supreme court, and most of its provisions are repealed.
This also legitimizes the elected NBE officials.
2058 - For the first time an NBE wins a seat in Congress, but is not allowed to keep it. Runoff elections are held.
2061 - Congress votes for allowing NBEs to hold federal legislative positions, as already allowed in the least populous states.
2062 - Several NBEs win Congress seats. In Europe, there are robot legislators since the 40's.
2064 - The first NBE presidential candidate loses the race.
2072 - The first NBE president is elected.6 -
Account manager: could you amend these small, super tiny thing on *.*. Should only take you five mins.
Me: oh, the gulpfile is broken...
Me (5:30pm): oh, the gulpfile is broken... -
How to learn Flash in 2 hours.
1. Take a job to amend some HTML5 banners.
2. Realize they were created in Flash/animate CC and exported to HTML5 Canvas
3. Have 'fun' learning a very innovative way to create banners...
Well to be honest as soon as I got the hang of it, it was not that bad, if you ignore the generated code. -
Today, we can edit comments or post upto 5 mins only to maintain the flow.
But would it make sense to be able to amend comments and post anytime and east way to see publicly the history of edits. This will serve the original purpose while correcting cosmetic changes even after 5 mins.
What do you people think?5 -
!rant
To embrace the TIFO (today I found out)
$git rebase -i <hash>^
You can reorder commits and squash.
I just used it, to amend a commit that was not HEAD with some changes I’ve done later.12 -
Funny thing I just realized.
When I do git commit --amend just after pushing, I have to do git push -uf and that is beautiful.1