Huge congrats to @linuxxx for being the first ever member of the devRant community to reach 100,000++

This is an awesome accomplishment and @linuxxx earned all of his ++ with awesome stories and has represented everything the devRant community is about while getting there.

So once again, congrats @linuxxx, and thanks for everything you have contributed to devRant!

@dfox @trogus How about ++ milestones?
F.e.:
404 ++'s: “Error 404“
255 ++'s: “256 Bytes“
69 ++'s: (Well you know...)
And so on... (be creative)

Let's just appreciate the fact the Unix timestamp will reach 1500000000 on july 14th :)

# Day 0:

Me: "Hey boss, I want to let you know that I need this kind of information from the customer for these features, otherwise I cannot finish the project's milestone in two weeks."

Boss: "OK, just continue as far as you can get. We have to get this finished."

Me: "Well, I cannot go any further for these tickets. I need that input. Shall we leave them in todo?"

Boss: "OK."

# Day 7:

Boss: "Whe didn't you start on these tickets in todo?

Me: "As I have told you, I need some information."

Boss: "We gotta get this out of the door!"

Me: "Yes, if we want to meet the deadline, we should. Yet I cannot guess the feature. Also, let me create a column: `to clarify` and move that ticket there. As I have said: I need that information. You have to contact the customer about it and get their feedback.

Boss: "OK."

# Day 13:

Boss: "Why isn't this project finished? There are still tickets open."

Me: "You never provided the information I asked you about."

Boss: "I want an explanation not an excuses."

Me o_O: "This is the explanation. I was asking you on multiple occasions about the required feedback. You never provided it. See the columns name? It's called `to clarify`. We created it last time together. That clarification never happened even though I told you that I need it. I cannot do magic. I can only implement features, and while I can sometimes make intelligent guesses to their use cases, I rather implement their actual ones than my fictional ones.

Boss: "You should have told me."

Me: ಠ_ಠ

@Linux thought this might be an important milestone for you. I remember when you got 1000...

!rant

Guys! I did it! Its possible!

My task was to extension a code in php. I wrote 100 lines of code and then it workes on first try without any errors!

This is a milestone!
Bill Gates is nothing against me!

I've just reached 1000++. It's not much and it's taken me almost 1 year but it's still a pretty nice milestone in my book :)

!rant
I quit my job today for a better one! It was my first job after graduation, been there for 2.5 years so it's a big step for me.
Wish me luck on my new job! :-)

We passed a milestone: 250,000 phpunit testcases.

If it weren't for a heavily parallelized build pipeline which splits it out over 20 servers, it would take about 7.5 hours to complete.

Not hating on PHP, and without tests it would truly be hell...

But still, fucking hell, we outgrew PHP.

Not having a solid type system just means you either accept more bugs, or write thousands of unit tests to guard all the foundational cracks in the system.

On the bright side, I get a coffee break after every commit 😄

paraphrased

C: "hey, we've seen the ticket resolved with a bug bounty rewarded to you! congratulations!"
C: "we've talked about it today on our meeting and think we deserve 85% - since it was discovered by you while working on our contract and system!"

That was so bizarre to me and I was speechless for a good 10 minutes, didn't even have any witty reply afterwards.

I just cancelled the contract, reported the client to my middleman, explained it to the on-sight business contact and requested the final milestone to be released with one week notice until it gets to be a public case if not released through escrow.

I'm still somewhat shocked at how greedy one can be, the whole system package I was working on had estimated 150-300k post first week launch (tons of existing clients merged and unified into one system, with much more paid and feature stuff etc.), the bounty I got was around 3.5k, it still didn't sink in me.

+++ Thank you for 1000+'s! +++

So guys we did it! We've reached our first big milestone!
This account was created about a month ago, and we are already this far!

Thanks to all authors (@DLMousey, @filthyranter, @baewulff) who are putting a lot of work and time into their articles and help this account to further grow in size!

To make this article at least a bit informative, here's how we publish our posts:
When I started this account, I hadn't thought of how articles were going to be published. Should I give the password to all writers? Should I post the articles manually?
Well, after I've started the devNews Discord Server, @olback suggested making a Discord Bot, that helps us to publish our stuff.
After surprisingly few hours, @olback already got a prototype working.
We have a special channel and whoever writes stuff in it, updates the current article. Later, I took on the work, @olback has done and switched to LowDB, to be able to let multiple users have their own articles they are working on and much more. (Like special signatures)
And that's how it is now.
We have a channel for draft, where we write our stuff and a channel for publishing, where the bot listens to what we write and then publishes the articles with a command.
That's all of it.

Thank you for reading!

Congrats to localhost for being the second devRant user ever to reach 1,000 points! I've greatly enjoyed his awesome posts and I know a ton of other people have too! Thanks for the laughs/great convo and I'm looking forward to an NYC meetup in May :)

Weekend milestone finished... 27 minutes to late but finished. Mini Voxel Engine for a Game in Unity.

Did someone else finished a milestone this weekend also?

Show me your progress :D

It has come to my attention that, I @C0D4 have become an addict.

This is something I thought I could fight. Resist the urge to become attached to my substance of choice in the early days and not have it compromise my every day life.

But how wrong I was, my addiction grew over time and my ability to resist the urge to peek at a ++ spam wall, or get back into a discussion at the mention of my name, read more of the great stories that remind us all, we are not alone and many of us are on a similar journey.

