techsin101

seems like a dismissive attitude... engineer can cost 1M a year easily and that eliminates viability of lot of small ideas. It's no different than internet servers costing thousands and then suddenly innovation makes them cost less by many factors and creating a surge in new startups.

just from pure api perspective how is setA, setB, setC better than...

this.setState({this.state: val})

which was already pushing limit of normal behavior which is

state.A = val

just to be revise

i went from having to do

state.onlineStatus = 'active'

to

const [onlineStatus, setOnlineStatus] = useState('active')

Instead of being able to get autocomplete and normal refactoring you would get from plain js.. now you need to add typescript to supplement the mess...

const obj = {

onlineStatus: 'inactive', shoppingCart: '3899x', lastActive: 1834393939 }

obj. [autocomplete anywhere in the project]

vs MORE Boilerplate

yes this as well... wrong info is worse than no info. Short var almost is like writing _list "_" indicates it's an internal property ignore it

At first I thought you were arguing against the point I made, but after reading this fully I totally agree. The worst offenders that are hell bent on naming variables as sentences are java developers. For some reason the boiler plate required by Java is no long enough for them. Lol. Joking aside, I think anywhere where the code is an API for external functions or anything like that. Having a very descriptive name and consistent convention is good, also if the variable is being carried over in a nested code or is being passed around or is being used 50 lines down somewhere then it is useful to name it in a way that is recognizable

Ultimately, I think even the choice of naming something and using a single letter communicates your intentions. If you make something a single letter then you're telling the reader that do not even worry about this variable it is just passing through, but if you need something your communicating your intentions of using this variable in the future it is more permanent in a sense

Sure, in this example user looks better. But as I said this code is not going to be existing on its own. There's going to be code preceded by this. Which is going to give a pretty good idea of what is being filtered on and you can always have comments before the code that can explain the general idea of what you're trying to achieve instead of burdening short-lived variables with a role of needing to give hints of what's going on at the expense of readability and speed of parsing mentally

If there is every time there a single variable is being searched then it means that it was not limited to that scope and by let's go. I mean in few lines front and back and if it wasn't then it should have never been a single letter variable. I see single letter variables as placeholders that are meant to live very temporarily. Few lines at best

.... Always

Yea, often vars are placeholders and making them descripting just makes them misleading and harder to get to the point. But yea at least I trust myself to refactor code and make the var name more descriptive if I see it's no longer just temporary placeholder... but would be a challenge to have others follow the same principle. One using is short name because it only helps, another to use it because you are just lazy.

I'd prefer it like this...

// get users older than 90

a = data.results;

b = a.filter(u => u.dob > 123456)

seniorUsers = b.map(x => {name: x.name, age: x.age})

// self contained

// comes out with one final var that is named to be used later on

// other vars are obviously meant to be ignored and just placeholders

// comment explains what is happening so each var doesn't need sacrifice comprehension speed

investors pay you money

you give investors equity

you use that money to pay for services, like a logo

you exchanged equity for logo, what's unclear there?

that would suck immensely for various downsides

is there a tool that uses to create UX/UI designs. It'd be really cool to get inspirations...

Unless entire team is spending 2 days on docs every week, docs are hell. I prefer comments in the code.

also Trillium and Zettlr

The illusion of a dream that kept people grinding has shattered. Housing prices doubling means that it's now clear that you will never achieve financial freedom, not that most would have but now there is no hope. Without any end goal, it's pointless to give your 100%. Now people's next goal is to make best what you are gonna get, and that is to do minimum.

only down side if vscode isn't open then it takes a while to open up

I use notepad and trying to move away from it. 1st there is friction creating new files, 2nd no search functionality, 3rd I've too much freedom to just create files anywhere.

Hey, if this is upsetting then I apologize

i actually like vscode because of shortcuts and muscle memory, this could be it

it could do what figma does, use web assembly and web workers

Just today I was telling my mom to not get iPhone for next phone if I can’t figure it out I don’t want to think what will happen to her… select a word? No.. place a cursor in a particular place? No.. double tap to select everything? No…

this is a good point

about 7 years

I won't say I'm pushed, but rather I get put a knife to throat, each time that has happened it has chipped away at my passion for programming in general. Now that I think of coding then the emotions that come up are negative. When I was a beginner emotions were positive and exhilarating, like I couldn't wait to wake up tomorrow and try this new thing. I believe it's all thanks "being pushed". I hate managers who think like this.

I do the later so I don't get stuck, i.e. if I have mastery over language/framework/etc then I'll not get stuck, because when I do get stuck my stress goes to cloud 9 and rapidly start losing hope. Spend days alternating between procrastinating and trying things which feels like putting hands on sizzling pan. But "the PROS" I've seen encounter bigger problems and move past them in a day or two, without going through entire cycle of despair.

Personally from what I've seen, yes! Recruiters don't see your founder experience as real experience. And engineering managers think you will get bored and won't like doing the grunt work.

for me jquery lib was very decent

i would disagree, if someone is highly specialized in a language X then they are going to be very resistant to learning something new. And if they have to then it'd be a slow process. They would have to learn: language, frameworks, build tools, code base, industry concepts. Compare this to someone who is already familiar with tech stack: they would be only learning code base and industry concepts.

it's becoming tiktok slowly

dark ages of A/B driven blindness