sheriffderek

I don't disagree with the comment, though its content is of low quality.

First impressions:

Will it be easy to switch between accounts? I have my own / and then I have a company account where I follow the students and leave comments with that. So far, looks like I can only sign-out / and then sign back in.

What if I want to follow that crazy political ranter guy in my email... but I don't want it in my feed in the app? It looks like there isn't a way to filter that besides unsubscribing - which will likely lead me to unsubscribe from people - that I normally wouldn't - to keep the app feed tidy.

What if I want notifications, but only for some of my favorite publications? Looks like it's just over-all so far.

Will I be able to edit a typo of mine / in the app? Doesn't look like it.

Will I have to add this app address to my Vimeo privacy/sharing so that my included videos can be embedded in it?

S the small box of files icon an archive button? As in / "here's your box of old files" - or as in "this will archive some amount of things when you press it." It's archive all. What is this bell - probably notification settings? No. It's "Activity" - of which I have none / and I do not understand. Seems like my inbox is the activity. So, maybe comments on my publication?

Again - already wishing for a filter because my inbox is showing the exact 3 publications I don't want to see on the app and nothing more.

What will pushing the substack icon do. Nothing? Seems like it should take me "home" - to what I would presume to be my inbox. Nope. But there is an icon of an incoming mail office box thing. That's the inbox. OK. Library icon - is not good. Doesn't read as a book at all. (to me) and - my list of publications - is not a "book." So - it's not a great icon to begin with / and it looks like spit pane anyway.

Still searching for a way to flip between my own accounts.

But overall - on part with Substack - and a positive move forward. However, I would have preferred to have a better signup module that we could style to match our sites / and other added features / over an iOS app.

When viewing the docs in Dash (paid app) - the styles are the old way. Fingers crossed it stays that way.

Is there anything positive about this?

How will setting all of the type close and closer to the same size, removing any any contrast for visual hierarchy, adding muddy zeros, removing any unique character, removing any syntax highlighting differentiation, removing any visual anchors, removing underlines on inline code with links, having nothing to visually reign in rags, adding more space around just - everything, smaller button areas, and a hidden search bar... help anyone? But there's dark mode.

I know that we're going to be weirded out by any* changes... because we look at this daily - but all of these changes are exactly what the books say to "not do." I'm just totally blown away at what has happened here. I'm sorry to anyone who was on the team at this time. I mean, I'm sure you mean well. And I know that most of the docs team was let go recently. But this thing feels white labeled. Didn't they show it to anyone as they were building it? This is about "changing it" - instead of improving it. Well, it's changed! But - now it's worse. I'm pretty sure that's an objective truth. If not, please explain it to me. I'm happy to evolve. Are the jump-to links new? I like jumping to examples...

But aren't you bored to death? What do you do all day?

It's very clear and thoughtful. I can't believe that it grew so fast.

For me, I personally think that it creates more problems, but maybe it's because my components aren't all so similar.

I wrote up a similar story arch here: https://css-tricks.com/on-type-patterns-and-style-guides

I'm going to create a "Free" service where you can just "freely" choose to stop creating these totally useless and backward pieces of production art.

Then, you might see the unicorn out there in the mist... the UX person who can actually just "make the prototype" and the design system - instead of inspiring hundreds of useless meetings to deliberate over a flat perversion.

I like paying for things. Good things. And when I pay for good things... (and they are managed well) - they inspire people to make more good things.

This whole "Free" thing... is costing us all - big time.

I prefer smaller stores. Probably not going to miss them. If I can't get something local, for some reason Sweetwater has been my go-to for the last 20 years.

What I don't understand is "filed for Chapter 11 bankruptcy" == "Guitar Center, which owns nearly 300 stores across the country, said business operations will continue without any interruption."

?

"Web browsers helpfully apply default CSS styles..." Totally disagree with the idea that this is 'helpful.' Pretty site though. I think there's some good stuff here - but it's not how I'd teach it. Side-note: I love how wappalyzer says 'zero technologies detected.' That's rad. "Each layout in Every Layout is intrinsically responsive." Everything is intrinsically responsive before you force it not to be. Big respect for tackling this though. Lots of good stuff and just a bit of maybe not great stuff.