So, devRant my one true drug of choice, Today is a significant milestone on this path of corruption, my 1024th (1kib) day!

Here's to another 1024 days of snorting rant lines 🙌 🤤😎

First I wanna say how grateful I am that devRant exists, because my friends either don’t understand this vocab or don’t care lol.

Last week I worked on a pretty large ticket, opened a PR with 54 file changes. Just to follow standards I set the PR milestone to a future release version, but the truth is I didn’t care which version this work ended up in— I just needed it to go into the develop branch asap.

Since it was a large PR there was some expected discussion that prolonged its merging, but in the meantime I started a second branch that depended on some of the work from this branch. I set the new branch’s upstream to develop, fully expecting my PR to merge into develop, since that’s what I set the PR base to.

I completed all the work I could in the new branch, and got two colleagues to approve the initial PR so it would be merged into develop, I could add the finishing touch and get this work done seamlessly before the week was over. They approved, it got merged, I pulled develop, and… my work wasn’t there. I went to look at my PR and someone had changed the base branch to a release branch. It was my boss, who thought he was helping. (Our bosses don’t actually work on the same team as us, so he didn’t know. it’s weird. We have leads that keep track of our work instead.)

I messaged him and told him I really needed this in develop, knowing our release branch won’t be in develop for probably another week. I was very annoyed but didn’t wanna make him feel too bad so I said I’d just merge the release branch into my new branch. So many conflicts I couldn’t see straight. His response was “yeah and you’ll probably have a bunch of package manager conflicts too because that’s in that release.” He was right— I have so many package manager conflicts that I can’t even see how many compiler conflicts there are. I considered cherry picking my changes, but the whole reason I set develop as my upstream was to avoid having any conflicts since I’m working in the same functions, and this would create more.

So I could spend the next (?) days making educated guesses on possibly a thousand conflict resolutions, or I can revert my release branch merge and quietly step back and wait for the release branch to be merged into develop.

I’m sure cherry picking is the best option here but I’m genuinely too annoyed lol, and fortunately my team does not care to notice if I step back and work on something else to kill time until it’s fixed automatically. But I’m still in dire need of a rant because my entire plan was ruined by a well-meaning person who messed with my PR without asking, so here is that rant and I thank you for your time.

Indian web dev companies suck ( for developers )

when I finished 3 year grad program in computer application here in my country (India), I thought life's gonna be fun working as a developer. Oh boy, I was so wrong.

I started out working for a small service based IT company, followed by 2 more. I realized really quickly that they're nothing short of a scam. If your company's only agenda to somehow survive in the market and showing no signs of growth in 8 fucking years, then I'm sorry you're working for scamsters.

Now I'm not saying that all of them are alike. But most of them sorta are.

They don't give a shit about quality, not one bit. Quality means no money in the short run. And they haven't been able to develop any strategy to deal with that. Hence, no growth.

They promise 100 things on their website but only provide shitty services in 10.

There is no pair programming, no code review, no code quality check, no architect, no database designer. They won't give you extra time to write test cases. They use git as a storage device.

They don't put their developers (especially the ones who are learning) under any sort of managed development framework to ensure smooth work.

At the end of the day, their main objective is to somehow NOT deliver a project but finish a milestone and make money out of it.

After cashing out for a milestone, they want you to put your current project on hold and start working on a new project until you have like 10-15 projects in the pipeline and you're severely overwhelmed and you just wanna fucking QUIT.

They would say YES to literally every fucking thing, only to disappoint the client later.

I can't believe someone in the US, or UK thought it'd be a good idea to approach these companies
for their brand new app ideas. They're so fucked.

They're rarely finishing any project.

I'm sorry if I hurt your feelings. I had to get it out of my system.

Guys i got 1000++!!!

It's not that i'm special now.

Just more special than others.

Oh I remember the old times when devRant veterans like @linuxxx or @Alice posted their first rants and I welcomed them!

I even remember that night I gave @dfox the idea of creating this app! "That's stupid.", he said. "If this app should be succesful I owe you some special kind of duck we will produce for some reasons I don't know yet!", he said.

But for real now: Thanks everybody for being a part of this and for bringing me so much joy!

First off: setup reveal
second off: thanks everyone for the 1000++!!
Lastly: devrant stickers!
Thanks @dfox and @trogus for making this awesome platform

Just about to start a milestone presentation, when suddenly the boss froze and yelled:

"Wait! Don't move! There is a bug, let me take it back to nature where it belongs..."

*Grabs a bug on my shoulder and carries it to the window*

Feel free to scroll by if you feel like it.

I am just very excited this evening because with today's commit I have reached a very important milestone in my side-project development. As of today all the [so far] 12 components are all working together and processing the main flow themselves.
No special functions, no test data in the code, nothing like that. A client is able to do its thing now as it should.

I know it doesn't sound like much, but as I'm working on this gigantic beast for 3 years now this milestone is hell of a reward for me!

Just wanted to share :)

edit: f* it! I'm getting a cake!

[long]
When searching for internship via school I found this small startup with this cute project of building a teaching tool for programming. There were back then 2 programmers: the founder and the co-founder.

Then like 1 week before the internship started, the co-founder had a burnout and had to get off the project, while the company was so low on budget the founder, aka my new b0ss, had to work separate jobs to keep the company alive. (quite metal tbh)

