thomas_moon

The whole point of my post is that you get to pick and choose what parts this magical software automates for you. Based on your response, it's an imagination issue for you.

The only viewpoint I really agree with in this article is the "use it or lose it" mentality. Skills are developed and maintained by practicing them, but if all the author really wants to do is write code, then LLMs are literally an answer to their prayers!

You can enable virtually free test driven development. Write the test names down and let the LLM implement them for you. You save 50% of your time and you get to go to town on implementation and or optimizations.

You can have the LLM take the non-tech-counterparts description of a bug and have it point you at precise lines of code to investigate rather than grepping around a codebase you might not know well.

You can onboard to new languages, frameworks, repositories extremely fast by having a partner (the LLM) explain implementation patterns and approaches on demand! You don't even need to talk to another human being! Get your questions answered in seconds and start coding!

You can rapidly prototype. You can get immediate code reviews. You can rubber duck. You can visualize business/logic flows and code branching to better understand existing implementations. You can even have the LLM write an implementation plan for you then write the code yourself!

If you cant find a way to write more code with LLMs, its either an imagination or skill issue.

Going to reply to my own post with a disclaimer: Go with HTML instead. As soon as you even try to position photos, you need HTML and CSS haha. Mine was a bit too simple but I was optimizing for absolute lowest friction possible to writing & publishing.

I find this post a bit misleading. It seems like he didn't build a blog. He built a website with real requirements, then added a blog to it.

The title* feels a bit rage baity to be honest.

I just started my own with literally no code.

1. Obsidian to compose markdown 2. Git extension to commit and push changes to github 3. Github Pages 4. Cloudflare for image hosting

Literally write markdown, push 3 buttons, its live within 2 min.

My first post was actually about figuring it all out. Sorry if its poorly written.

https://tmunayyer.com/Projects/making-this-blog.html

TLDR: You use HTML and CSS.

I set out to make a blog in the simplest form possible a few weeks ago. Today I wanted to add some formatting when including photos in posts. It turns out I made some bad calls already when I set things up optimizing other areas like process and publishing.

Maybe someone out there will find this as funny as I did while I was writing it.

I got the idea of live streaming from this community. It takes $0 and about 90-100 minutes to start from 0. If its something you have thought about doing hopefully this helps you.

Thanks

Thats true. Along with the fact likely no one will be reading it unless I post it somewhere myself anyways, maybe the Private/Public setup was overkill haha.

I don't know who this will be helpful for, but I am trying to get out of my comfort zone and do things more in public. This is a first step.

Thanks

Thank you for this post! I have been searching for something that goes a bit deeper than most medium blog posts. I was surprised at how much of the React tidbits I have picked up through trial and error but couldn't quite articulate. It's super helpful to have it thoroughly explained all in one spot!

At work we are currently exploring/POCing a migration to RTK to manage state and redux. Something we were planning on doing is converting completely to hooks. This post probably saved us some headache and made me realize that might not be the right move.

You're right, my mistake. Believe it or not, it wasn't intentional and I just completely spaced. Edited to be much closer.

I get your point but I guess I fail to see how more obscure syntax at the time of composition helps someone understand something should be immutable. If I'm mutating inputs in a functional programming code base, syntax probably isn't the problem.

edit: wasn't to isn't

Seems to be trying to solve a problem that I would consider an anti pattern (attempting to 1 line everything). Someone else mentioned temporary vars and I think thats appropriate and equal if not better syntactically.

This example:

   // Status quo
   return filter(obj, negate(cb(predicate)), context);

   // With pipes
   return cb(predicate) |> _.negate(%) |> _.filter(obj, %, context);

   let result = cb(predicate)
   result = _.negate(result)
   result = _.filter(obj, result, context)

   return result

edits: figure out how to format code, don't omit things

In my experience, currying is usually helpful as a hack and is tolerable as long as you don't get carried away. One "curry" is fine. Two+ is really pushing it and is probably a signal that something should be refactored.

A lot of people here asking "why". Only solid example of it being the more elegant solution (in my opinion) is on the front end with redux.

Maybe you have a large amount of objects in state. Each object has many properties and is used by many components. If you are using an implementation pattern that predefines selectors, you don't want tons of different functions selecting one property each. The simpler way is a single selector that "picks" the property dynamically by currying the property name to the single, more general selector.

The early return pattern was the most effective single piece of advice I received from a senior dev on how to make my code more readable. You end up with clearer code paths than any other pattern I have seen so far and way less indentation making things look (and probably perceived) as less complex.

Pair it with naming your complex and chained expressions and suddenly you have some seriously readable code.

So far, I have never seen a valid scenario where a switch statement is actually any better than if.

TIL that you can apply to speak at conferences. I always thought it was an invite only kind of deal haha. Thanks!

While I think its comical that the author casually recommends people to go "speak at conferences", theres some really good advice here.

I came out of a Hack Reactor and started pumping out React code for a small startup. After about 6 months, I was bored and decided to take some Bradfield courses just like this article recommends and the experience has been invaluable. Seeing how some "black boxes" work in details has been super illuminating and helpful at times. The core concepts and even just the code I was exposed to moved the needle in terms of my progress quite a bit and also showed me other areas of software engineering I didn't know existed when I got started.

Location: New York

Remote: Willing

Willing to relocate: No

Technologies: Go, Javascript, HTML, CSS, React, Express, Node, PostgreSQL

Résumé/CV: https://www.dropbox.com/s/h2sg85mkod3t4is/MunayyerResume.doc...

Email: tmunayyer@gmail.com

Im a full stack developer with just over a year experience looking for my next opportunity. I have recently learned Go as I am more interested in the backend. At my most recent job where I joined as an individual contributor, after a few months I was promoted to lead developer. I am open and willing to explore any and all opportunities.

*formatting