What is DEP?
As we have PEP in the python community (Python Enhancement Proposal), it might be a nice idea to have some DEPs (Dev Enhancement Proposals) from the dev community.
How would this DEP look like?
In a nutshell, it would be a mere of:
- Current
- What I like.
- What I don't like.
- Future
- What I hope to see.
- What I hope to not see.
So let's start!
What I like
- Dev nature
I see dev as "Facebook for developers", you communicate with developers, share ideas with devs, crack jokes with them, and most importantly know the trends of developing.
- Super fast
Dev brings great user experience when searching/browsing, today I was searching about the testability of serverless architecture, so I wrote "tdd serverless" and voila it brought the result in the very exact second!
What I don't like
- Notification links
When you open a notification on someone-has-commented, you click on it and darn! it opens a small window of his comment, you wanna check/read the context of his comment, you open the full topic and play the scrolling game to reach his comment... duh !
Why not opening his comment in the full topic window and auto-scroll to it, then do some yellow highlighting over his comment ?!
- Adding pictures
Uploading above => Copying the link => Pasting the link in the editor => meh !
Why not copying the pic (from the clipboard) and pasting directly on the editor?
And keeping that button for the phone/tablet users.
What I hope to see
- Emojis
Seriously speaking, how can you interact with others where written words are the only medium, and there isn't an easy-to-use emoji like in Discourse (you just write a colon and they all appear in front of you).
- Markdown live-preview
Isn't it better to just check what I'm writing in a live-preview as in Discourse, instead of jumping from tap to another (Markdown / Preview) to just check how it looks :|
- More organized/simpler UI
The main page UI is a bit cluttered, and can be much simpler
Example: which one feels better for you left one or right?
What I hope to not see
- Native iOS/Android/Whatsoever app
Yeah, I'm serious... even they've already started with the iOS app in their repo!
There is always a technical debt for every repo you start, every software you write, and every small idea you wanna apply.
It's a burden that the dev team will have (for two extra repos: iOS & Android), and bugs will surely occur, and they gotta fix it.
PWA is more than enough and much more pleasant in so many ways especially the updating thing... I don't wanna see a buggy, need-to-update-via-app-store, burdensome-for-dev-team app for dev.to.
- Hostile environment
No (dislike / anger face) reaction to posts... just because you don't like someone's ideas, doesn't mean you gotta show an anger face to them, ignore it and be happy without spoiling other people happiness.
- Localization/Internationalization
I know this is a social network... but let's not forget, more languages means scattering the community into smaller portions of different language speakers :(
And yeah, "English is the lingua franca of programming", says the great Jeff (co-founder of stackoverflow) in his article here.
- Job platform
Most people here are pointing to there LinkedIn accounts in their profiles, so what's the point of adding a hiring platform (with annoying emailing/notifcations) in dev... given that HRs can check their posts/comments/github.
We all saw how stackoverflow got a bit spoiled with the job thingy.
Having said all that, tell us what do you think about it?
And, feel free to write your own DEPs ;)
Top comments (26)
If you really want emojis: browsernative.com/chrome-emoji/ . On a side note, I do believe that emojis should be an OS/browser side functionality rather than a website one... I mean, since emojis are now part of how we all communicate on the web, implementing emojis on every service is just as dumb as if every site implemented a keyboard to type words.
For the native app, even though I don't wish one myself (I never come here on a mobile device), I don't see why it would be a bad thing, if you don't want one, just don't use it (when it'll be here).
As for the rest, it's nice of you to suggest improvements for dev.to, but since it went open source recently, don't you think there would be better ways to do so? :)
Since when in the UX world you tell the users to install an extension on their browsers to use emojis :D
As for the native app read in the comment above plz.
Ah... I saw that comin', and let's be a bit transparent about it:
Dev is the dream of the three folks: Ben, Jess, and Peter. They make the profits out of their dream (all happy for them), and we are the users of their platform. We all have dreams, like I do make my own coding academy: coretabs.net (totally open-source: github.com/coretabs-academy/websit...), and a handful of other projects: github.com/coretabs
If I would write something to improve their dream (for-free), I would do it for a tool/component that I might get benefit from like: Dapper ORM used in Stackoverflow or their fast Redis client, but not for stackoverflow website itself ;)
I'm not saying telling users to install a browser extension is a good thing, just that the "emojis on websites" problem is a wider problem than a per-website issue. Also I believe the dev.to team are OSX users, they might be a little biased towards emojis with their super futuristic OS that supports emojis 😋 (that IS a joke, do not hit me 😇)
As for the last part, I was not asking you to contribute, I was just saying that the GitHub issues might be a better place to submit some of your ideas (like the simpler UI, and, for the record, I do agree with this one, at least partly) than a post here... because it will sink eventually and might never get the visibility an issue would have had.
Ah... I get it, thanks for elaborating!
Well, Github issues are good but IMO for reporting, not for discussions (at least for dev.to cuz here feels a bit better for discussing).
And yeah I agree on your point, I was just a bit lazy to take that point separately into github :D
💩
If you're on Windows you can hit "Windows Key + ." and it will bring up an emoji picker. 😎
😁
I can pretty much get behind everything you're saying. A couple things worth commenting on the "hope not to see" front:
If you look at the approach we're currently taking, any native experience is basically going to be a pretty simple web wrapper. Apple's PWA story is really really lacking right now, so we're building towards a basic native-ish experience, but really low-touch.
We're not trying to re-implement views or any complex app logic, basically present the app natively and possibly hook into some native functionality for a few specific augmentations if it seems relevant.
So on the same page there.
Same here. I agree 100% with you, the thing is: We already have a sort of job platform under the hood. We have the concept built in to your settings that you can opt in and opt out of certain job functionality. We totally hate this kind of direction you are describing and that's why (even though it's fairly experimental), you don't really even know this functionality exists unless you opt in.
There is one state in which someone might feel excited about a job opportunity: When they are looking for a job!!!
Some other platforms really miss the point here.
I think the best thing we do as an org/platform is care about the nuances of some of this stuff. We don't get everything right, but we try to be thoughtful.
Ah... I love that!
Hope it will never go through any different burdensome path ;)
Love that way of thinking again!
IMO, that's why dev continues to be a non-stop growing platform... plz keep that up ❤️
That's simple:
Jokes aside, the "heart" is nothing more than a like button and the "bookmark" one is nice for people who haven't heard of Pocket (again, joking... last one, promised). As for the unicorn, I simply see it as a fun bit, not everything has to be 100% useful 😀
The three dots are side features (link, Twitter share and abuse report).
Bookmarking actually does bookmark the article for later on your account's reading list.
Mine's pretty perpetually full of stuff... which is why I'm now coming back to this article!
Why a native app would be buggy and have to be updated every couple of days?
There is always a technical debt for every repo you start, every software you write, and every small idea you wanna apply.
It's a burden that the dev team will have (for two extra repos: iOS & Android), and bugs will surely occur, and they gotta fix it.
Why shattering the focus on the iOS & Android & web, while the PWA gives you an accessible auto-updating app for the same platforms with writing only ONE web app.
On Windows, hit the Win+. chord to get a pop-up dialog, complete with search, to pick an emoji. I think macOS has something similar.
... though I'm tempted to say that DEV should have its own emoji set, just to make sure that everybody on the site has the same ones ...
Some thoughts (btw happy to see a python guy here)
btw i see peps inspire lots of people, i know people who use it in biz in internal projects!
I actually like the unicorns and use them for stuff I really like, but that's just because I like unicorns in general.
I always thought that the heart means you like the article (or want to show some love for it or its author) and the unicorn that you find it a unique gem you don't see every day - just like unicorns (not that I've ever seen one...).
That reasoning makes sense.
Me too
To answer your question I like much better the left picture in the comparison of homescreens
Actually it's related to the design time of dev "ah what are we gonna make... like button or heart or clap?", and then the unicorn came up :D
🦄
🦄