It's funny because I'm a junior developer, 100%. I've been coding as a hobby for around 8 years now but I've never worked in a big company before. (No exception to this workplace either)

First project I get: rewrite the compiler. The Python compiler.
"But wait, why not just embed a real compiler from the first case?"
-nanananana it's never simple, as you probably know from your own projects.

The new compiler, as compared to existing embedded compiler solutions out there, needed these prime features:
- Walk through the code (debugger style), but programmatically.
- Show custom exceptions (ex: "A colon is needed at the end of an if-statement" instead of "Syntax error line 3")
- Have a "Did-you-mean this variable?" error for usage of unassigned variables.
- Be able to be embedded in Unity's WebGL build target

All for the use case of being a friendly compiler.
The last dash in the list is actually the biggest bottleneck which excluded all existing open-source projects (i could find). Compliant with WebAssembly I can't use threads among other things, IL2CPP has lots of restrictions, Unity has some as well...

Oh and it should of course be built using test-driven development.

"Good luck!" - said the founder, first day of work as she then traveled to USA for **3 weeks**, leaving me solo with the to-be-made codebase and humongous list of requirements.

---

I just finished the 6th week of internship, boss has been at "HQ" for 3 weeks now, and I just hit the biggest milestone yet for this project.

Yes I've been succeeding! This project has gone so well, and I'm surprising myself how much code I've been pumping out during these weeks.

I'm up now at almost 40'000 lines of source and 30'000 lines of code. ‼
( Biggest project I've ever worked on previously was at 8'000 lines of code )

The milestone (that I finished today) was for loops! As been trying to showcase in the GIF.

---

It's such a giant project and I can honestly say I've done some good work here. Self-five. Over-performing is a thing.

The things that makes me shiver though is that most that use this application will never know the intricates of it's insides, and the brain work put into it.

The project is probably over-engineered. A lot. Having a home-made compiler gives us a lot of flexibility for our product as we're trying to make more of a "pedagogic IDE". But no matter that I reinvented the wheel for the 105Gth time, it's still the most fun I've had with a project to date.

---

Also btw if anyone wants to see source code, please give me good reasons as I'm actively trying to convince my boss to make the compiler open-source.

Cheers!

First pull request just got merged! Woooo!

Over the past few years I've tried to start learning JavaScript, only to become annoyed and move on. In my latest effort, I finally hit that "aha!" milestone. Turns out that the tutorial books and videos everybody said we're the ideal way to learn weren't so ideal for me. What ended up working:

1. Find a project tutorial.
2. Understand maybe 5% of what I'm doing.
3. Alter the project, ultimately breaking it.
4. Spend the few hours Googling.
5. Scrap it.
6. Redo it, exactly the same. It works this time.
7. Bask in my glory. For I am a JavaScript master.

I'll get there eventually. I think.

After serveral weeks of stress, bug hunting, despair and fun - I JUST COMPLETED A PROJECT MILESTONE !!

Time for a reward :]

Today my first ever PR on a community repo on Github just got merged!

I was always afraid to open a PR on any project because of my lack of self confidence. It's a really big milestone for me and I'm really proud to say that the code and the tests I wrote immediately got approved and merged into the main branch.

When I was at university in my last semester of my bachelor's, I was doing a game programming paper and our last assignment was to group up and make a game. So I go with one of the guys I know and this other dude since his previous game was really neat. Then two randoms joined that from my first impressions of their games wasn't much at all (one guy made four buttons click and called it a game in Java when we had to make games in c++ and the other guy used an example game and semi modded it.

Anyways we get to brain storming, totally waste too much time getting organised because the guy that volunteered (4 buttons guy) was slow to getting things sorted. Eventually we get to making the game and 4 buttons guy hasn't learnt how to use git, I then end up spending 3 hours over Skype explaining to him how to do this. He eventually learns how to do things and then volunteers to do the AI for the game, after about a week (this assignment is only 5 weeks long) he hasn't shown any progress, we eventually get to our 3rd week milestone no progress from him and the modder, with only three classes left we ask them both to get stuff done before a set deadline (modder wanted to do monsters and help 4 buttons with AI) both agreed and deadline rolls up and no work is shown at all, modest shows up extremely late and shows little work.

4 buttons guy leaves us a Skype message the day of our 2nd to last class,, saying he dropped the paper...

Modder did do some work but he failed to read all the documentation I left him (the game was a 2d multiplayer crafting game, I worked so hard to make a 2d map system with a world camera) he failed to read everything and his monsters used local coordinates and were stuck on screen!

With about a week left and not too many group meetings left we meet up to try and get stuff done, modder does nothing to help, the multiplayer is working my friend has done the crafting and weapon system and the map stuff is working out well. We're missing AI and combat, with our last few hours left we push to get as much stuff done, I somehow get stuck doing monster art, AI is done by the other two and I try to getting some of the combat and building done.

In the end we completely commented all of modders work because well it made us look bad lol. He later went to complain to my free claiming I did it and was a douchebag for doing so. We had to submit our developer logs and the three of us wrote about how shitty it was to deal with these two.

We tried out best not to isolate ourselves from them and definitely tried to help but we were swamped with our other assignments and what we had to work on.

In the end leaving and not helping right when the deadline is close was what I call the most shittiest thing team mates can do, I think sticking together even if we were to fail was at least a lot better.

Wow ! What a milestone ! 1000++'s

Thanks everyone for this amazing community ! I really feel I'm part of something, I never got so involved in a community and it's awesome :D

Thanks to you all ! All the doggos for me now !

Here you go
Your 69(nice)999.
Aaaand your 70k!
Congrats @root!

Going to sleep with a newly gained 4k milestone! I'm gonna have good dreams :)

I never thought anyone would actually like me on this platform when I joined last month, but I guess I was wrong. I got along with a few awesome people, which I'm gonna list right below. Other than that, I'm glad to be a part of the community :)

