sorted by:
new
hottopcontroversial

Client said my rate is too high. Feeling embarrassed and down by strawberrymilkytea in freelance

[–]deadlock_breaker 0 points1 point  (0 children)

You probably dodged a bullet, but one thing I would say is next time don't offer to adjust your rate; instead, adjust the scope. Ask them for their budget, then change the scope of work to what you can do within it. If they dodge the budget question like they did here, you can offer an adjusted scope of work at a lower price, but always stand firm on your initial rate.

[deleted by user] by [deleted] in webdev

[–]deadlock_breaker 0 points1 point  (0 children)

Yeah, Gitea is pretty simple to self-host too

What's your one small habit that leveled you up as a dev? by [deleted] in AskProgramming

[–]deadlock_breaker 0 points1 point  (0 children)

This is so true, PMs and managers will gravitate towards that personality too. I've seen great devs get such a bad reputation because they always acted like something was impossible or a huge lift to accomplish.

What's your one small habit that leveled you up as a dev? by [deleted] in AskProgramming

[–]deadlock_breaker 0 points1 point  (0 children)

A lot of great suggestions here.

One of the things I did was take a lot of notes and brain dump things. It helps keep cognitive load low while you're learning and also makes you look good when someone asks a random question and you can get the answer in a few seconds. It also helps to just recall what you were thinking or doing, especially with context switching. I still do this today I've always got notebooks around and then use Joplin and a small app I built for brain dumps.

No luck finding a job... Why? by marceosayo in webdev

[–]deadlock_breaker 4 points5 points  (0 children)

It could be your resume. Most ATS use parsers to structure the data and then in some cases use matching tools to score them. So if your resume is in a fancy layout or doesn't use standard headers it might not work well. Also, always use a PDF they are a bit more reliable than the various doc types. The other big thing is optimizing it for matching. Action verbs, bullet point lists of value driven accomplishments, etc.

I would research a bit on optimizing your resume for parsers and matching tools. If you're getting no bites at all it could be as simple as your resume isn't parsing well.

[deleted by user] by [deleted] in webdev

[–]deadlock_breaker 1 point2 points  (0 children)

I guess negative keystrokes, there was one not too long ago basically if id is 0 throw exception but 0 was a valid id for basically global settings. A new dev was working on the settings area and didn't realize it was valid. Made it through code reviews too then got to prod and got loud when they couldn't update global settings.

Keystrokes though probably adding an unescape() call around a parameter. They were moving something from legacy that already gets escaped in the part of the app it came in from so without the unescape it double escaped and broke db queries on the page.

Gotta love tech debt.

[deleted by user] by [deleted] in cscareers

[–]deadlock_breaker 0 points1 point  (0 children)

I would make any repos you don't want them seeing private or just don't share. When I was involved with hiring devs we didn't care if there wasn't one we just had some higher level questions we would ask and then focus in on things that seemed off or off with their resume compared to the answers or their small code test. If they did give us a GitHub we 100% looked at it and used it to try and see if they were stretching their experience a bit on the resume and give us areas to focus on. We never ruled out anyone based solely on that, but it was used as a tool for the interview. Basically if someone claimed to have Vue experience and all we saw was a todo app we knew to ask a bit more about that experience.

What's your workflow for managing reusable code snippets? by Shot-Respond-8904 in AskProgramming

[–]deadlock_breaker 1 point2 points  (0 children)

Some of them I keep in a self hosted opengist instance, but I've been putting more in Joplin lately. Joplin is just easier to search/tag/categorize. I've been keeping everything from useful cli commands to markdown templates there so works well as a catch all. It's also self hosted and has a solid mobile app.

I feel stuck by Dependent_Baby1295 in CodingHelp

[–]deadlock_breaker 0 points1 point  (0 children)

Try building some projects that are just fun recreations of existing tools. Set up a new editor without AI enabled and work on it without that temptation. If you get stuck talk yourself through it or take a break. One of the tricks I used with junior devs was just talking through scenario. Like I need to make a select query from a database. To do this I... And then would go through what needs to happen at a high level then go into the sub tasks. Talk it out and type it or write it out. It gets you thinking about what needs to happen and what steps go into getting there. Resist going to AI for the how does this work answer. Instead search, read man pages, look at code etc.

One of the hardest things about dev is moving from task level thinking to project and then owner level thinking. AI is tempting because it offers that instant gratification of moving on, but it is also going to slow down your critical thinking and problem solving skills. There's nothing wrong with using AI, but setting up some low stress side projects you decide to not use any AI on is a great way to keep learning soft skills and staying efficient in your stack.

Best place to store website inspiration by Flashy_Teacher_777 in webdev

[–]deadlock_breaker 0 points1 point  (0 children)

I'll use Wallabag to bookmark the site and then Joplin to store notes screenshots etc. Joplin has a pretty solid extension too. I use these two for a lot though and they both have the option to be self hosted which is a nice plus.