I'd be curious to know what you consider the fundamentals to be.

CSS is completely dependent on HTML. If you write poor HTML - then you've already shot yourself in the foot. If you can't learn them together - then it's really hard. People don't learn the different display types / or positioning, and then they freak out when they can't figure out why a margin-top isn't working on their inline element. I've never met anyone I consider to write decent markup or styles in any of my jobs. This is pretty good: https://maintainablecss.com/chapters/introduction/ - but it doesn't teach you CSS. It teaches you how to write maintainable CSS. MDN is the best we've got (so far)

No. No way. If you're CSS is a problem - then you are doing something really really wrong.

Once you add all of those classes, it's nearly impossible to add a developer who isn't used to it. It's also really hard for me to read. Tailwind / bootstrap etc - is a total deal breaker for me. I'll just get a different client. https://www.browserlondon.com/blog/2019/06/10/functional-css... I just can't imagine not writing CSS like this: https://maintainablecss.com/chapters/introduction

I've been using harvest for years - and It's been great. The time-tracking widget has been updated - and the invoicing is smooth.

I think the flaw in the system is land/personal property. If you have enough money to call 'dibs' on a shared resource like that, then we create a feudal system. There is no legal place to just live without paying the landowner.

I'm not actually fighting for it... or talking about bytes. I care more about keystrokes. My fingers seem to prefer lowercase. OTHERWISE I can just SOMETIMES write THINGS in weiRD cASEe FOR no REASON.. but I have to hold shift or use caps-lock and "I'd prefer not to." https://www.youtube.com/watch?v=U-9tAqdd_4Y

The browser knows what a <title> tag is, so no–the head nesting doesn't really matter. That's Google's point.

While we're at it, how about we lose the unnecessary uppercase for the doctype: <!DOCTYPE html> vs. <!doctype html>

Leaving out optional tags makes sense. These days, at least with web-apps, It's not like we are writing a <head> for every page. It's just a partial you rarely ever interact with anyway. Either leave them in or take them out. The only negative I could see is that some people may not know what's optional–think you're a dummy–and put them back in. Probably best to just follow the conventions of whatever framework you use. Save your fighting energy for trailing commas in JSON! :)

I prefer writing <heading level 1> instead of <h1> :p

Whenever I hear this argument, I think of those guys out there on the freeway laying asphalt in the middle of the night. Or those people who are dead - inside the dam's cement. They probably wish they didn't have to use tools or try new techniques or combine skills and continue to learn new ways of building complex structures. They probably wish things didn't go wrong. They probably wish there was a task manager that just put all the dirt into the wheelbarrow and rolled it where it needed to go. As we move to a computer-based way of building things, it seems that we have already become spoiled and self-deserving. It seems like most 'developers' took a "rails for zombies" tutorial and are angry that things aren't as easy as that. That's why front-end developers get paid 4 times a much as most people / to make crappy software for other developers to track their time or catalog their toys or rants with their friends about how much they hate programming. I think everyone who doesn't like writing code, should get a job on a contractor's team for a summer - if they'll have you. Then while you are thinking about how much that job sucks, dream up a new box-model CSS type thing and be the hero.

I would exclude the 3rd framework. You do not need or want to use a CSS framework if you actually understand and have experience writing CSS.

I suggest you choose to fall in love with Ember.js. She is the prettiest girl in your small town and she's really friendly. Start calling yourself a programmer instead of a coder - and help move Ember toward being, not just a framework, but an SDK for the web. Everyone can complain all they want about CSS and how it's broken etc, but no one has come up with a better solution. It's not the dark ages... in fact, it's the best time in web development so far. Developers haven't had to be 'designers' in the way they are being forced to now - with variable screen-size, and alternate UI patterns for each. HTML in little dynamic templates, variables for CSS preprocessors, ES6, and modular JS patterns. Things are wonderful. +1 for a new mental paradigm.