The people I got along with the most:
- Linuxxx, the privacy superstar
- ewpratten, the young programming genius
- devTea, the compulsive upvoter
- Condor, the account deleter
- Alice, the pink freak
- Stuxnet, which I kinda forgot the first time I wrote this (sorry!)
- Almost everyone on here!

To be clear, those are people I enjoy talking with, they might not feel the same way. I just wanted to thank those who made me smile the most here.

So now that Covid is apparently "gone", management wants us to come to the office to participate in daily team building events to hype up people to commute full time...
but still gotta finish those milestone deliveries while having too many meetings and deadlines.

Murphy is watching us from above with a shit-eating grin.

Published my first Android library today!! It's not something big but I guess I reached a new milestone in my devlife today!!

I would like to thank everyone who ever upvoted me because I am now joining the 1000 club haha :D

a milestone for me 😬

Not really a rant and I'm only a beginner/hobbyist, but for a few months I've been active in a local gamedev club where I recently managed the courage to approach a much more experienced (5+ years) programmer.

We managed to have a good 30 minute chat (despite not using the same programming languages) and he told me "I really appreciate talking to someone who actually understands programming and what they're talking about!"

It felt like a pretty big milestone on my path to game development, at least it feels like I know more than I care to admit to myself.

!dev

Yes! I just managed to play Take Five by ear with the exact chords. Might not sound like a lot, but this have been a milestone I've always wanted to reach. Yay!

Could do with some dev input here.

Going to rename most of my projects before I start them up again just for some consistency amongst everything so...

Because I name my projects internally as a different tree for each milestone (1.0 is maple, 2.,0 is pine etc) I'm going to have my other stuff follow a tree related naming scheme, first up is my game engine/framework...

It's currently called the 'Mod Engine' but I have 3 idea's and want to know people opinions

- Woodsman Engine
- Lumberjack Engine
- Lumber Engine

Which is best do you think or can anyone think of any better ideas? :-3

!rant

milestone: exited vim for the first time

How I got selected for GSoC'19:
I will describe my journey from detail i.e from the 1st year of the college. I joined my college back in 2017 (July), I was not even aware of Computer Science. What are the different languages of CS, but I had a strong intuition of doing BTech from CSE only?

So yeah I was totally unaware of the computer science stuff, but I had a strong desire to learn it and I literally don’t know why I had this desire. After getting into college, I was learning HTML, Python, and C, also I am really thankful to my friends who really helped me to learn, building logic and making stuff out of it. During the 1st month of joining the college, I got to know what is Open Source, GSoC, Github due to my helpful seniors. But I was not into Open Source during my 1st year of college as I thought it is very difficult to start. In my 1st year, I used to do competitive programming and writing scripts in Python to automate various stuff. I never thought that I would even start doing Open Source development, also in the summer vacations after the 1st year I used to practice programming on HackerRank and learnt an awesome course called Automate the Boring Stuff with Python(which I think is one of the most popular courses for Python) which really helped me to build by Python skills.

Now the 2nd year came, I was totally confused between doing Open Source development or continue with my Competitive programming. But I wanted to know about Open Source development, so I thought to start now will be a good idea. I started attending meetups of OSDC(Open Source Developers Club) which is a hub of my college, which really helped me to know more about Open Source development from my seniors. I started looking for beginner friendly projects in Python on the website Up For Grabs, it’s really helpful for the beginners. So I contributed in a few of them, and in starting it was really tough for me but yeah I continued, which really helped me to at least dive into Open Source. Now I thought to start contributing in any bigger project, which has millions of lines of code which will be really interesting. So I started looking for the project, as I was into web development those days so I thought to find a project which matches my domain. So yeah I finally landed on Oppia:
Oppia

I started contributing into Oppia in November, so yeah in starting it was really difficult for me to solve any issue (as I wasn’t aware of the codebase which was really big), but yeah mentors at Oppia are really helpful, they guided me which really helped me to start my journey with Oppia. By starting of January I was able to resolve around 3–4 issues, which helped me to become the collaborator at Oppia, afterward I really liked contributing to it and I was able to resolve around 9–10 issues by the end of February, which landed me to become a Team Member at Oppia which was really a confidence boost and indication for me that I am in the right direction.

Also in February, the GSoC organizations list was out, and yeah Oppia was also participating in it. The project ideas of Oppia were really interesting, I became even confused to pick anyone because there were 4–5 ideas which seemed interesting to me. After 1–2 days of thought process I decided to go for one of them, i.e “Asking students why they picked a particular answer”, a full stack project.

I started making proposals on it, from the first week of March. I used to get my proposal reviewed frequently from the mentors, which really helped me to build a good and strong proposal.

I must say a well-defined proposal is the most important key for getting selected in GSoC, also you must have done some contributions to the organization earlier which I think really maximize your chances of selection in GSoC.

So after my proposal was made, I submitted it on the GSoC website.
Result Day:

