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 - "ux future"
-
Unpopular opinion about Microsoft buying GitHub.
Just putting it out there that when you made your github repos you did so under their privacy policy and terms and will be protected under those in the future, and that both GitHub and Microsoft are corporations with the goals of making money.
Are people seriously mad that their code has gone from one capitalist corporation to another, with no foreseeable change in privacy or data policy? I have respect for those that switched to self hosted long ago since that's going from corporate to private, but if you throw away the UX and community GitHub has developed because a multinational corporation (with so many branches, products and divisions, which happens to have a few products you don't like) will soon own it, are you actually making a rational, guided decision?
Also just throwing it out there that GitLab is also a company. They've also had issues with keeping data intact in the past. They do, however, have free private repos (although I can't ever trust someone who gives me "free" privacy) as well as builtin CI. There are some definite upsides to it, although the UX has a ton of differences. If you're expecting the same dashboard and workflow you've used on GitHub, don't, GitLab has cool features but the bells and whistles aren't the exact same.
If you're switching to GitLab solely because of Microsoft, step back and think, regardless of how popular it might make you to hate Microsoft, is it really worth changing your development ecosystem to go from one corporate entity to another solely because you don't like the company?
I use GitLab and GitBub as well as Bitbucket and selfhosted git on a daily basis. They each have their upsides and downsides; but I think switching from one to the other solely because of Microsoft is not only totally irrational, but really makes light of/disrespects the amazing tools and UX the teams behind each one have carefully developed. Pick your Git hosting based on features and what works out for your use case, not because of which corporate overlord has their name plastered on it.
(Also just throwing it out there that lots of devs love VS Code, and that's Microsoft owned too... They did also build and pioneer a bunch of really cool shit for devs including Typescript so it's not like they're evil or incapable in any sense?)11 -
I wish all open source desktop applications had the same combination of expert features and polish as Blender.
The state of FOSS applications for creating diagrams, DB management & ERD, drawing SVGs, editing video, slideshow presentations, document processing, etc -- Yeah just all of it seems to be either stuck in some 90's UX paradigm, or it's a basic-as-fuck Electron app with 12 buttons for toddlers.
I know... I know... it's FOSS, can't be entitled.
But there's a part of me that really wants to be.
Fuck it, I'm just going to be entitled.
FUCK YOU LAZY FOSS DEVS, GET YOUR FUCKING SHIT TOGETHER AND MAKE SOME MODERN APPS. THROW YOUR GTK TOOLKIT BULLSHIT IN THE TRASH, GO CHOKE ON YOUR RETARDED WINDOWS-95 THEMED TOOLBARS, AND START MOTHERFUCKING COMPETING. YOU'RE BEING SURPASSED BY VENDOR LOCKED $50/MONTH CLOUD ABOMINATIONS MADE FOR COKE SNORTING DIMWITS. DON'T GIVE ME THAT "BUT PEOPLE WORK ON IT FOR FREE" CRAP, IF BLENDER CAN MAKE A GREAT COMPETING PRODUCT THEN SO CAN YOU.
Ah, completely unjustified and unfair.
But it still feels really, REALLY great to get it off my chest.
Now that I have descended from my soapbox, I'll go drag my useless developer ass over to the nearest FOSS project and see how I can contribute to a slightly less depressing future.15 -
- Project for a 40+b$ company.
- No business analysis.
- Only some 64 pages tech paper dividing the project in 4 iterations (pretty well written).
- « Please estimate the first iteration ».
- Can we do it in 2 weeks? Only items in first iteration, I think we can but we need a BA before we accept the project.
- Confirmed by senior dev front. 10 days, says we need a BA before we accept.
- Confirmed by senior dev back. 12 days, says we need a BA before we accept.
- UX/UI senior designer says he can't estimate such a technical, says we defo need a BA before any estimations.
PM, who is actually the department manager, says OK we can do it. No BA and estimations are halved, UI/UX 2 days.
He fucking signs the contract.
SURPRISE MOTHERFUCKER, WE NEED STUFF FROM FUTURE ITERATIONS IF WE DON'T WANT TO THROW AWAY ALL THE FIRST ITER WORK.
PROJECT BECOME A CLUSTERFUCK.
NOBODY UNDERSTANDS ANYTHING. THE CLIENT HAS NO CLUE EITHER.
The fucking dep. mgr assigns another PM and says he don't have time anymore.
NOBODY HAS A CLUE WHAT THE PROJECT IS AT THIS POINT.
We have 3 days left.
Whole team came to a conclusion: the only sane thing to do is to give our grouped resignation letters.
Thanks. It was fun while it lasted. Your dep. can go to hell.5 -
Team: Qt doesn’t let us build the UX we have in mind. Web is the future.
Me: what do you guys recommend ?
Team: Electron! We vote for Electron!
Me: Alright, who know JavaScript here?
Team: ...9 -
devRant collaboration project - a lot of us are thinking of doing a project or projects in the future. I am sure some valuable partnerships will be forged.
My desire is to do something that can make a positive impact in people's lives. Possibly to help people with special needs.
I am thinking about code that extends into the physical world - an Internet of Things project sort of a devThing.
Brainstorming a bit deeper - maybe a mashup of off the shelf components - maybe using Raspberry Pi or the $5 Raspberry Pi. Keep it low cost so everyone can afford it. As an aside CubeSats powered by RP's are being used in outer space saving a great deal of money and providing value.
The great thing is devRant has great coders, graphic design, ux, Raspberry Pi (or similar miniaturization), public relations to get the word out...
I have some examples we can use for inspiration. Let's keep building on this.40 -
Okay so I have a lot of experience in UI/UX, graphic design, and Front End dev, but I hate it. My github and resume are full of front end shit because it makes up most of my experience, and so when I apply to software dev things I often don’t get interviews because of lack of exp.
Well today I got an email from a big company that I applied to over a month ago and they told me that I was an excellent candidate and that they’d like to interview me. I say “the position is still open? I applied over a month ago!” to which they respond “well, the position you applied to has closed, but we are looking to hire a UX developer and had your application in our UX pool of applicants”
I did not fucking apply for this. They saw my application and threw it into the pool for future UX gigs and I’m mad because I’m not in a position to not interview for this job but I also really want to work in software.
Do you think, assuming I got the job, that it would hurt my prospects further to work in UX?3 -
!rant
I'm a developer turning into product designer guys. But I'll never forget my roots, my development origin. What I'm learning is, most of the UX designer are ignorant about development and developers in general and many developers are ignorant about usability. My future aim would be to build a well communication bridge between these two entities and get designer to empathize with developers and vice versa.13 -
F*CK...that feeling when you were working as a junior UI/UX designer for about 3 weeks in new company, you were on a project which is almost finished and delivered...
1 and half week Later (after technical issues - check my older rants)......
you have noticed one quite importat mistake in the designs, which were done by senior designers, which can lead in future to a huge Ux problems - so huge, that users will probably leave/close the app and will not purchase the product via that app... ( We can say than whole design solution was a waste of money for the client)... On that designes was working a team of 4 people, about 3 Months (and the app (prototype) had to be ready already 2 Months back)...
the deadline was pushed 2x already...
And your boss (senior designer) tell you that this is not such an issue.. But thx for your opinion.....
1 week Later by user testing 4 out of 4 people were asking about that stuff I told to my boss that is missing...
And I was ignored...
In less than 1 week Later after the testing I get fired from the company without no reason...
Or better - the reason was:
I have too little experiences for this job...
Dont know if I should laugh or cry🤦♀️🤣/😭8 -
We are 2 people working as remote android devs for this startup in another country. 6 weeks ago a new person joined onsite to work directly in startup HQ. I'l refer to him as an newguy.
Last week we started new sprint (of 2 weeks) to work on a new feature.
Newguy was responsible for gathering all the specs and planning, so this is how our sprint is going so far:
Day 1:
We have 10+ tickets in jira (tickets have only titles) no one knows what to do and we don't even have specification. I started pushing everybody onsite to get their shit together. We NEED UX/UI specs, we NEED backend to be ready, or at least start working paralelly so that once wer'e done with frontend backend would be ready. I mean cmon guys this feature is already 70% done on iOS, why cant you send us the specification?
Day 2:
We had a meeting on Zoom and talked about missing specification and project manager promised to send us the specs. Meanwhile the idea of feature became clearer so I agreed with the newguy to start researching about best way to implement our solution.
Day 3:
We received the specifications. I provided my research for the feature to the newguy. Turns out the he knew about specification 4-5 days before.
Instead of sharing information with us, he decided to create his own library to do what we want to do and blatantly rejected my research input.
Now he showed his implementaton (which is shit by the way) and presents it as the only way to proceed forward. He offers for us to work paralelly with him on this (basically he wants to write library alone, and we are supposed to somehow implement and test it, but how the fuck we can implement if backend is not ready and library is just a bunch of empty interfaces at this point?)
I talked with one of the teamleads in the startup and told him that this is not the way things were being done here before and new guy is becoming a dictator.
Teamlead talked with new guy and found no issue. Basically newguy defended his sole decision by saying that he did research on his own, there are no libraries that do what we want and he knows better.
Teamlead tells me to STFU because new guy seems competent and he will be leading this feature. Basically from what I gathered teamlead doesn't give a single fuck and wants to delegate all project management to this new guy.
Day 5:
End of the week. New guy claims that his lib is done so we can start implementing properly. I tried implementing his lib but its fucked up and backend is still not ready.
Day 6:
Backend is still not ready, no one is doing anything just waiting for it to be ready.
Day 7 (Today):
Today(Backend is still not ready, no one is doing anything just waiting for it to be ready.
So what can I say? His plan was to probably prove his self worth and try to lead this feature by giving us information at last minute. At the point were we should start implementing instead of researching.
What happened? Motherfucker doesn't know shit about backend, has been notified about backend issues multiple times but his head was so deep up his ass with that new library of his that he delayed the rest of the team.
Result? 7 working days wasted. Out of 3 developers only 1 was actually working (and his fucked up code will have to be rewritten anyways). Only 50% of feature done. Motherfucker tells me that this is how we will work in the future, "paralelly". The fuck is this mate? If you would have worked on this feature alone you would have done it already now, but instead you wait until we remote devs will login and fetch you the test input and talk with backend guys for you? The fuck is wrong with you.
You fucking piece of shit, learn to plan and organize better if you want to lead the team. Now all that you are doing is wasting time, money and getting on everyboys nerves. Im tired of fucking spoon feeding you every day you needy scheming office politics playing piece of shit. Go back to your shithole country and let us work.
When I was responsible for sprint planning I figured out what to do before start of the sprint and remote devs were able to do week's work in 1-2 days and have rest of the week off. This is how it's supposed to be when you work with a remote team. Delegate them separate features, give them proper specs ahead and everyone's happy. Don't start working on frontend if you dont even fucking know when backend will be ready. It's fucking common sense.
Now I need to spoon feed this motherfucker who can't even get information while sitting on his ass onsite in HQ. Fucking hell.8 -
Hey this is the first time i post here.
I just started working part-time for this company last week. What i have to do is to change some windows from Win32 to WPF. As i was reading the legacy code i just had to sigh man. They have like 100 projects in a single solution, from C++ to C#, everything acctached to each other, with almost NO comments or docs. Wtf man? I don't know how it actually works in the industry (this is my first dev job) but when you write fucking 20 classes with each one contains bunch of attributes, methods, properties, you can't just leave all the code's semantics in their names. And by the way the app is so fucking ugly i bet they have appointed part-time developers as UX engineers... Even i have little knowledge about UX/UI, i just can't bear with this kind of ugly and confusing and unintuitive production with a cost of a good photo editting software.
Ok there may be much more to rant in the future but let me try through this and tell you more. Have a good day. :)5 -
It sometimes really sucks to see how many developers, mostly even much better than me, are too lazy to implement a function to its full UX finish.
Like how can you not implement pagination if you know there's going to be fuck ton of content, how can you not allow deleting entries, how can there be no proper search of content, but instead some google custom search, how can you not implement infinite loading everywhere, but only in parts of your application, how can you not caching a rendered version or improve the page, that loads EVERY SINGLE ENTRY in your database with 11k entries, by just adding a filter and loading only chunks of it.
I know sometimes you need to cut corners, but there's rarely any excuse with modern toolsets to just write 3 lines more and have it ready for such basic things.
I sometimes just wake up during the night or before falling asleep and think "oh, what if in the future he might want to manage that, it's just another view and another function handling a resource, laravel makes that very easy anyway", write in on my list and do it in a blink the next day, if there's nothing else like a major bug.
I have such high standard of delivery for myself, that it feels so weird, how somebody can just deliver such a shitty codebase (e.g. filled with "quick/temporary implementations"), not think of the future of the application or the complete user and or admin experience.
Especially it almost hurts seeing somebody so much more versatile in so many areas than me do it, like you perfectly fine know how to cache it in redis, you probably know a fuck ton of other ways I don't even know of yet to do it, yet you decide to make it such a fucking piece of shit and call it finished.2 -
A tale of silos, pivots, and mismanagement.
Background: Our consultancy has been working with this client for over a year now. It started with some of our back-end devs working on the API.
We are in Canada. The client is located in the US. There are two other teams in Canada. The client has an overseas company contracted to do the front-end of the app. And at the time we started, there was a 'UX consultancy' also in the US.
I joined the project several months in to replace the then-defunct UX company. I was the only UX consultant on the project at that time. I was also to build out a functional front-end 'prototype' (Vue/Scss) ahead of the other teams so that we could begin tying the fractured arms of the product together.
At this point there was a partial spec for the back-end, a somewhat architected API, a loose idea of a basic front-end, and a smattering of ideas, concepts, sketches, and horrific wireframes scattered about various places online.
At this point we had:
One back-end
One front-end
One functional prototype
One back-end Jira board
One front-end Jira board
No task-management for UX
You might get where this is going...
None of the teams had shared meetings. None of the team leads spoke to each other. Each team had their own terms, their own trajectory, and their own goals.
Just as our team started pushing for more alignment, and we began having shared meetings, the client decided to pivot the product in another direction.
Now we had:
One back-end
One original front-end
One first-pivot front-end
Two functional prototypes
One front-end Jira board
One back-end Jira board
No worries. We're professionals. We do this all the time. We rolled with it and we shifted focus to a new direction, with the same goals in mind internally to keep things aligned and moving along.
Slowly, the client hired managers to start leading everything in the same direction. Things started to look up. The back-end team and the product and UX teams started aligning goals and working toward the same objectives.
Then the client shifted directions again. This time bigger. More 'verticals'. I was to leave the previous 'prototypes' behind, and feature-freeze them to work on the new direction.
One back-end
One conceptual 'new' back-end
One original front-end
One first-pivot front-end
One 'all verticals' front-end
One functional prototype
One back-end Jira board
One front-end Jira board
One product Jira board
One UX Jira board
Meanwhile, the back-end team, the front-end team overseas, all kept moving in the previously agreed-upon direction.
At this stage, probably 6 months in, the 'prototypes' were much less proper 'prototypes' but actually just full apps (with a stubbed back-end since I was never given permission or support to access the actual back-end).
The state of things today:
Back to one back-end
One original front-end
One first-pivot front-end
One 'all verticals' front-end
One 'working' front-end
One 'QA' front-end
One 'demo' front-end
One functional prototype
One back-end Jira board
Two front-end Jira boards
One current product Jira board
One future product Jira board
One current UX Jira board
One future UX Jira board
One QA Jira board
I report to approximately 4 people remotely (depending on the task or the week).
There are three representatives from 'product' who dictate features and priorities (they often do not align).
I still maintain the 'prototype' to this day. The front-end team does not have access to the code of this 'prototype' (the clients' request). The client's QA team does not test against the 'prototype'.
The demos of the front-end version of the product include peanut-gallery design-by-committee 'bug call-outs', feature requests, and scope creep by attendees in the dozens from all manner of teams and directors.4 -
Got rejected for an UX designer position turns out they were realy looking for a UX tester with project leadership skills 🤗 does that even mix bro???
Note to self 🤔 never apply for jobs there in the future 🤔1 -
@dfox @trogus
Kinda’ NOT(x+x) = rant, but still would like to have some way of direct message system in the app, i guess it will be added in the near future but im getting more frustrated by the hour when not being able to communicate directly with a user without a mention publicly and offtopic’ing the main rant’s subject.
Another thing would be cool to have the app in landscape mode without losing its ui/ux integrity. Think “iphone 6” ergonomics when at restful position.
Just realized how monstrous this app could get and be if the team grew and started implementing shit ton of APIs to connect and centralize every coding dev scheme.
And not sure if its okay or not but, I just mentioned myself! XD iMessages dejavu?3 -
Hi there everyone am Shreyas a CS student. Am a C# guy and learn the parts of language every day (recently learning Asp.net) and having a lot of intrest, knowledge and passion in buildling stuff in it with WPF, Xamarin. And also i do practice a lot in it everyday.
But recently I am getting a lot more intrest in UI/UX designing. Am finding myself watching more UI/UX designing (mostly in Adobe Xd and illustrator) videos on YT (dansky YouTube channel specifically) rather than C# which I used to watch in early days.
So what is your suggestion on it? Should I learn the UI/UX designing basics. Will it help me in future, if I become a developer on building applications for mobile and desktop in C#?
Am pretty confused with it? Should I learn it or not?2 -
Whatever be the current trend on Linked-In, at the end of the day the product development life cycle remains quite the same.
Still, as developers which general domains in software do you think would flourish in the near future?
My picks (not in order) -
>> Cyber security : automation, both offensive and defensive
>> Block chain : trustable data platforms
>> Applied AI : a few key models, applied to all niches, bettering existing UX
>> IOT : wearables, embeddables, smart appliances
>> AR : Navigation prompts, real time info about real life objects
>> VR : Immerse entertainment. (Metaverse 🤮)
>> Quantum computing : first gen costly commercial releases, new algos
What would you add or subtract from this?1 -
I'm finishing my secondary school in a few months and I'm currently unsure what exactly to do after school.
I'm pretty sure I want to become a software developer (maybe frontend UX/UI focused) already but I'm unsure what path to pursue.
As I live in Germany I have the options of either vocational training or studying at a University.
I'm pretty fed up with theoretic work and school right now so I'm tending towards vocational training as it incorporates one or two days of school with working in a company for the rest of the week.
The issue is that I will complete my A levels and therefore be eligible for university education in most relevant courses and have the feeling of wasting possible success in my future career (and maybe life experiences) if I just do the
vocational training.
As most developers here have a long experience as devs I'd like to ask you for advice.
Would you suggest studying something like applied computer science etc. to achieve a successful software developer career and higher wages or is experience more important than higher formal education at university for a developer?4 -
I tell a designer at the company to take a look at a (huge) corporate web project we're currently building. He's not assigned to the project, but I thought a fresh eye and recommendations could be good for future Sprints, since we're doing a first release in a month.
The guy knew all of this, yet his "designer a.k.a artistic spirit" couldn't hold him from sending a UI/UX review to the PM, of about 6-7 pages or smth - I dont even remember now.
The whole report had a total misunderstanding of the business logics, because he didn't even wait for me to explain that shit to him. Eventually his versions of UX suggestions were irrelevant. It was pretty funny, now that i think about it.
I'm guessing he just hoped to get some attention...?
tldr: its fucking disgusting when designers try to act as artists;2 -
..that time when you close the wrong window, because the computer *still* hasnt learnt what window on what monitor you were looking at, when you hit that shortcut
-
How difficult is it to decide for your own future?
It's a month that I'm in total panic 'cause of a difficult choice I have to make about my job.
I really need some external opinions and points of view from other developers, maybe more experienced than me (I'm a medium-junior JS developer).
The situation is as follows:
1) I work as a Frontend Web Developer for a wonderful enterprise-like company with 100+ employees, where the individual rights are fully respected, there are no whatsoever pressures and there is a peaceful paradise-like atmosphere most of the days. I also love my teammates, which is something rare because I often dislike other humans.
2) I received a proposal from a Fintech startup, which required me a long time to complete a complex programming test they gave me. They look all very young, modern, fast and passioned about their job. But they are only living with bank's investments and are not producing any money at the moment. Also, I don't know if Fintech will be a successful field in the future.
3) I received another proposal, from a Healthtec startup this time, which has a lovely mission in the medical field, has received millions of investments, it's gaining some KK net each month but has a team of only 2 developers (3 with me if I accept). I know one of the developers and I remember he had issues of not getting paid months ago.
What's the problem with the first company? I totally dislike the product we are building, the development stack (fully Microsoft-based), the company's view (they still sell and think about software like in the 90's) and how the repository is managed. Everyday there are huge problems that end up blocking the frontend work and the final product is super ugly and works only if you know all the quirks behind it.
It's an old-fashioned desktop app with inside Chromium which should execute some components like graphs, tables, forms and shit like this. Every component is configurable through a property editor which is an utter giant mess of collapsed menus. I also suspect that the company's main business model is based on the difficulty to use this software (because they sell licenses and courses to use it).
There are no modern UX/UI concepts applied at all, nor they seem to care about it.
Each time I propose something there is a huge chain of approval-waiting that end up in a stale mate.
Also, it's useless to show my frustration about all these issues because I count very little in a so populated office.
------------------------------------------------
TLDR: I need to choice if staying in a Enterprise Microsoft-based and old-fashioned company, but in which the atmosphere is paradisiac or accept the risk to work for a Fintech or a Healthtec startup.
------------------------------------------------
What would you do if you were in my situation? What's for you the most stable field in the future?
Many thanks for the attention!6