Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "project award"
-
A tool I built for my past company just got nominated for a European Data Science and AI award!!!
I'm over the moon that something I built is up for such an award. Be early next month before winners are announced. Oh and given I don't work there anymore, how I was told about it is a REALLY funny story .... I wasn't.
Saw a Linkedin post from my ex-manager congratulating the company and the org for great work done. He/They just forgot to mention the fact that me and another ex-employee did everything, left it practically finished and completely changed the direction of the project within the first month as their plans made no sense.
fuckers.8 -
Professor in college: We have our fest coming up. We need some volunteers for technical team to build website and android app.
*She says that and looks towards guys. Some guys raise hands saying they were interested.*
She didn't look towards girls even though some girls were raising their hands too.
Then she looked at girls finally....and she said "Oh you girls are interested too? We have cultural and decoration team. You can join that. "
I was triggered to next level.
I stood up and asked "Can't girls be part of technical team?"
She said "oh...yeah sure...." With not much hope that I would get into technical team.
But I ended up passing the screening round and got into technical team. She realised at that time that I knew my shit.....
There was even a time when I was in HODs office and she pointed at me and went "She is my student." trying to take credit for me being so Awesome ;)
LOL!
She was my guide for final year project too. We ended up writing a research paper and won best project award as well.
This was a year back. I have graduated and now I am working....
Just remembered....19 -
Obviously this year. I went from KDE Neon (bloat ree) to Arch, learnt Git, Golang, vim, some JS, did my first major public project (asl), learnt how to package python stuff, did my first collab (private repo with a friend), did my first public collab (animator), made 225 contributions on GitHub (so far), won the "Most Technical" award in my Science Fair, went on climate protests, and sh*t-tons more.
And I joined devRant!
I'm excited for 2020!1 -
Who would have thought that Ben Award's VSCode stories would be sold at 9000$. That's almost my entire college fees for 4 years.3
-
My worst team experience finished only a week ago:
- Be me
- be averaging 80% in completed modules and on track for a 1st
- have to take a team project worth double credits
- get stuck in random team with 40%ers
- lose 1 artist at the start (team of 12: 6 artists, 6 programmers)
- 2 artists contribute nothing and disappear for a few weeks
- I'm forced to do level design to have something to show (looked good tbh)
- weeks go by and too many contribute very little.
- by the end the team was basically 4 programmers and 2 artists contributing.
All other teams basically get an easy 2:1/1st just because their team turns up and contributes.
I could lose a 1st because of this module bringing down everything else, it also had a huge effect on what I could achieve for my dissertation due to time.
- did get an award at the end for managing to not kill someone and showing restraint 😂😂
Basically don't choose a degree where more than 25% of your mark is almost entirely out of your hands.
The small individual component I averaged over 90%! -
We're having a favorite hackathon projects vote at work tomorrow. Basically each team are given 5 minutes to present their project and we'll vote the most interesting project for a favorite project award.
I'll give my vote to whichever team confuse me the quickest.2 -
It's was the forth year of my college, in the corner of the world in south India, I wanted to something to combine both medicine and the coding that I learnt, I started learning about heart murmurs, it's basically a skill based diagnosis that only 1 in 20 heart specialists can make by hearing the heart beat and listening to a small murmur that happens during the systolic cycle or the diastolic cycle. I wrote a program to learn a lot of sample murmurs and try to find (very bad hand made logic) the similarities between two wave patterns, the problem started with noise so I went out and built a new stethoscope with a carbon mic inside a normal stethoscope head and try filtering the sound at source (worked well enough at that time) I then tried to find people to test it on, but alas I was not able to find patients as doctors are not supposed to reveal them etc. I wanted to show them visually how a murmur pattern would look like and I stole some code and made a plotter for the wav file and presented everything. By that time I got a lot of close amazing friends involved and they helped me solidify the project and we won the best project award and I got my first gold medal of my life at the end of my academic life :) it was one of the best moments of my life. Second only to the joy of getting married to wife. May be third if I put getting a job in Microsoft India Development Center.
I still wish I could dig that code up and write it properly with what I have learnt today but work is never ending and I find great problems to solve everyday which I know I can make a difference, may be when I get retired I will dust out that CD with the decades old c++ code and write one last program...3 -
Rant
Team lead has no idea whats going in project , who is doing what work , nothing at all. Come to our team once a week and got award for successfully managing the project.
Real bullshit4 -
A record system containing student's information. A project given by my teacher so that I could get the "Best in Computer" award in my school. He helped me to get that award because my school was unfair in giving chances for other students not in the top class to get the award. Unfortunately, I didn't pass it on time. Even if I was the highest in computer in my level, I didn't get the award just because they never gave me a chance
-
Story of my first successful project
Being part of a great team, I've shared in a lot of successes, one I am particularly proud of is my first attempt to use agile methodologies in a deeply waterfall-managment culture.
Time was June/July-ish and we applied for a national quality award where one key element in the application stated how well we handled customer complaint resolution.
While somewhat true (our customer service is the top-shelf good stuff), we did not have a systematic process in resolving customer complaints. Long story short,
the VP lied on her section of the application. Then came the 'emergency', borderline panic meeting (several VPs, managers, etc) to develop a process to better manage
complaints before the in-house inspection in December.
As most top priority projects go, the dev manager allocated 3 developers, 2 DBAs, and any/all network admins we would need (plus all the bureaucratic management that wanted their thumb in the pie).
Fast forward to August, after many, many planning meetings, lost interest, new shiny bouncing balls, I was the only one left on the project. The VP runs into the dev manager in the hallway and asks "Is my program done yet? If its not ready before December with report-able data, we will not win the award."
The <bleep> hit the fan...dev manager comes by...
Frank: "How the application coming along? Almost done?"
Me:"No, haven't really started coding. You moved Jake and Tom over to James's team, Tina quit, and you've had me sidetracked helping other teams because the DBAs are too busy."
Frank: "So, it's excuses. You really think the national quality award auditors care about your excuses? The specification design document has been done for months. This is unacceptable."
Me: "The VP finished up her section yesterday and according to the process, we can't start coding until the document is signed off."
Frank: "Holy f<bleep>ing sh<bleep>t! No one told you *you* couldn't start. You know how to create tables and write code."
Me: "There is no specification to write to. The design document is all about how they plan on reporting the data, not how call agents will be using the application to serve customers."
Frank: "The f<bleep> it isn't. F<bleep>ing monkeys could code against that specification, I helped write it! NO MORE F<bleep>ING EXCUSES! This is your top priority from now on!"
I was 'cleared' to work directly with the call center manager and the VP to develop a fully integrated customer complaint management system before December (by-passing any of the waterfall processes that would get in the way).
I had heard about this 'agile' stuff, attended a few conference tracks on the subject, read the manifesto, and thought "I could do this.".
Over the next month, I had my own 'sprints' and 'scrums' with the manager (at the time, 'agile' was a dirty word so I had to be careful of my words and what info I shared) and by the 2nd iteration had a working prototype.
Feature here, feature there (documenting the 'whys' and 'whats' along the way), and by October, had a full deployed application.
Not thinking I would get a parade or anything, the dev manager came back from a meeting where the VP was showing off the new app to the other VPs (and how she didn't really 'lie' on the application)
Frank: "Everyone is pleased how well the project turned out, except one thing. Erin said you bothered him too much with too many questions."
Me: "Bothered? Did he really say that?"
Frank: "No, not directly, but he said you would stop by his office every day to show him your progress and if he needed you to change anything. You shouldn't have done that."
Me: "Erin really seemed to like the continuous feedback. What we have now is very different than what we started with."
Frank: "Yes, probably because you kept bothering him and not following the specification document. That is why we spend so much time up front in design is so we don't waste management's time, which is exactly what you did."
Me: "We beat the deadline by two months, so I don't think I wasted anyone's time. In fact, this is kind of a big win for us, right?"
Frank: "Not really. There was breakdown in the process. We need better focus on the process, not in these one-hit-wonders."
End the end, the company won the award (mgmt team got to meet the vice president, yes the #2 guy). I know I played a very small, somewhat insignificant role in that victory, I was extremely proud to be part of the team. -
After the long haul of designing, structuring and finally implementing, my side project is done. The only challenge I faced was to not lose interest or get distracted :p
I made this to get a hang of haskell. It adds haskell functionality to your shell and lets you apply functions to outputs of other programs(ls,ps,df etc)
https://github.com/iostreamer-X/...
Your honest feedback is highly valued.
Thanks!
:D -
So there is this project from hell that ive been working on for 6 months...
We have won an award for it. First reaction when i heard it was nominated was: Do you think i’m happy with this? This project has taken blood sweat and tears goddammit.
But today the actual piece of glass came in. I can’t help but to feel proud. -
Aka... How NOT to design a build system.
I must say that the winning award in that category goes without any question to SBT.
SBT is like trying to use a claymore mine to put some nails in a wall. It most likely will work somehow, but the collateral damage is extensive.
If you ask what build tool would possibly do this... It was probably SBT. Rant applies in general, but my arch nemesis is definitely SBT.
Let's start with the simplest thing: The data format you use to store.
Well. Data format. So use sth that can represent data or settings. Do *not* use a programming language, as this can neither be parsed / modified without an foreign interface or using the programming language itself...
Which is painful as fuck for automatisation, scripting and thus CI/CD.
Most important regarding the data format - keep it simple and stupid, yet precise and clean. Do not try to e.g. implement complex types - pain without gain. Plain old objects / structs, arrays, primitive types, simple as that.
No (severely) nested types, no lazy evaluation, just keep it as simple as possible. Build tools are complex enough, no need to feed the nightmare.
Data formats *must* have btw a proper encoding, looking at you Mr. XML. It should be standardized, so no crazy mfucking shit eating dev gets the idea to use whatever encoding they like.
Workflows. You know, things like
- update dependency
- compile stuff
- test run
- ...
Keep. Them. Simple.
Especially regarding settings and multiprojects.
http://lihaoyi.com/post/...
If you want to know how to absolutely never ever do it.
Again - keep. it. simple.
Make stuff configurable, allow the CLI tool used for building to pass this configuration in / allow setting of env variables. As simple as that.
Allow project settings - e.g. like repositories - to be set globally vs project wide.
Not simple are those tools who have...
- more knobs than documentation
- more layers than a wedding cake
- inheritance / merging of settings :(
- CLI and ENV have different names.
- CLI and ENV use different quoting
...
Which brings me to the CLI.
If your build tool has no CLI, it sucks. It just sucks. No discussion. It sucks, hmkay?
If your build tool has a CLI, but...
- it uses undocumented exit codes
- requires absurd or non-quoting (e.g. cannot parse quoted string)
- has unconfigurable logging
- output doesn't allow parsing
- CLI cannot be used for automatisation
It sucks, too... Again, no discussion.
Last point: Plugins and versioning.
I love plugins. And versioning.
Plugins can be a good choice to extend stuff, to scratch some specific itches.
Plugins are NOT an excuse to say: hey, we don't integrate any features or offer plugins by ourselves, go implement your own plugins for that.
That's just absurd.
(precondition: feature makes sense, like e.g. listing dependencies, checking for updates, etc - stuff that most likely anyone wants)
Versioning. Well. Here goes number one award to Node with it's broken concept of just installing multiple versions for the fuck of it.
Another award goes to tools without a locking file.
Another award goes to tools who do not support version ranges.
Yet another award goes to tools who do not support private repositories / mirrors via global configuration - makes fun bombing public mirrors to check for new versions available and getting rate limited to death.
In case someone has read so far and wonders why this rant came to be...
I've implemented a sort of on premise bot for updating dependencies for multiple build tools.
Won't be open sourced, as it is company property - but let me tell ya... Pain and pain are two different things. That was beyond pain.
That was getting your skin peeled off while being set on fire pain.
-.-5