It was the result day, by the way, I had the confidence of being selected, but yeah I was a little bit nervous. All my friends were asking when is your result coming, I told them it will come at 12.30AM (IST). Finally, the time came when I refreshed the GSoC website, Voila the results were out. I opened the Oppia organization page, and yeah my name was there. That was the day I was really happy and satisfied, I was thinking like I have achieved something in my life. It was a moment of pleasure for me, I called my parents and told them my result, they were really happy for me.

I say cracking GSoC is worth it, the preparation you do, the contributions you do, the making of the proposal is really worth.

I got so many messages from my juniors, friends, and seniors, they congratulated me. After that when I uploaded my result of Facebook and LinkedIn, there were tons of comments and likes on the post. So yeah that’s my journey.

By the way, I am writing this post after really late, sorry for it. I must have done it earlier, but due to milestone 1 of GSoC, I was busy.

Just realised that i have reached 1K +1's, thanks everyone!

"How many time do you need to close this task?"
"Mmh I guess 3 days and half"
"Ow..the delivery is this evening, is that a problem?"

Dude. Seriously, what the fuck!

Yay, one more milestone :)

"404 - Account not found"

After a long time I finally reached this milestone of 100% code coverage. I often asked myself why I had to test every function, no matter how small. But this log output of 100% was worth it.

Yeah ! 100++'s

It's not a big milestone but ... Well it's something xD

Thank you all for this amazing community !

I can finally say I have L33T users 😎

Had anyone experienced with an impatient boss who require you to complete the project in the month you just recently got hired?

Here's the story, I recently got hired by a company, joined on 1st April 2022, the boss expect me to complete the app for Android and iOS by the end of this month. (An e-commerce applications exactly like shopee.com) Without providing me the Backend ApI , that they mentioned. They just gave me a and expect me to know what's happening at the backend.

He require me to give him a specific date that I can launch the app to play store and Apple store. (From my experience, it take days, weeks or months). He need a milestone of what I need , did , and will do (which predictably that they will reject any new ideas proposed) .

I even considering to quit, but I need opinions. Am I just too sensitive or there's something wrong?

The scary thing about burnout is that you usually don't realize you are burning out before it's too late.

Personally, at least, I've worked on projects that just felt a little intense at the time, but after taking a step back due to holidays or hitting some milestone I realize I never want to have anything to do with it ever again. One project makes my stomach drop even today every time I see the code; Not because the code is bad, but how it takes me back to how miserable I was without admitting it to myself.

The biggest red flag I look for is when I'm tempted to work on stuff in my free time. When this starts seeming like a solution there's a serious problem with the project that needs to be addressed.

Passing my projects to the next maintainer before leaving the company. And I had to leave this in the milestone

I noticed the main dogecoin repo was one star short of a significant milestone. Is it odd to feel honoured to be their 2000th?

What personal milestone have you achieved this month?

I'm a tech lead for a new agile project for a manager who knows nothing about agile. Having to work on a chart that shows exactly how many sprints each milestone will be and when it will complete for like, 17 sprints from now when requirements aren't even set. Wtf?

Bloody mother fucking jesus christ....

It's working.

Sometimes I really wish I had the gift to be creative and to e.g. draw a (metaphoric) image of the shit I had to fix and how it felt to fix it.

It's sad not being able to share stuff in a way everyone can understand it :/

I uncludged the last bits of the networking / loadbalancer / craptastic network.

The whole chart that includes most of the associations / information for the network fits easily on a A2 paper. Internal only.

Just migration of a few remaining servers to Proxmox and a large MySQL to Postgres migration outstanding....

1.75 years and it's the first large milestone achieved. Large milestone as in it will not be a total clusterfuck anymore.

Still a lot of stuff to do...

But down to one major OS, Debian, for everything (container / VMs)... only LTS supported versions for services...

No more stuff that's so old it's near fossil state. We stillhad Ubuntu 12.04 running... :) ;) And XenServer is nearly gone...

Too many feels. Too many brain poofs. And way too much pain.

