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
Get a devDuck
Rubber duck debugging has never been so cute! Get your favorite coding language devDuck
Buy Now
-
Happy Thanksgiving! Thank you for waiting for this new release of avatar items! We have new pets, new computers, new eye wear, some fun shirts and a special treat for our #1 ranter @linuxxx. The required ++ pts for these are a little higher than normal to reward the dedicated people who have helped support and build this community over the last few years. Thank you all!
39 -
Alright fuck it, let's release this fucker!
https://lynkz.me is the main domain. The interface is *usable* and nothing more than that. I'll invest more time in that soon but for now, hey, it works.
Api is located at https://api.lynkz.me.
Documentation for this (literally some echoes to the screen but it contains the needed information for now) is at that api url.
Found a bug or a security vulnerability? Please let me know!
Yeah I use mariadb but sql injection is luckily not possible due to quite some sanitization ;)
WARNING: if you make a shortened url and forget the delete key, you won't be able to delete it.
Let's see how this goes 😅115 -
I recently suggested we start giving our releases code names, so that they accurately describe our client's change requests.
The idea was quickly rejected after I suggested the first two code names be "#yolo" and "Leeroy Jenkins"
Apparently I'm the only one that thought it was funny.8 -
Spent most of the day debugging issues with a new release. Logging tool was saying we were getting HTTP 400’s and 500’s from the backend. Couldn’t figure it out.
Eventually found the backend sometimes sends down successful responses but with statusCode 500 for no reason what so ever. Got so annoyed ... but said the 400’s must be us so can’t blame them for everything.
Turns out backend also sometimes does the opposite. Sends down errors with HTTP 200’s. A junior app Dev was apparently so annoyed that backend wouldn’t fix it, that he wrote code to parse the response, if it contained an error, re-wrote the statusCode to 400 and then passed the response up to the next layer. He never documented it before he left.
Saving the best part for last. Backend says their code is fine, it must be one of the other layers (load balancers, proxies etc) managed by one of the other teams in the company ... we didn’t contact any of these teams, no no no, that would require effort. No we’ve just blamed them privately and that’s that.
#successfulRelease4 -
I might start naming our release tags as Kraken-x.x
That way on launch day I can legit order the team to RELEASE THE KRAKEN.2 -
A client obsessed with *security* won’t give us access to the server that hosts the website we built.
Code release involves building templates, compressing the changed files into a zip folder, and emailing them to the client with instructions on where the changed files go8 -
Never, ever, ever, release on a Friday. But.....
if you do.
Add this step as part of your production push process.
2 -
Complains why the app is not done yet ...
Because you fucking keep coming up with new features and ask us to implement them immediately !!!??2 -
I am puching myself over this one.. This made it into the official release. And this is one of the public screen shots that I saved to my phone from my devBlog.
How did I not see this??
.. "SizeTest" ..
24 -
One of the better filler release notes I guess. Not as good as Slack or Discord but still better than Google.
1 -
So... the US Govt. just released a shit ton of files on JFK assasination, and being the data hoarder that I am, I promptly requested a bulk download link...
Apparently I underestimated the "shit ton" part, coz each of these files is around 2.4GBs... and I dont have the data to download them :-D :-D
FML
30 -
Oh, well, of course ...
I thoroughly enjoy that both Google apps have different bullet point styles.
1 -
Backend: Sorry the fix we had isn't going to work. Turns out app is sending an "undelivered" status after you call the API where you claimed we had an issue. This is in fact the cause, please address it.
Me: We do not have an "undelivered" status anywhere in our codebase. We do not do this.
Backend: *CC product* turns out this issue is only affecting 0.1% of users, its very minimal. Lets push ahead with the release.
Product: Ok, lets go live.
Me: ... ... ... we all just gonna ignore that "undelivered" bullshit? ... ok ... very stable release, here we go.3 -
My biggest mistake in my life.
Boss: So when are you gonna finish this?
Me: I'll finish it today,
Me: Finishes task and submits pull request
- The Next Day-
Team Lead: Oh bro you gotta put this on a separate file, this change this too, and that, don't use that shit use this instead, oh and yeah, you can probally use this 'totally awesome typescript decorator' here for that.
Me: Refactors code intensely
Boss: You said this going to be finished yesterday
Me: FML13 -
That moment when you had a good weekend and it is Monday again.
You log in to your work PC and see 15 emails... There goes my Monday again.
And 12 of those turn out to be congratulations on the recent release 😥3 -
Me: "I've just released a new app"
Everyone I know: "I've got a great idea for an app.... I'll give you 10%"
Every. Single. Time. -
Successfully launched after 9 hours of bug fixing and patching. Let's se what will happen tomorrow. It's now 01.56, and I wanna sleep... Good night.5
-
You know it's going to be an interesting day when you see a release note containing "migration" and "cross your fingers" in the same sentence 😅2
-
My raspberry Pi finally arrived ☺️! Now i just have to set it up... Any advice on what linux distro i should put on it? (i will use it as a NAS, torrent server and pi hole)
7 -
To all of you that is saying Friday release is horrible, you have no idea how bad Monday release is :(2
-
Hello, world!
Soo.. I am half way done with Pre-Release 10!
Woohoo!
However.. The update log is already as long as the full update log for the last update.. Which was twice as long as the log for the update before..
I'm Starting to notice a pattern.. XD
This is all good and well, but I feel as if I'm overworking myself. I'm getting stressed out, and I'm not spending near as much time with my girlfriend. 3: But, I'm having fun. I'm genuinely enjoying myself, and I'm making a ton of progress in such a short amount of time. I also have a new team member!
Idk.. I haven't done anything the past two days really. Work nor spending time with my girlfriend. I'm stressed, and I'm not sure what I should do. I'm sooper modivated to keep working, but I feel that my situation will only get worse.
---
Because I'm sure some of you will be interested ('cause my game is very popular in this community <3), here is the update list so-far. Do note that this is not the final list, and things will be added, and may be removed.
As you can see below, this update is mostly focussed around API's. Specifically Modding, and the new FileSystem. On top of this, I will *try* and tinker with the official Patreon API for Java and see if I can't intergrate that into my game. I'll also work on a ModManager, but I'm not sure if either of these will make it into this release. I also have plans for new Apps and Commands for this release, as well as working and polishing up existing Apps and Commands.
---
* Closing the game with X button (and other ways) now also calls preExitTasks()
+ Added AddonLoader. It's literally a Mod-Loader. (Your welcome :3) A tutorial coming soon, but just know that it's standard Java codeing and you simply need to drop the mod.jar into the game's addons/ directory.
++ Added "API" - This is a bunch of methods that are added for the Mods to use. These Methods likely wouldn't of been added othewise.
+ Added in-game FileSystems (Folder, files..)
++ Added FileNavigator API for traversing the in-game FileSystems
* Fixed a major bug with the "debug" command where you could no longer run any commands after enabling debug mode.
+ Added GameSave creation
+ Added System creation
+ New Save + localsystem are generated on startup
++ Added WindowBuilder API for creating Apps. This makes creating Apps much, much simpler, and is intended for not only us, but use in Mods.
* We re-wrote the Console Class from scratch, and turned it into an API for creating custom Terminal Apps. (Commands are now created using the Command Class and are then passed to Console and registered as either a Local or Global command)
++ Added Command API for creating commands. These commands execute Java code, much like a JavaFX Button would, on each call. You also get everything after the first [space] of the command that was passed, as a String.
* Re-wrote ALL previously implimented Apps.
* Re-wrote ALL previously implimented Commands.
+ Added "debugtest" command to test debug mode. (This just prints a totally boring random message, and you shouldn't try it.) [Note: This "command will not exist" when debug mode is false.]
+ Added "cd" command. ("cd ~" "cd .." "cd /home/folder" "cd etc" "cd /")
+ Added "cat" command. ("cat file" "cat /folder/file")
+ Added "mkdir" command.
+ Added "rm" command.
+ Added "dir" command.
If you're new and you have no clue what I'm talking about, here's the info page: https://trello.com/b/0bH2SjQf2 -
We started a project in January for which I was the sole developer, to automate tedious interaction with a vendor's ticketing system. We have a storage environment with about 400,000 commodity disks attached(for this vendor-- there are other vendors too), in sites around the US and Canada. With a weekly failure rate of about 0.0005%, that means about 200 disks a week need to be replaced.
This work-- hardware investigation through storage appliance frontends, internal ticket creation, external ticket creation, watching the external ticket for updates to include in our internal ticket --was all manual, and for around 200 issues a week, it was done by one guy for two years. He was hopelessly behind. This is all automated now, and this morning, I pushed this automation from dev/test to production.
It feels great to see your work helping people around you.8 -
Laying in bed with a huge headache while the alpha release is at Sunday (own company) and the main feature isn't even written yet 😫 fml hard.5
-
Want to travel to the future? Release on a Friday. You'll be experiencing your weekend as if it were Monday.1
-
I'm pretty stoked on the future release of SemicolonJS... It will change webDev as we know it. 😎
http://semicolonjs.com
@dfox, @trogus when is the release?8 -
Finally we release November release in December. All developers united against sneaky bugs.
God bless (drawing by me)
2 -
I'm actually a Dev, mostly just a shell scripter who needs to support 500 servers which run our applications. I install the new versions and check whatever is wrong if there are customer issues.
One release weekend everything went wrong, Development had to make new builds on the fly with hardly any time for testing.
It took 18 hours with no break.
It was extremely hard to concentrate, but being in the Skype group with everyone and finally getting everything fixed was quite rewarding.
Everyone just opened a beer and we stayed on the call for about 30 more minutes just to relax.
I like our Dev team way better than I like my actual colleagues, who merely mess things up and call me for the smallest thing without even thinking.4 -
How the fuck does someone releases a new version of a package without testing one of the core features of that package?
Spent fucking hours, hitting my head on the wall, only to realize that the latest build they have released has a bug. This is not acceptable :@2 -
That moment when you need badly to go to the toilet and your boss stops you to have a long discussion7
-
Today my boss decided to sit in the same table that his team works (me included) he said that he will take a call and apologized in advance because he will "rant". I didn't get it until I Google it and found the name meaning of this app.
-
Dat moment when your contact person phones you and ask If you delete the whole Release Folder...
YEAH SURE I WAS IT BECAUSE I LIKE TO WORK ON WEEKEND
Fyi: FTP with one user for everyone - harhar stupid bricks -
I spent two days in a row fixing chairs at work because our whole dev team was waiting for issues (which means helping QA team and playtesters testing the whole game).
Just when everyone left and Im standing up to go as well a playtester comes up with a release breaking bug in the handwriting recognition code...
Since this game is build for a charity which will release it in a country at war we cant push the release date.
Guess who is making overtime trying to fix this bug?3 -
So... as a follow-up to my previous rant (https://www.devrant.io/rants/899731)
I happened across this today and started giggling internally.
Enjoy
1 -
So I just found out that another company is launching the same app/website idea as mine...*sigh*
This is not how I was planning on starting my week.
I suppose I need wait and see what they have and improve my app to be better.
Hello devRant, it's good to be back. I hope everyone has a good week.6 -
Finally finished my new app Deep Sleep Fan for iOS. Took 3x as long as I thought it would to develop even though it used a shared code base. Check it out at https://itunes.apple.com/app/...
Now I can go to bed.
3 -
Kivy 1.10.0 just got released for Python 2.7, 3.4, 3.5, 3.6!
Check that fancy thing out =(^.^)=
https://kivy.org
2 -
alias break-ubuntu="do-release-upgrade"
# Only works if new distro is available, otherwise you have to find another way to break ubuntu -
For fucks sake...
If it is a new feature, out of scope for the next release ...
It is OUT OF SCOPE FOR THE NEXT RELEASE, MKAY?????4 -
I have a stupid earworm everytime the release comes closer. "Release candidad" - in the tune of "Feliz navidad".
... I'am sure you tried it out now! 😂2 -
I'm not going outside until like 3 months after they lift the restrictions. I'll let y'all deal with the bugs and crashes and resurgences. I'm not really an early adopter. I'm gonna wait until they release outside 4.2 the stable patch1
-
I am the old famous kiddy here, who just came back days before school exam starts^^
Just to say, I want to ask you all, is it ethical(?) to release a hacking/cheating creation tool for games for educational™ purposes?
I have been making a cheat creation tool called Mysterium, but I am not sure where to use it. I made cheats for some big title games, and reported them to the developers, patched, and got some in game items in return....
Long story short, is it okay to release to the public, or should i release this product to game developers?
Sincerely,
A kid who made cheats since he can't play games well and wanted to get some free items4 -
Flutter 1.0 is announced and they even planned to make Flutter for the web in the form of Hummingbird. Exciting times.5
-
A project I've been a part of for two years finally exited beta this morning! It was so exciting watching it grow and and change into what it is today. The project in question is Storj.io. A decentralized cloud storage. When I first joined the project, literally all it did was create junk files to take up space. Now it is a thriving network storinf over a petabyte of data without the possibility of it ever going offline.8
-
Is there a Developers' Manifesto? Like Agile Manifesto?
If not let's start one here, I'll start:
-We should not be working outside work hours except for exceptional cases, hours != 24/7 && exceptional != 7 days a week
-Death to last minute changes!
-Everyone needs to understand Murphy's Law, it's real!3 -
When someone asks you to test something before pushing a release...releases anyway and tells you any fixes can just go in the next minor release 😫4
-
tl;dr
I am either the most responsible or the biggest idiot in the team
----------
TODAY.. oh boy.. fuck today. Like literally tuck this day and this shit. We ware doing releases for an integration we ware working on for ~1.5 months ... Aaand things went wrong - I guess we didn't make a sacrifice to the release gods - finally at around 8:30pm, being pretty much the last in the whole fucking office after a few last minute fixes I get my skinny ass on my way to grab a Corona and enjoy the public holiday tomorrow ...
Aaaaand I wish that was it, it turns out some things ware forgotten by.. well everyone aaaaand shit doesn't work (ofc ffs, why should it).. I see a slack notif and the feeling of dread gets me a couple of messages back I promise I'll be there in a couple of hours tops..and here I am ranting doing shit covering my desk with "food", hating my fucking self...
Me and the Head of Dev are literally the only ones working ATM... -
When you love and use arch-linux based distros but everyone that does support linux only seems to know about ubuntu...4
-
Going to release the biggest feature I have implemented for Product I work on. Change in more than 150 files and it is very very critical.
Wish me luck..3 -
You know what doesn't bother me?
Not knowing something and letting the concerned know that you don't know a few things. It's perfectly fine, no one knows everything! Totally fine!
What really bothers me is when I ask you a million fucking times if you know git and you fucking lie and mess up the entire branch and boil my blood with senseless commit messages!! And after all this have the audacity to say you know git cause you did a crash course right after I asked you the first time if you know git you lying piece of shit!!!3 -
No! I don’t have any problems that you are deprecating various libs that I used in my software. Just don’t fucking insist that your code is production ready and stable and backward compatible. Please
-
*Screaming Internally* I'm really, REALLY, stressed.
We just entered the final sprint for the finishing of a major project. This is my first "Launch" type achievement since I started working as a programmer(I started almost exactly a year ago)
We have a lot of work done on the project, and it's very clearly near "Completion" but we all know a programmers job is never done.
But specifically I've been thinking about the code i've worked on. I've been at the burnt out phase of the development for a week now, I haven't been getting a lot done, and I can't help but stress that my code is going to be what breaks on launch day and i'm going to get canned or something...
It's not that i'm a bad programmer(at least I don't think) but more or less that I just have been so stressed I think I've made some mistakes, and I think it's going to blow up in my face, and I might lose my job over it.
How do you guys deal with work stress?
1 -
Ran an app release yesterday, adding some new stuff and fixing a few bugs. Was scared this morning because APM didn't have any errors and the app was already in use by half of the userbase.
Turns out it's the most stable release so far! Day's all good again :D -
A client asks me to produce a Release note when publishing a new version, which is more than fair ask, I shall deliver.
Then he asks me questions on the version's feature which are clearly described in the release note, with examples, showing he did not bother to read it..............
...
2 -
My first packages, uploaded to nuget!
A simple neural network library, written in C# (.Net Standard)
Here's a link:
https://nuget.org/profiles/Mitiko233 -
Doesn't work
I hate my life
fuck this shit
Oh I used the wrong list
*jumps from the top of the mountain* -
I’m finishing to test my new sleep app and it seem to work fantastically. I never slept better. Too bad your optimal sleep just can’t always align with your working hours 😬
Release will be this Tuesday4 -
Release on Monday === almost 10h of code today... Though it's just an internal release, so not that serious really. Though it's be fun to have something we've been working on for half a year working decently the first time people actually get to try it... Well, well...
-
I already ranted about this particular designer and his need to mess with the client's server configurations.
Last time he thought it would be a good idea to use cloudflare for the 1 visitor per day website. And because he missed adding some important subdomains, the admin and register page didn't work. And oc the client called me in the night and during work because I destroyed her system.
And the worst is that this designer tries to redesign everything for 3 years. Every time he sends me new stuff, something is missing. Then I write him, that xyz is missing and he doesn't respond for months. Then the client calls me, why I still didn't finish the redesign and I have to discuss with her about the designer missed something. Then the designer writes the next time, that he will send me new stuff because the design will change again.
Oh, and I already wrote, that the designer is the client's boyfriend, so he probably sits beside her when I have to defend myself about not being able to finish the redesign.1 -
So we released to production today (Friday), not my decision.
All pages work fine expect for the one page which I added a new feature.
It worked fine in Chrome and Edge. But after release a customer who requested the feature said it doesn't work for him. Screenshot showed he was using IE.
Horror time.. it was evident that it has to be the changes to the JavaScript I did, but why does the whole page doesn't work.
So I started debugging. Nothing works on that page in IE11, it doesn't even load the fucking script file. Then I dared to change mode to IE10, it actually gave me an error in my script file. The bad IE has actually picked a mistake that other browsers didn't.
So, the mistake is fun part too.
I had the following jQuery (or Jake Weary) call
$.getJSON(
'/url',
{
argA: a, argB, b, argC:c
},
function (){
// did something
}
);
In second argument, I accidentally typed comma instead of colon. Chrome and Edge ran the script perfectly passing all the arguments.IE 11 failed to load script without giving any error and only IE 10 gave an error of expecting a colon.
I do not know which browser to blame.
PS I didn't try in Firefox, safari, etc.2 -
"We are releasing today" - sentence my project/tech manager keep saying for a week now. Of course, we changed few core components during the week - because, why not - and nothing works now.
-
For some reason github is returning 503 on our build servers randomly. And I need to checkout several repositories to build everything successfully. Builds are automatic and I don't want to maintain local mirror. And we wanted to release tomorrow (but were smart enough to promise this week). And on top of everything build takes six hours and sometime fails randomly even without github. But I'm still optimistic - it's Monday after all. We still have enough time to make it in time for Friday release :-)5
-
Yesterday we released this huge refactoring/rewrite I did alone so it was my task to release and fix any upcoming problems. Not that I would have died to refactor a huge part of the codebase but technical debt was waiting to kill us on upcoming features.
Deployment is done by ssh'ing into prod and pulling from git. I'm happy I could convince them to track a dedicated release branch... Why would we want to build anything? What is automation?
Debian 8 with MySQL 5 community edition... Throws some internal error on my use of JSON functions. Thankfully I was allowed to switch prod to MariaDB but updating packages caused segfaults with the PHP MySQL connector. This is why you need NixOS!
Prod is a 4 core 4 GB VM that would take forever to run migrations. Also no disk space. Had to copy the whole db to staging (which is much more powerful and on Debian 9? diverging environments in the same data center...), migrate there and and pipe back mysqldump directly into ssh while in my neck I feel another client's project that I have about half a week left to finish.
It's Monday night. Customer has a full office of over 50 users at 8 AM.
Almost fell asleep in the car the next day, and I think I have RSI in my enter finger now. -
So, I'm on holiday for a week from Friday. Woo! The plan is to head to a cottage in the middle of nowhere with the wife and the dog and chill the fuck out for a while.
Just found out from my boss that, due to some fucking colossal mismanagement, I have to support a huge release for an architecture rebuild project from 10pm til 8am on Sunday night. While I'm on holiday. In the middle of nowhere.
FML3 -
When I was an apprentice in a small company, ...
my boss told me that his company would never ship release builds, because the "evil optimization option" is responsible for breaking his code.
My first thought was that it wouldn't make any sense at all. The default option for code optimization is always set to zero.
After investigating his code, I found out that he didn't care to properly initialize his variables. The default compiler option for debug builds did implicitly initialize all variables to zero. After that I've confronted him with the fact that implicit null initialization does not conform to the standard of C and C++. He didn't believe me what I was saying and he was questioning my knowledge about C and C++. He refused to fix his code to this day, so he keeps building his libraries and applications always in debug mode.
Bonus fact: He would never build 64-bit applications, because his serialization functions do get incompatible with exisiting file formats. -
Hey guys,
some fellow contributors and I have been working on an update to my second app.
I wanted to ask if you have any suggestions or any feedback on the UI/UX, app or code.
This is the TestFlight invite: https://testflight.apple.com/join/...
This is the repo link: https://github.com/bcye/...1 -
when the release date is may 31 and the client thought it's a good idea to request a bunch of new features and changes in friday afternoon :)
Tomorrow is gonna be a fun birthday... -
API team: "Hey they have a client demo on Monday! What about changing all of our object IDs from int to string on a Friday night without notifying our only subscribers?"1
-
To all guys who write shitty code:
if (false)
I just found that when compiling for Release mode in Visual Studio the JIT compiler eliminates this:
Dead code elimination - A statement like if (false) { /.../ } gets completely eliminated.
And a lot of other similar stuff2 -
So, against like 90% of all odds, we (I) managed to submit the application to Apple for review at the ripe old time of 21.27 last night.
Events of the day included:
- fighting with appstoreconnect (turns out they just return a 500 if you haven't paid your Apple developer membership)
- legal being over an hour later than our absolute deadline for getting the Terms and Conditions and Privacy Policy
- said T&C's and Privacy Policy being delivered in Word, and having to manually format those for our app (thanks guys, please don't use tables again)
- removing FAQs altogether because "it would have taken too long to make those today" (ticket in Jira for this for ~4 months)
- our app was targeting both iPad and iPhone, so we had to rebuild the app for iPhone only because "we don't have app store images for iPad".
On the bright side, that leaves 3 days next week to get the rest of the backend finished for actual go live on Monday 16th, so long as Apple don't reject the app.
Side note: adding the target-device preference affected the android build somehow? despite the preference being iOS only, and wrapped in a platform="iOS" section. -
Planned release today, one of my co-worker's laptop's hard drive died in the morning.
And you guys say Satan is not real :/1 -
When you forgot to remove your debug description and add a real one before publishing your watchface :)
3 -
After many months of hard work we are finally near to release the new website. It feels amazing and is such a relief. Some days it seemed like everything was against me but it's in times like these I am so glad to be a developer.2
-
tomorrow i have a presentation of a webapp but last night i decided to change the ui. i am not done yet and this frontend is driving me nuts.13
-
Company i applied for told me how they are planning to release a new project on friday.
... Decided for a different company -
HIT THAT MOTHER!)#%Y!)!!! BREAKPOINT!!
...
...
...
...
God damn it, it's in Release configuration again.2 -
Finally end of the week. All that is left is a little polishing over the weekend for Monday release. Like get the lastest code from all the developers, put it together and hope it somehow works and fix whatever doesn't :-/
-
Life lesson learned:
Despite good intentions, don't overengineer the front-end, when time is heavily constrained and the release is scheduled and is communicated to media outlets immediately after.
A broken release just makes the client send around multiple emails per minute with tens of people in CC.
Shit happens... at least it was a bargain for them. -
To Android developers:
ALWAYS use annotations for service classes when using minifyEnabled option in build.gradle!! I learn it in the hard way 😐 -
Not a rant, anyone else play League of Legends? Just started back up and it would be cool to game with some fellow ranters. Gaming releases my anger lol5
-
Deployed to production on Sat evening while drunk, surprisingly everything went smoothly. I think this was the first and last time I'll be releasing like this, lol.
Similar stupid experiences anyone?3 -
my first ever release
https://github.com/dextel2/...
please, give your thoughts, and it would mean a lot if you run it locally :)26 -
The story of a normal release:
- tool gets tested "intensely" by 3 ppl quite a long time - everything works
- a major 2 days reserved as maintenance window for even more testing
- release starts
- first the admin panel of the server suddenly is not accessible anymore
- after some problems the tool is deployed
- suddenly servers are down and not pingable anymore - off on off on (provider has major problems .. good job)
- ppl start testing
- testers report lots and lots of new bugs - seems like the testing wasn't that intense after all...
- people start coming with lots of new requirements (oh we need to import those excels.. excels don't match our internal stuff.. )
- confusion over confusion
- getting pissed of a lot...
- quit caring and focus on another project
- profit
Fuck my life -
So we pushed some quick fixes management required to the system before going home to sleep. We warned them that we don’t have much time to check and test them. Because ordinarily such fixes go fine, they insisted.
What do you know, while we slept some smartasses within users drained our system money through the new hole we did not notice.
Manager responsible for this just gone dark, never ever picked up his phone. Just disappeared.
We don’t do such fixes anymore 🤗2 -
So as expected, due to the rush of the submission on Friday, the app was rejected.
I'm fairly certain they never got past the first screen or two.
We have some things to fix, and some things to tackle properly now, which is quite nice, however the current main issue numero uno is that an Apple developer account can take up to 10 days to be created, and Go Live is next Monday.
I wonder who will get the blame for not taking on the "Investigate the iTunes release process" ticket that was in Jira, assigned to someone for ~4 months. -
So we develop several apps for Android.
And since the whole company is full of .Net developers we´re using Xamarin.
That piece of software alone is worth more than one rant.
But today someone called and said he updated to the latest version he got from our server.
But now one of the menu points in the settings menu is opening the wrong mask.
I´m like ... what? Who fucked that one up now. Ok...
I look at the code and, I didn´t expect it to be honest, but it looks alright.
The menu point has the correct id. The function "OnOptionsItemSelected" looks for the correct id and opens the correct activity.
Just to be sure I also check the activity.
Everything good.
So I start up an emulator. Deploy the app in debug. Works correctly.
Create a self signed apk and install it on the emulator. Works.
Repeat the same with a tablet and my personal phone. It works.
Then I install the apk from the server and would you look at that.
It opens the wrong mask.
So it seems only if the app is compiled on the release server it shows that strange behaviour.
And for the love of my 1080ti I can´t figure out what causes it...
Thank you Xamarin! -
So, today we had our first production release of our web app. Last week we changed a big part of our UI. This week we changed the design, rewrote the complete API documentation, implemented mobile support. While the release the administration center of our cloud was unreachable. Shortly after the release we made a bug fix and deployed it directly to production.
So today was a very normal prod release 😂1 -
It’s always fun when you are asked to push to production on a friday afternoon...Because the project managers and owners won’t have be the ones who have to fix something on a friday night or weekend 🤷♂️
-
Ideas I've had over the years that could pan out and be useful:
SMS-DB: Stands for SMS-Data Burst. Used to allow those with low cell signal or no data plan to transfer data between a phone and some client via the standard SMS text space. Would be slow, but would act kinda like dial-up over SMS (as mobile lines are compressed on all service levels, even LTE, so traditional dial-up wouldn't work!) I have a general idea on how packets would be laid out, but that's about it so far...
everything2PNG: Allows one to transpose any file's data into a PNG with a 3 byte per pixel (full color RGB), which allows for a "compression" of sorts (about 91, 93% on preliminary tests) AND allowing further, more efficient compression of the resulting file. (Plus... it's just kinda cool to see files transposed as PNGs.) I actually have a simple transposer to go to PNG, but can't yet go back. Large files (around 600MB) use upwards of 4GB with efficient paging and other optimizations via NumPy so far, so it's not *viable* yet, but it's coming along nicely.
RPi-GPIO Interconnection Bus: A master/slave or round robin method to allow for Raspberry Pis to communicate using GPIO, which can help free up network bandwidth in RPi cloud computing clusters. At most, this'd allow for 4 bits used for pushing to the GPIO "bus", and 4 bits used for pulling from the "bus". 8 pins total are usually unused minimum, so either 3 or 4 pins for upload, 3 or 4 for download, and potentially 1 or 2 for commands, general non-data communication, etc. I made a version of this concept using Round Robin for a client, but it was horribly slow. (I also don't have distribution rights for the code, so i'm working from scratch.) Definitely doable. -
I had a great dream last night of finally finishing a project I've been working on for too long and pushing to prod. I awoke to find magic doesn't exist and I still have to complete it. Saddest morning in a while.
-
Today we had an hour long meeting on gitflow. The senior developer who felt compelled to arrange this meeting, during his demo couldn't figure out how to merge a hot-fix. "But you guys know what I'm talking about, right?" *Forehead=>Brick-wall*
If I wanted to lose brain cells I'd just start doing drugs, at least it would be more fun.1 -
!rant
type(rant) = shameless_self_promotion
I made an open source python personal assistant named W.I.L.L!
I made a reddit post about it here: https://reddit.com/r/Python/...
and you can use it for free at http://willbeddow.com
I've been working on it for a few years and it has a few hundred users.
Code: https://github.com/ironman5366/...12 -
Is it just me or is what susspose to be the tech giants, making more and more n00b mistakes lately... Apple's latest update "best release of iOS yet" bricks the phone, Samsung phones are blowing up...
Things are continously prematurely released to try and beat everybody in the market place which just leads to unimpressive and dangerous product releases.3 -
!Worst, being put on the project a day before release
!Best, finding and fixing all the data model issues before release, so that the next time I have to pull stats about the system, everything actually makes sense, as all foreign keys and indexes would be explicitly defined for once.5 -
After 3 years of constant procrastination, planning, proof of concepts and 17 months of actual implementation I am finally finished my first ever side-project, or actually just MVP of it.
I present you Accio - a boilerplate code generator:
https://github.com/g1ntas/accio
I hold big ambitions for this project, have a large-ass list of features I would like to implement to make it even more awesome, and hope it can become somewhat popular, so I won’t lose motivation to keep working on it.
Tell me, what do you think?7 -
So my company is preparing to do a deployment now... It's Friday 4pm...
And it's just yesterday that the build system was upgraded to a way newer version...
Luckily I'm not responsible of things go sideways 😅2 -
Today I released the next versions two of my company's Android projects. Today was a good day.
Also, releasing on a Friday afternoon FTW! (they are beta releases, so I'm good).1 -
So remember when we said 1.1 would be the last release, and then we said that 1.2 would be the absolute last we promise this time release?
Well buckle up buckaroos because 1.3 will be the last release. -
The icing on this app release cake was piped this morning.
The clients released the app into the wild, without our knowledge, despite some rather large, glaring issues that are present.
As to why they thought it was a good idea, who knows?1 -
Hi! I want to switch to linux but i never used it before and i want advice from you guys about the OS (what distro should i use and how to get started).15
-
Aaarrgghhh! That piece of crap build system we use is acting again. Nobody touched it, nobody had time to replace it with something reasonable and now it starts not building as far as I can tell random parts of system. I guess it can sense we wanted to release :-/ So no time for any nice project and back to kicking its shit together :-(2
-
Someone else updated a firmware and noticed that its worse than the older? The worst ia when you try to fix it and it broke another thing.
Too many bugs in a release (yes, a "verified" release)3 -
You know what I hate? The periods close to a new release. It's that annoying time that managers start heaving impatiently to developers: "Push out new hotfixes! Push out new hotfixes!". Fuck you, man. Don't stress a developer. Kthx. If you think developing is so easy, come do it yourself, you IT-ignorant buffoon.1
-
So I just released a thing I've been working on for the past few days and I'm very glad that it's finally public!
It's a thing that you can use on your website to let the user choose which cookie they want to allow.
https://github.com/metaa/cookiebox
It's worth playing around with the cookie panel in your developer console of your browser on the example page, too!
https://metaa.github.io/cookiebox/
I'd be glad to get some serious feedback and I hope it could be useful to someone out there. 😊 -
!rant
Whoo!! Client's satisfied with recent launch of product!! Still has little bugs to fix here are there, but general feedback was positive, stating it's "much smoother" -
Today is release day!
Got a whole set of new features to deploy on production!
Also, internet at the office has been dead since 6am.
I'll take a coffee break. -
New version release Saturday morning. We have 3 hours window I plan to do it in 15 minutes and don’t loose weekend.
Wish me luck.6 -
Not sure if Google is surprised this happens or they really never face issues using Gradle
Edit:
Took 4 minutes to compile a basic flutter app. But it takes 1.3 minutes to compile a native app. So far liking flutter, still hating React Native tho
1 -
Sad because I was performing an extensive code integration of a release from an external source and then an employee from another building integrated another release before me
Now I need to request a new release with the bug fixes and it will take various days, maybe weeks (and if another release is integrated before, the cycle restarts).
I might be able to integrate by the end of the next year. Who knows. -
Hey guys, i made a program years back and just refactored the thing and gave it a nice GUI. I made it mostly so I can use it in my daily life which I do but now I might release it as open source and give it to some friends. But I’m facing A problem i never faced before...giving it a name. Need some help 😂
Basically, i have tons of series, so i created it to maintain a nice naming convention for the videos but obviously can work for any file list.
- it renames them in a couple of different ways (replacing string occurrences in the file names, appending - prepending strings, completely renaming it alphanumerically. Anyway I use those features most (OCD i know)
- it also grabs subtitles for movies and series (parses its way through subscene and yifisubtitles until it gets to download the zip file and extracts it for me) .
- It also plays random episodes for me when im confused what to rewatch ( just opens a random file in a directory u point it to)
So any name suggestions ?1 -
4 hours to a major release, decided to remove a web service from the app, instead do whatever that service was supposed to do in a DB query, as just realized that the foresaid service will be called only once to fix some data discrepancy !!!
-
Test the project pre-release -> everything works well
Release the project -> new bugs comes out, features are not working anymore, some files are corrupted, your PC is ready to explode and a black hole is going to destroy everything1 -
Currently in our 4th cycle of manual regression testing for a release and still finding bugs. Automated tests? What are those? That sounds an awful lot like it would take time to implement. Time that could be spent fixing the bugs and getting the release out the door.
When release dates take priority over quality.... -
When you click on a link in google and get taken to "wwwqa.companyname.com". I think they're really really confident in their QA environments ;)
-
Finally after 3 fucking months, 15-20 fucking meetings, I got sign off for a feature release. The development took 3 weeks and was completed in March end.
I know being a financial institution and feature was regarding system handling funds, business guys need to worry a bit as any mistake in code can mess up the funds disbursal. But fuckers took 3 months to give sign off.
However, it's finally released and I can relax for now. #peace -
So the project I have been working on for the past 5 months was finally released yesterday with only very minor problems, this stemmed from both programming side, and users entering data incorrectly.
It has been a rather hectic 5 months. I've had to deal with crap like:
- clients not knowing their own products
- a project manager that didn't document anything (or at least everything into a Google Slides document)
- me writing both requirements AND specifications (I'm a dev, not a PM)
- developers not following said specifications (then having to rewrite all their work)
But the worst thing I think would be the lack of vision from everyone. Everyone sees it as a "project" that should be get it over and done with rather a product that has great potential.
So with the project winding down, and only very few things left to fix/implement. Over these 5 months I learned a lot about domain driven design, Laravel's core, AWS, and just how terrible people are at their jobs. I imagine if I worked with people who gave a damn, or who actually had skills, I probably wouldn't have had such a difficult project.
Right now I'm less stressed but now feel rather exhausted from it all. What kind of things do you to help with the exhaustion and/or slow down of pace?1 -
So here it is. Apple release, second round.
This time, uploads to AppStoreConnect took 3 hours and 40 minutes. Submission of the app was at 0.04, just after the planned launch day. Android submission tomorrow.
Tomorrow, and Friday are public holidays.
I'll have to work those, at best being able to not work on the weekend. The client has already told me he's calling me tomorrow morning to talk about things.
I don't want praise, but I'd like him to respect that while I may just be a lowly developer, I would like to have a life.
When are the happy times coming? -
Release build fails. Bad test was commented out on development branch but merged into release branch.
-
My first production support release is next week and its from midnight till 5am and be at work at 8:00am. If something goes wrong with any of the other developers from our team goes wrong I have to figure it out. And this image is exactly how I picture it goes, if any tickets fail. (🤘🏽 bring it on! )
-
The wonderful feeling when project was finally relesed and deployed, you have no chance for any more last minute fixes and you can finally merge into master and break everything :-)
-
Here we go again.
It's 21.15, on my day off. I've been working all day. Client isn't responding, but we're supposed to submit apps for review again.
This is what my life has become.3 -
I absolutely hate release days..
Yes I am happy that it will never be a friday in my company but you can tell everyone at office that the page will be down for like half an hour and this a month before actually doing it and they still call you 20 times in that half hour while everyone at the IT department already knows about those important issues and we are already yelling at each other
at those days its really hard to stay strong and not start again smoking.. -
If I have a project wich use AGPL and LGPL Libraries at the same time, my project must to adopt AGPL or LGPL, I'm so confused.1
-
Yesterday I installed linageos without gapps and wondered if there is an official release of the devrant apk without Google store. I acquired my copy from apkpure
-
I am launching an Android app in Play store for the firdt time, any To-do list that I should consider before launching it? already been thru SO to-do, anyone has anything more to add?4
-
Two architectures to support, on one everything went smoothly, other one I spend since Monday till yesterday 2am to make it work. Now time for half-day meeting and if it compiles in the meantime, I can release today before leaving work. Sounds like a solid plan, Friday afternoon release. What could go wrong? And I hoped it will work nicelly on Monday, latest Tuesday.
-
Release was supposed to start at 10 am, its now 11am but our release document is being debated heavily. The outage is scheduled to last until 2 and we thought we'd be tight for time when starting at 10 FML to right now..
-
I just commented a test so the PR passes and the feature reaches next release; I can't fix it (Damn react testing library tests)
but after that, the linter failed for the same PR, so I just fixed it and did a git push -f
I guess once you cross the line you cannot come back
feel my pain1 -
Release is out now!!!
Just seven month after first beta! I'm so fond of those customer change requests. Now I'm back in the predictable world... -
Some of my first thoughts on the new 16.3 release of React...
New Context API:
- I’m glad they made the context API less scary, but as a redux user I will still be staying away from using context as a best practise.
Strict Mode:
- I like this a lot. React allows for great freedom in how you do things, but also offers the freedom to write some shit code that in the end does the job. A way to enforce best practises in JSX is good in my eyes.
New lifecycle methods:
- meh. Life moves on
https://medium.com/@baphemot/... -
Everyone has Allo, but here in Germany it isn't yet available. Does anybody know when I can talk to Allo so I have a friend? :P5
-
Honest question - when a company offers has an open source software product (in the name of transparency and whatnot), but offers it as a binary release as well for non-developers, what guarantee do you have that the release was *really* compiled from the source they provide?
Top Tags
Weekly Rant
View