Made a logo design with Gravit Designer

it feels fine but.... IDK if I did my logo right

how to be a shitty client:
- have a legacy database where column names are misspelled and everything is nullable
- hire external help which instead of helping break the ui (bonus points for breaking the api too)
- demand a very much custom auth logic but decide to use aws cognito for shits and giggles
- demand 1hr daily meetings
- demand biometric auth with 0 knowledge of how biometric auth works (the previous devs just had a face id prompt which does nothing and retrieved email and password saved on the device???)
- message me at 2am because you don't understand how timezones work + demand a build while you're at it
- call me a "heretical pagan" because i took a day off on a holiday you don't celebrate (???)

i could go on but i think this is enough

Why do simple errors take the longest to fucking find!

Was using the geolocation api (js) to get the current longitude and latitude of my location. Stored them in an object to use in a fetch(). Every time I ran the fetch it was giving me the wrong location!

1hr later I realized I had used.

Fetch(https${longitude}blablabla${longitude})

After realizing this mistake and everything I that lead up to that moment I closed my MacBook and took my ass to sleep.

Moral of this story is...take fucking breaks.
Goodnight

ideal sprint fallacy.
total days 10 , total hours(excluding breaks ) 8 hrs per day= 80 hrs per dev

code freeze day = day 8, testing+ fixing days : 8,9,10. release day : day 10
so ideal dev time = 7days/56 hr
meetings= - 1hr per day => 49 hrs per dev

- 1 day for planning i.e d1 . so dev time left . 6 days 42 hrs.
-----------
all good planning. now here comes the messups

1. last release took some time. so planning could not happen on d1. all devs are waiting. . devtime = 5 days 35 hrs.

2. during planning:
mgr: hey devx what's the status on task 1?
d: i integrated mock apis. if server has made the apis, i will test them .
mgr : server says the apis are done. whats your guestimate for the task completion?
d : max 1-2 hrs?
m : cool. i assign you 4 hrs for this. now what about task 2?
d : task told to me is done and working . however sub mgr mentioned that a new screen will be added. so that will take time
m : no we probably won't be taking the screen. what's your giestimate?
d : a few more testing on existing features. maybe 1-2 hrs ?
m: cool
another 4 hrs for u. what about task 3?
d : <same story>
m : cool. another 4 hrs for u. so a total of 12 hrs out of 35 hrs? you must be relaxed this sprint.
d : yeah i guess.
m cool.
-------
timelines.
d1: wasted i previous sprint
d2 : sprint planning
d3 : 3+ hrs of meetings, apis for task 1 weren't available sub manager randomly decided that yes we can add another screen but didn't discussed. updates on all 3 tasks : no change in status
d4 : same story. dev apis starts failing so testing comes to halt.
d5 : apis for task1 available . task 3 got additional improvement points from mgr out of random. some prod issue happens which takes 4+ hrs. update on tasks : some more work done on task 3, task 1 and 2 remains same.
d6 : task1 apis are different from mocks. additionally 2 apis start breaking and its come to know thatgrs did not explain the task properly. finally after another 3+ hrs of discussion , we come to some conclusions and resolutions
d7 : prod issue again comes. 4+ hrs goes into it . task 2 and 3 are discussed for new screen additiona that can easily take 2+ days to be created . we agree tot ake 1 and drop 2nd task's changes i finish task 2 new screens in 6 hrs , hoping that finally everything will be fine.

d8 : prod issue again comes, and changes are requested in task 2 and 3

day 9 build finally goes to tester
day 10 first few bugs come with approval for some tasks
day 11(day 1 of new sprint) final build with fixes is shared. new bugs (unrelated to tasks. basically new features disguised as bugs) are raised . we reject and release the build.

day 2 sprint planning
mgr : hey dev x, u had only 12 hrs of work in your plate. why did the build got delayed?

🥲🫡

I feel inferior.... :(

Maybe I used too many ifs...

and it took me 1hr it seems...

maybe i should go back to sleep...

actually i woke up at 2am and realized i was supposed to be taking a nap... so i sorta overslept by 6hrs... tho i still need to work tomorrow... ehhh... today.

Question about conditioning my new android lithium battery.

I dont understand what's happening with my phone. Have old Xperia Z3 D6603 (running android 6.0 marshmallow).

Had problems with battery since it was not lasting even 5 minutes so bought a new battery from ebay and installed it yesterday.

So first time I put it to my phone it showed that it had 70% of charge. I've read in battery description that I have to discharge the battery and recharge 3 times.

First time I wanted to discharge from 70% to 1% and with a battery discharge app + youtube 1080p videos + wifi signal it took only around 1 hour and phone was at 1%. From 1% till complete discharge it took me extra hour and then phone died.

I plugged it to charge and after 15 minutes it showed that battery now is at 100% (which is insane, it should take 2-3hrs to charge it up to 100%). So I charget it for 2-3 hrs ignoring that it said 100% already.

I discharget it from 100% to 1% in 1 hour and now again phone is stuck at 1% and it took me 2 more hours to discharge phone until battery died completely.

I don't believe that this behaviour will fix itself. How can I fix this problem so that battery percentage would be distributed evenly? Now it drops from 100% to 1% in 1hr and then from 1% to 0% in 2 hrs.