Management has bequeathed that it shall hit prod tomorrow, the developers cry 'but it's not ready`. Hush little dev for tomorrow we hit another payment milestone

MICROMANAGEMENT

I got assigned a milestone we had delayed twice already. It needs to be ready for tomorrow, it's harsh but doable.

Guy from another team, looks at my folder system during the presentation, something like
"src/views/users/view-all/view-all.template.html" and starts whining "hurr durr this isn't good tho, you should have chosen a significant name, it's impossible to understand what this file does".

Honest thought: if you can't navigate through folders, you shouldn't be writing code in the first place.

Agree or disagree: as a developer guaranteeing your work, when you accept a deposit from a client as a milestone payment, you should not spend that money until the client signs off on the milestone in case they decide your work is unsatisfactory and want to go elsewhere.

Finally became a 2GB lol just random but a milestone nonetheless. Thanks all for listening to my inner voice when i feel there is no place to get these recursive thoughts out of my head.

Have a great day

The source engine is interesting, because it has reached that stage of life where it's old enough to be remarkable-- in the sense that it could be called 'legacy', a sort of milestone in development practices and thinking, both in software, and design.

That said, a better look at it might be from the lense of *uses today*.

A lot of former source engine (SE) devs are now going to unity or unreal, I don't blame them.
But it's interesting to examine examples of games that haven't.

One such game is the freeware "No More Room In Hell". A couple online play throughs shows a wealth of well designed maps (and an even greater horde of shovelware maps, but hey, you take the good with the bad).

The age of the engine itself shows. Even in games like Left 4 Dead the engine's age can be seen. This, in some respects has been a drag, but also a blessing. Where other games could rely on their effects, shaders, and other tech, modders, map makers, and designers have had to rely on wit and creativity.

Enter "situated environments."

In an age where many people desire to travel, to go places, and have grown up doing the exact OPPOSITE, there is a great desire for variety of locations in games: not merely 'environmental' in the shallow sense of a 'theme' such as 'lava', 'tundra', etc. But in the sense of setting in general.

We want places that are both out of reach and yet familiar. Fire-fights happen in city streets. Apocalypses happen in neighborhoods where the skyline is both broken and at once something we know by sight. Open air markets, grocery stores, neighborhoods, all of these provide the back drops of popular games and series such as COD, Battlefield, The Last of Us, and yes, the example game, NMRIH.

I call this idea of 'familiar but out-of-reach level design', "situated environments", because familiarity with them, but *lack of real life experience* with them, on a day to day basis, allows people's expectations to fill in the gaps.

No one for example would argue the layouts of 7 Days To Die are familiar, but most of us don't spend all day in a junkyard or a high rise hotel.
So they *feel* familiar. Likewise with Skyrim, the villages and towns, both iconic and strange, our expectations formed by cultural inheritance, hollywood films, television shows, stories, childrens books, and yes, other games.

In a way, familiarity-without-real-in-person-experience is a shortcut for designers, one that lets them play with the player's head-space, the players subconscious idea of how a space and setting *should* work, what to *expect* out of the area, how to *operate* within the area. And the more it conforms to expectations, the more surprising an overdesigned element appears to be, rather than immersion breaking. A real life example of this is people's idea of chernobyl. When they discover the amusement park and ferris wheel they're blown away by the juxtaposition of the wasteland that surrounds them and the associations ('nostalgia' as it were) that such a carnival ride carries for many of us. It simultaneously *doesn't belong* and is yet all at once *perfectly situated in the environment*.

It is to say 'surreal', which is adjacent to the idea of *being real*, in terms of our "perception of what is and isn't plausible, if not possible."

This is at the heart of suspension of disbelief, because in essence, virtual worlds are a lie, like fiction, and good fiction violates expectations in order to tell us truths about reality. As part of our ability to differentiate bullshit from reality, there is to say an element in our bullshit detectors (doubtless evolved over many 10's of thousands of years), that is designed to not merely detect what is absurd in our limited experience, but to incorporate absurdity into everyday experience. In that sense part of our rationality is the acceptance of irrational experiences, learning from it, and discovering 'a proper place for each thing' in the "models of the world" we all carry around in our heads. Eventually we normalize the absurd, it becomes the new reality, and what remains unassimilated becomes superstition (real or otherwise), a figment, or an anomaly.

One of the best examples I've encountered is The Last of Us: Left Behind, a good chunk of which is spent in a mall. And they nailed the environment perfectly I would say.

Or for those who don't own a PS4, a more accessible example is a map in NMRIH aptly called "the museum", and few words better do it justice than to go play it yourself--that is, if you really want to know what I mean by a 'situated environment'.

What better way, during this pandemic, to get out of the news cycle and into your own head? Sometimes the best way to escape isn't outside, it's within.

1000!
Love to all of you grumpy people.

I chose my next milestone as a dev. I’m gonna ask a question on stackoverflow. I just need a question 🤔

Completely forgot to update what was going on with my potential role shift. Long story short, it was approved by the damagement. That’s nice.

I only have to get to a major milestone in my current giant of an IaC project and transfer enough knowledge to leave it in my current team mates’ hands. Looks like we’ll be there pretty much next week and I can switch at the start of 2023. Life’s good.

Finally got a project I’ve been working overtime on for the last 18 months or so ready for a 1.0 launch! Still some features we want to build in for down the line, but it’s nice to finally hit a meaningful milestone...

!Rant

That feeling when you get when you reach a milestone after hours of coding, errors and the IDE just being stupid :)

Do you guys still see the relevance of using code freezing instead of just properly managing versions, repositories and branches in a cyclical manner, given how advanced software practices and tools are supposed to be?

To give some context, the company I work for uses the complete trash project management practice of asking teams to work on a sprint basis, but there is still a quarterly milestone and code freeze to commit to and it's where shit hits the fan.

Development teams rush features at the end of the quarter because they had to commit at the very least to a 6 months in advance planning (lol?) and turns out, not being able to design and investigate properly a feature combined with inflexible timelines has high chances to fail. So in the end, features are half-assed and QA has barely any time to test it out thoroughly. Anyways, by the time QA raises some concerns about a few major bugs, it's already code freeze time. But it's cool, we will just include these bug fixes and some new features in the following patches. Some real good symver, mate!

Of course, it sure does not help that teams stopped using submodules because git is too hard apparently, so we are stuck with +10Gb piece of trash monolithic repository and it's hell to manage, especially when fuckfaces merges untested code on the main branches. I can't blame Devops for ragequitting if they do.

To me, it's just some management bullshit and the whole process, IMO, belongs to fucking trash along with a few project managers... but I could always be wrong given my limited insight.

Anyways, I just wanted to discuss this subject because so far I cannot see code freezing being anything else than an outdated waterfall practice to appease investors and high management on timelines.

Actually not a rant, I just want to share my happiness with you guys. Finally I broke out of a startup, and got accepted to an international big company. Cannot wait for the things I’ll learn there, it’s so exciting! (Yep, this is a very big milestone for me as an autodidact programmer.)

Any advice you can give to me? What was your biggest achievement so far in your carreer?

Quit “milestone smoking” 😃

Almost halfway there to reach the milestone of 1024 ++es! My day couldn't start in a better way haha :D

Make your code available for your team members, please.

So we're working on this robotics project using ROS, a framework that enables multiple nodes in a network exchange their functionality among each other through tcp connections. Each node can be implemented and executed on your own machine, and tested with dummy inputs, but in collaboration they make a robot do fancy stuff.

The knowledgebase needs data from the image processing unit, providing this data to others with semantic context to high level planning, which uses this semantic data for decision making and calling the robot manipulation node with meaningful input, to navigate the robot's components in the environment. We use a dedicated machine, which pulls the corresponding repositories and is always kept configured correctly, to run each node, such that everybody has access to each other's work when needed.

So far so good. We tried to convince the manipulation guy (let's call him John) to run his code on our central machine, not a week, but since the first day, 5 months ago. Our cluster classification has been unavailable for 2 months, but my collegue fixed that. We still can't run the whole project without John's computer. If his machine blows up we're fucked.

Each milestone feels like a big-bang-test, fixing issues in interfaces last-minute. We see the whole demo just moments before our supervisors arrive at the door.

I just hope he doesn't get hit by a truck.

Estimate how long it will take you then double it. After that split the project into milestones and add the days you give a client to accept the milestone. If you have a good client you will get done early and refund them the difference. Otherwise you get paid well for dealing with a dumbass.

So it finally happened... A recruiter contacted me out of the blue with a long personalized message.

I'm happy with my current job and I realize a lot of are forever trying to escape relentless headhunters but 2019 and 2020 were not good years for me career wise, so silly as it seems, this is actually kinda a milestone for me

(imagine all of this said in Undoomed's "hey moron" tone)

Hey, moron, fuckin moron! How about if you're a noob with no actual programmer on your side, you just tell me so we can work it out together, instead of sending a moronic 4page "acceptance criteria" that pretend you know what you're talking about, and then bury me under loads of moronic noob questions that reveal you as thenmoron you are, all of that for a fuckin 50 quid?! I thought it's me being an idiot, not being able to do the task within two days timeframe, but now I see you're just too much of a moron to have any idea how much these things take. And now you nonchalantly mention a one-line one point from the four page document full of drivel, which (loads of moronism credit for me here) i didn't notice amongst all of that other mundane drivel, which actually like doubles the whole workload on the task, but your moronic document, which makes 3 parts of the same algorithm into three separate MILESTONES, makes this whole thing that nearly DOUBLES the workload into a shitty SEVENTH SUBPOINT of the completely unrelated first "milestone"?

FUCK YOU, YOU STUPID ROBBERY CHEAPFUCK, and fuck me for letting myself be tricked by all your fancy wordings that pretend you actually know what the fuck you are asking for, so i assumed you did, so I missed THE POINT, WHICH ACCORDING TO THE SEGMENTATION LOGIC OF THE WHOLE REST OF THE DOCUMENT SHOULD BE 3 SEPARATE FULL-SIZED MILESTONES, NOT A SINGLE SUBPOINT, YOU FUCKING FUCK!

... so much for still trying to at least a bit trust people.

FUCKING DISGUSTING MORONIC CHEAPSKATE FUCK.

and I can't even tell him to fuck off through the rectum he came here because he's all nice and polite so I would be the asshole!

"hey, please, can you build me a house?"
*house is basically finished*
"oh, great job, i love it, but i think you might have missed the fineprint in our contract that says that the house is supposed to stand inside an entry hall of a multibillionaire-sized mansion, so could we please sort that out and add it to the building real quick before i pay you the toolshed's worth we agreed on based on the contract? "

FUCK. HIM.
FUCK
FUCKFUCKFUCKSHITFUCKERYFUCKDISGUSTINGIDIOTICFUCKINGFUUUUUUUUCK!!!!!!

i thought i can be a shitty liar and a con man, but this is some next level shit that would be totally beyond my abilities to pull off...

YES I KNOW IT'S MY FAULT I DIDN'T COMB THROUGH THAT BULLSIT "SPECS" OF HIS LETTER BY LETTER TO MAKE SURE THERE'S NO CON BULLSHIT LIKE THIS HIDDEN AMONGST ALL OF THAT MUNDANE SELF-EVIDENT PSEUDO-TECHNICAL DRIVEL, SHUT THE FUCK UP.

fucking disgusting moron, pretending all nice and innocent probably even to himself because he HAS NO FUCKING IDEA WHAT HE EVEN ASKS FOR.

i bet it's one of those pukefucks who get an overpriced contract for 50k without even knowing or caring what programming is, because "i'll just outsource the core functionality of the app for 50 quid to some naiive idiot who lives in the illusion that people are not diarrhorea-worthy pieces of feces, and this other third of the app to some other moron for hundred quid and then i somehow outsource gluing it together to some third poor sod, and that's 49.8k quid of pure profit for me, yay"

and now i'm torn between three options, just cancelling the "contract" with a comment saying "fuck off, you con man", or cancelling it with a lengthy explanation why he's a know-nothing piece of shit who conned me already into having done something worth about 5x more than his shitty "acceptance criteria" requests, or just start conning and bulshitting him back, which won't net me any money, and waste my time, but at least will also waste HIS time, which might be nice because he seems to be on a tight schedule so if i play this right i might have the chance to sink his whole contract which might be mighty nice satisfying...

FUCK THIS, ALL OF THIS, FUCK HIM, FUCK ME, FUCK ALL OF YOU, I SHOULD HAVE STARTED FUCKING OVER EVERYONE RUTHLESSLY A LONG TIME AGO BECAUSE FUCK THE WHOLE WORLD, WHY SHOULD I CARE WHEN NOBODY ELSE DOES, WHY SHOULD I BE DECENT WHEN NOBODY ELSE IS, AND IT ONLY ROYALLY BITES ME IN THE ASS.

stupid fucking lobotomized fuck, IF YOU DON'T KNOW HOW TO DO SOMETHING, DON'T OFFER YOURSELF TO DO IT FOR MONEY AND THEN CON-SOURCE IT TO OTHERS YOU SHITTY BARFPILE!

FUCK.

When I reach my short term milestone, I might start dedicating my full-time to one of the following projects:

1. deno
2. brain.js
3. The forking of TypeORM
4. The teardown of Isaac Schlueter
5. Create a full on movement to rescue open source

is it better to work on a project every day even when i dont feel like it but then do like 80% of the work for the next milestone with a shitty code (done alot faster)

or

work on a project when i have the will to work on it but then do 30% of the work for the next milestone with a clean code? (done alot slower)

!rant

My employer is a subcontractor on a big and rather complex project, that already is way behind schedule and over budget (as these monsters tend to be). To get back some confidence from the client our principal moved an important milestone up two weeks. Which we protested against vehemently because the projected workload was already a very tight fit for the original timeline, without any reserve to speak of left. They wouldn't listen though...
The result? The whole team has to work the next weekends to have even the slightest chance of making the earlier timeline. Which is exactly what we told them would happen when they moved the milestone.

The worst? This isn't the first time this has happened while I worked on the project 😑

SQA here.

What do you even do when dev, other senior QA, your boss and management all give conflicting requirements for a big milestone planning while still ramping up?

My instinct tells me to do what my boss and dev tells me and to come up with the solution that makes the most sense.

No we don't have a product owner ffs. It's like a bizarre waterfall scheme. I have figure out this on my own and hope I made no big mistakes because the ones with the knowledge are unavailable to help. Been thrown in this shit and it's been 3 months I work here. I am honestly trying my best to filter the best out of this.

#Suphle Rant 5: Xavi

When I first detailed what it was I was working on to my brother and its expected impact on the industry, I must have done so with an enormous amount of enthusiasm that he impatiently began to request when the dream will be realised. He didn't give a shit about specifics of where I was on the timeline. He kept repeating the same question. Exasperated with the futility of my explanations, I replied that I'd be done by November as this was far beyond my estimated completion date

Every milestone (e.g. my birthday) I've expected it to be ready at has come and gone, including the unrealistic November. My present state of mind is far from the optimistic pioneer I was then. I'm just going with the flow and won't be surprised if it's not officially released by the end of the year

This gonna be me in 2072, convincing anyone who cares to listen that I'm fleshing out the docs and that the reason the release date keeps getting pushed back is because nobody has shown interest in either using or contributing to it

The iron glows. Now we'll shape it.
- Me, Today. As reaction to a reached milestone.

!dev
I feel like I hit a milestone yesterday - a post of mine was used by a farming bot on Reddit lol

#Suphle Rant 8: Strange star discovered

I was searching for a project I'd starred earlier, on my github feed, when I realised a user had starred suphle at some point but for some reason, it wasn't reflecting on the stargazers. I was half overjoyed and half confused. Overjoyed over unlocking the milestone.

User seemed legit –an Italian with projects in C that were not forked. Followers and commit graph are organic. Did he star in error, feel the project is a stinker, or encounter installation challenges? Luckily, I found his email address but all his repositories are in Italian so I wasn't too sure he'd understand English, or if the mail was being attended to. Yet, I took my chances

He surprisingly got back to me, affirming that the star-unstar was actually deliberate. He withdrew the star cuz project's documentation is not hosted online and still requires npm start.

I try to persuade him by reminding him it's just a one liner but that markdown files are equally rendered directly on github. Never heard from him again, sadly

I'm kind of bothered cos I find it funny I thought suphle's APIs are all cast in stone, but the more I work on the docs, the closer I am to spotting something that doesn't sit right with me, and diving in to modify it. This not only prolongs ETA, there's the risk of someone who may have stumbled upon it and is studying it, having the rug pulled from under their feet. Things like validator rules and route-collection service-coordinators have been converted from methods and classes to native decorators. I guess I'm safe since nobody has indicated any signal to the contrary. It'll be pedantic to start tagging versions for each change.

Another consideration is that these breaking changes would go to the first segment of the semver scheme, which is hilarious because the rate at which I push such changes is so alarming, we'd probably progress through 15 versions under a year

What's your routine for versioning pre-releases?

While working on a big change, like "milestone 2.0", how do you, while working on it, version it before the main release? To keep it being 2.0.0 on release and not for example 2.130.0 (since it was "2.130.0-pre" just before release)?

Or is it my fantasy that when released to public it "should" always be *.0.0?