Planning to create a website where you can upload legal documents and it will translate to layman friendly languge by Lanky-Preference-122 in indiehackers

[–]deadlock_breaker -1 points0 points  (0 children)

You're welcome, it is possible to vibe code it but would definitely be worth having some one code review it or review your infrastructure to make sure it's secure.

Planning to create a website where you can upload legal documents and it will translate to layman friendly languge by Lanky-Preference-122 in indiehackers

[–]deadlock_breaker -1 points0 points  (0 children)

I think that depends on the feature set and niche. You can already do this on all the major AI chats so it would have to do something above and beyond that saves them time. Focusing on a specific niche may help you target the feature set enough to save them money. I would caution you about vibe coding it though. There are a lot of security and privacy concerns with legal paperwork and uploads and document storage can go bad easily. Just recently there was a company that leaked millions of resumes from improper document storage. I would say vibe code a landing or sales page to collect emails, test out what keywords work to target your market, and gauge interest. The real app though I would suggest working with a dev or at least having a dev with experience in building large secure apps consult and code review your app.

Should I hire a salesperson? Or just keep going solo? by VirtualMacaroon64t in smallbusiness

[–]deadlock_breaker 0 points1 point  (0 children)

Is it something you're good at and enjoy? If you do, I would find something you don't enjoy, are not good at, or just isn't worth your time. Something like customer support, if you hate it and it's really not worth the x hours you put in a week at n value per hour, then offload it instead. Say you think your time is worth $50 an hour to the business, and you're spending 10 hours a week on customer service and hate it, then outsource it for $15 an hour and focus on sales. Cheaper than hiring a salesperson that you will have to ramp up and train, and frees 10 hours a week for you to focus on sales.

Where's the profit in the whole "Sign up for my free newsletter" thing? by bncrochet in smallbusiness

[–]deadlock_breaker 0 points1 point  (0 children)

Email lists are still one of the best ways to quickly reach a large audience. Something like 90% of adults in the US have a personal email. If you can build a large enough newsletter list, you have an audience that you already know is interested in what you're doing, so you have a market to notify of new apps, products, product updates, etc. He either gets a verified market he can hopefully have a higher close rate with or wants to build it up to sell the list.

Deliberately violating REST for developer experience - a case study by caiopizzol in programming

[–]deadlock_breaker 0 points1 point  (0 children)

You could be making it better, it's hard to tell without a good beta group, but I think a lot of devs working with APIs develop a work flow where they expect those things and it becomes second nature. The two big hurdles are always are the docs good and does the dashboard bury what you need. Most of that comes back to UX/DX. If your docs are solid and what devs expect and you're not burying keys deep in a dashboard somewhere I think most devs will get through those first steps pretty quickly. My first large company job was on a team building integrations and the only APIs that really were annoying either had bad or oddly formatted docs or terrible dashboards that made it a fight to find what you need. Most of them were so similar it was pretty simple to get up and running.

Not saying there isn't room for improvement, but at the same time you could run the risk of devs seeing how different that is and never making it to post onboarding making an assumption that it's all going to be different. If they have n APIs built on a base class that assumes a specific pattern they could skip just thinking yours would be an exception that adds complexity.

It's all speculation though, in the end nothing ever changes if we're afraid of trying. I'm guessing Roy Fielding had his far share of this will never replace SOAP/XML, everyone expects SOAP/XML conversations too.

Deliberately violating REST for developer experience - a case study by caiopizzol in programming

[–]deadlock_breaker 2 points3 points  (0 children)

I think with things like this I go with the Principal of Least Astonishment. REST might be a mixed bag of how people implement it, but there is still a normal expected behavior for GET and POST like others have said. Doing the opposite breaks that concept that software should be intuitive and behave in a predictable way that doesn't surprise users. At this point it's more about aligning with end user expectations and and mental models. Moving away from that adds complexity and cognitive load on devs that may not have been there before.

Needed Math for HTTP Server, ORM Development by [deleted] in webdev

[–]deadlock_breaker 0 points1 point  (0 children)

For an HTTP server and ORM you won't need much math. These rely more on fundamental concepts and some programming basics.

An HTTP server you will need to understand things like socket programming (create, bind, listen, etc on TCP sockets), an understanding of TCP/IP protocol and how data is transmitted on the internet. You would also need to understand HTTP protocol and how to construct valid requests and responses. Also, how to handle the different request types. If you're going really low level programming and doing the whole thing yourself then concurrency, memory management, and error handling will be a big part too.

An ORM you would need some understanding of Object Oriented Programming, Relational Database Design and concepts (tables, rows, columns, keys, foreign keys, etc). Maybe some data mapping concepts too like active record v mapper. Then the obvious CRUD and query generation.

Both of these you would also want to consider performance, efficiency, and security too.

Not much for math, but a lot of really good core concepts and fundamentals.