Ask Experienced Devs

The problem is I am using beam.ParDo to call api, to enrich my data.

pipeline | "read_csv" >> beam.io.ReadFromCsv("...") | "get_info_api" >> beam.ParDo(GetApiDoFN()) | "write_output" >> beam.io.WriteToBigQuery(...)

The problem is that api have limit. I need a way to control so it do not overload api or get 429 error.

I would like to set api call should not exceed 4 call / second.

How should I do it ?

cross-posted from: https://sh.itjust.works/post/19440902

> I want to document my debugging sessions in a text file but I don't know if anyone did this before. > > I came up with this kind of "language" that is a mix between Markdown and C++, but I still wonder if something equivalent exists already. > > > // When you click on the button > # [click button] > - A::f() > // - ... other method calls, don't document if you don't need to > > # A::f() > // "..." for "parameters" where you don't need the details > - Stuff::g(...) > - Stuff::h(...) > > // <Class> is a fake template thing to show the possible types of an object > # <SubStuffA | SubStuffB> Stuff::g(...) > - Stuff::g() {} // empty but I use v/=> for virtual call > v/=> SubStuffA::g() > v/=> SubStuffB::g() > > # SubStuffA::g() > > # SubStuffB::g() > > # Stuff::h(...) > > > I document methods in the order of appearance in the code. > > If you have any good idea about a reliable way to document a list of function calls, I'm interested!

?

Sorry for the burner account.

I have to figure out what to do with my life right now. I really enjoy programming, and honestly, of any kind. Haven't really found a kind of developing I dislike yet. I have been doing stuff for around 4-5 years by now, so I have confidence that I'm a good programmer, with the huge caveats that I've never finished any presentable project and I've never done anything with a team, I've only done solo stuff.

It seems like the logical thing to pick for a job. However, I've heard experiences of people with programming jobs and CS degrees that they're absolute hell to be in. Super long work days, absurd deadlines, crunch, and that doing a CS degree means you have absolutely zero time for anything else in your life.

Having a life like that really scares me. I'm not really a strong, disciplined person. I know I can't handle living like that. I'm scared I'll just realize I want to quit and end up having wasted years of money and work on a degree I don't want to use for anything - and that's even assuming CS college isn't that awful.

My biggest dream is doing indie game development, and it has always been that since I was a little kid, but I know that's not a safe prospect for a reliable living wage. At the same time, abandoning that dream completely would make me feel awful. So I NEED to have time to work on my own stuff.

I wouldn't go to a CS degree purely for more job opportunities, I'm sure there's a lot of things I'd be able to learn in one that I need. I just don't want to end up living just to work. I'm really only going off on rumours and experiences of other people I know though - and I don't have much of a chance of visiting a campus or talking to professors. Because of life reasons it'd have to be abroad and I'd have to do at least the first year online.

So... yeah. I'd appreciate hearing some experiences in CS degrees and in programming jobs. Is it really that bad time-wise? Is it something enjoyable?

I'm really enthusiastic about anything involved with Unix/Unix-like operating systems and their ecosystems (Mostly Linux and a bit of BSD variations). I also know a couple of programming languages including C, C++23 and OCaml. But other than doing a couple of tiny projects mainly to practice my programming skills in the languages mentioned above, most of my experience is theoretical and it comes from reading books, blogs and watching conferences.

I'm interested in gaining "actual" experience by doing systems programming related projects but I'm not sure how to get started. How do I decide on which topic to choose? A topic which would not be too overwhelming and actually achievable? And how do I gain the background knowledge needed to implement a project without ending up copying and pasting everything from existing implementations?

Thank you!

Referring more to smaller places like my own - few hundred employees with ~20 person IT team (~10 developers).

I read enough about testing that it seems industry standard. But whenever I talk to coworkers and my EM, it's generally, "That would be nice, but it's not practical for our size and the business would allow us to slow down for that." We have ~5 manual testers, so things aren't considered "untested", but issues still frequently slip through. It's insurance software so at least bugs aren't killing people, but our quality still freaks me out a bit.

I try to write automated tests for my own code, since it seems valuable, but I avoid it whenever it's not straightforward. I've read books on testing, but they generally feel like either toy examples or far more effort than my company would be willing to spend. Over time I'm wondering if I'm just overly idealistic, and automated testing is more of a FAANG / bigger company thing.

I'm thinking of ways to help people move from established software to more open, flexible forms that don't lock them to another organization.

I am professionally a software developer for 8 years and I simply don't have ideas for personal projects (Can't find any problem that I can fix with programming). At times I feel like that's natural and I shouldn't worry about it. But on the other hand, I do like to imagine having something personal that I can work on so that even if some days on my main job are not satisfying, I can always work on my hobby project and find that missing satisfaction.

End goal here is obviously to get better sleep as sometimes my mind feels dissatisfied with the day's work.

Funnily, I day-dream about the idea of already having done the boring parts (simply manifesting a project that already exists) of some personal project and only solving exciting problems in relation to adding a new feature or exciting aspects.

This creates a problem as I hate staring at a blank file not knowing what to write.

Imagine, your are a Java developer with multiple years of experience in the job. You really like working with the language.

Your employer kind of canceled most of the Java projects of the company over time and is now really focused on AI...... And AI means here: LLMs, GPT, ... Not like basic Machine learning... It's all about language models. Most of this stuff and the tools are written in Python and your employers wants you to kind of throw away your pretty good Java skills completely and start over in Python.

The new tasks would be kind of "easy"... You have to prototype "LLM bots". And that's your perspective for like at least 1.5 years. No, not real software development.. Prototyping... And that means, quick and dirty is what they want... It's also very easy to impress your employer with GPT doing things. Easy money, isn't it?

I'm in this exact situation right now and worried.. What, if I quit in 2 years and the new potential employer for a Java job asks "What have you done recently?"

I kind of liked working there and like the colleges and the salary is fine and switching the job and maybe moving away is a huge thing for me... It could get better... But maybe also worse........?

What would you do in my situation? Accepting it? Starting a rebellion? Looking for a new job somewhere else?

I've been doing some interviews lately, and my most recent one seemed to be my most promising one so far, until he started doing what he called "light tech screening" and did some trivia questions to test my knowledge on what goes on under the hood. I do admit, I should have been better prepared on the topics, and didn't do as well as I could have. At the end, he said my experience was interesting but I needed a better grasp of the fundamentals, and that we should keep in touch. Afterwards, I messaged thanking him for his time, and that I needed to review my course material, asked if he thought I should review anything specific and if I could do that for a few weeks and revisit it like he said. He suggested I do a deep dive into JS/TS to really understand what goes on and why, and would be happy to revisit it in a few weeks, and again said to keep in touch.

Does that really mean keep in touch regularly or often? Or is it just a throw away yea reach out again in a few weeks when you're ready? I'm already pretty stoked to get a second chance at this, the company seems cool and I like that they aren't weighing everything on leetcode problems. If I should keep in touch regularly, what would that even be about? I also don't want to annoy him before meeting again.

Any advice would be appreciated!

My current team runs weekly retrospectives using the Lean Coffee format. More and more, I find that the items people are bringing up aren't really important or could just be a question in Slack.

For example, someone recently made a topic for how we can test credit card payments. Another topic was navel gazing about how we use Jira and multiple team members asked "what's the problem you're hoping to solve?" to which the only answer was "That's not what I've seen elsewhere".

I'm beginning to think that there's something wrong with our format or prompts, in that we aren't identifying important issues for discussion. Perhaps the format is stale or there's no serious issues lingering each week?

Any advice on alternative formats, how to get better feedback, etc. would be greatly appreciated.

Hello! I'm making changes to a web app that involves some aria classes, and I read the docs about how they work, but I'm not real confident in my ability to construct them into something that produces a well-usable experience for someone who's using the app. Is there a good way to get direct feedback from someone who uses a screenreader, or otherwise get some evaluation on whether what I've fumbled together is actually functioning well?

Would I have to drive there myself or could I pay an on-site tech to do it for a courtesy fee? Does it depend on the company?

I've interviewed for and been interviewed by companies large and small. We all know software engineer job interviews suck. But it's hard on the other side of the table too.

One of the better places I worked for had a lightweight process of one phone screen and a four hour on-site. The company also prepared offers before the on-site interview round.

When you finished interviewing, you got a same-day yes or no answer, and if it was yes, you had the offer in your inbox within an hour.

What interview practices have you found effective?

... And by what metric?

We have a team AMA coming up with a director. Apart from the typical "what are plans/goals for the team" type questions, what else could be useful or insightful questions?

Was just wondering what's popular nowadays, maybe I find something new and better - what kind of tools are you using to access and manage databases?

I'm personally using Dbeaver a lot but honestly it feels increasingly more buggy and unreliable as time passes, every installation and update has had (unique) issues so far and there's little support. However the ease of use and some powerful, convenient, utilities in it make it preferable to others.

I'm looking for an external monitor for both programming and gaming. Currently, I'm using a 1080p monitor, but I'm tired of turning my head between the macbook and the monitor when I have to deal with 3+ windows.

So, I think a 2K monitor would be a nice improvement for my QoL, wouldn't hurt my GPU too much compared to a 4k monitor. Any suggestion or should I scrub the idea?

Hi.

I'm a dev with 3 YOE, mostly in ML and MLOps, and more and more I'm trying to pivot into traditional software engineering. As of now I'm trying to really learn the fundamentals of backend engineering (as opposed to the bootstrapping DIY learning attitude that I had during my ML roles towards backend engineering), and I'm learning Node.JS. I'm getting familiar with the the concepts and the syntax, and so far so good. But one thing that I really lack is the imagination of what a good side-project might be.

So I ask experienced devs here, can you recommend me some good project ideas to work on, to make myself a better dev?

Hi experienced devs , I am a beginner programmer. I mostly use code completion and go-to source , and rename function and objects, code-pretty. Other features not so much. What features do you use often And what features are not that useful in an IDE and can be considered bloat? P.S.- Which is that one feature that you can't live without?( sorry for sounding like tiktok wannabe)

cross-posted from: https://lemmy.blahaj.zone/post/4160765

> I am opening a woocommerce store pretty soon and I was looking through a various drop shipping/fulfilment on demand services. One of them offers their services through an API and there is some documentation on it, and how to run a test if it works correctly on my end but no information on how to "install" it on my store. > > I can send you the link to the service and their documentation page - just don't want to do it here not to doxx myself 😄 > > What is API and how do I use it? > > Many thanks

I got this article in a reply to a different conversation, and for the most part I agree with it. Gpg is old and we have better ways. I like signing my commits, I like feeling that these commits are actually and provably mine. But I'm not married to GPG like I used to be, I'd like a better way. The problem is that git used gpg for signing. I learned about this new thing called minisign and I wanna use it with git. So how do we switch? And if we can't switch, then how do we fix GPG?

For a personal project, I’m not exactly sure how to decide between cross-platform mobile frameworks (e.g. React Native, Ionic, Flutter, etc.).

I know a lot of it is use-case based, so as an example consider a highly simplified social media with creating posts with text and photo, editing your profile, and viewing/following others. What works best here and why?

For my project, I do have a web app as well built using NextJS, and I have a decent amount of experience with React. I’ve also used Flutter in the past and found it pretty easy to work with, but I’ve never tried my other options.

As far as I’m aware, most people generally recommend staying away from Ionic? I’m not exactly sure why that is or if that’s just an old sentiment.

Thanks!

I know this is a very generalized question, as it depends on the company, product, position, etc. But in general, what sets someone apart as ready for a senior position over an intermediate or junior position? Experience I would think would be a big one, but say you have a candidate that shows problem solving abilities to solve code problems, but is newer to the tech field vs someone who's been in the field x years, does the first guy have a shot without really knowing the ins and outs of working as a software engineer, hoping to pick it up quick?

I'm a senior engineer (web full-stack) at a bank. I've been doing this for about 5 years.

When I write code, I find it similar to authoring a book or even writing a poem. I love trying to write code that reads really well, has beautifully designed boundaries between dependencies, great structure and so on. I also find that I write code with a big focus on making it a joy to work with for developers that touch it later on.

I struggle with the emphasis on collaboration and quick iteration approach in this field. "Co-authoring a book" with 6 other "authors" in two week chunks just seems crazy to me. And what I've seen that passes as shippable code is also crazy to me -- but hey, "it works".

I also have never been a guy that gets overly excited about using technology to solve problems or using software to satisfy business needs. I really just like writing code, setting up development environments or CI/CD pipelines, cloud infrastructure or whatever...just for those things themselves. (Again it's like an art form to me. And I really really like reading other's well thought out code and appreciate for just that rather than the use-case or problem that the code is actually solving)

Anyone else out there like me? (Not arguing the merits one way or the other...just curious if I'm a weirdo)

Hi, by now it seems to be common knowledge that passwords shouldn't be stored in a database. Backend devs generally know to hash and salt and what-not their transmitted passwords. It seems to be well documented.

However, I wasn't exactly able to find such a clear answer for client applications accessing e.g. web APIs. For example, lets assume you were to create a Lemmy desktop application with support for multiple accounts. Ideally, that software would work like a password manager and store its master password as hash only.

However(2), sometimes users like to start said application without entering their password. Like an Email client in pleb mode. Which requires the passwords to be stored somewhere. In this case, what is the best course of action?

A friend of mine has an eCommerce company of ~30 people. They're now collaborating with an Odoo Partner to implement Odoo as their ERP. He wants me to become their Odoo Developer and Maintainer in the future. He wants me to not just know how to code, but also understand the parts the business is running. From where should I start learning?

Over the years I feel brainwashed by the thoughts of others with no willpower to affirm my own beliefs.

Simply, to me blockchain/crypto is this idea of P2P communication where the intermediate technology that “handshakes” our connection isn’t essentially governed by a centralized entity. But, “handshaking” in this world costs and gas is often times used as the processing/energy to enact this exchange.

Now, for what can be exchanged, it can be quantities of an item. Or information stored within an item. Kind of like Pass by value vs. Pass by reference, in a weird way? Or cryptocurrencies vs. smart contracts?

Now, my own belief is, comparing this system with torrenting, seeding and other technologies that existed long ago and still today. What makes “blockchain/crypto” so valuable that cannot be solved with the technology invented prior to it. To me, it seems like there is extra charge and latency and thus just more negative values overall, when the final overall goal should be this idea of exchanging information without a middle man. We still need ISPs, we still need physical wires to complete the “end-to-end” connection with a peer. So isn’t everything still fundamentally centralized?

What is it actually improving? And is my way of thinking accurate? Why can’t there be a normal P2P project handling exchange of information and/or modern fiat in the same way (Something like Paypal, but transactions have no middleman)?

Edit: The only thing I recognized was the ease of transferring money in other countries. But, that was solved pretty much in the beginning. Why didn't it just stop there? And, now with US regulations, it's much harder to buy crypto and all the fees on top of it, kind of ruins a lot of the advantages the early adopters (at least for US citizens) had.

US, Georgia if it matters.

I just got laid off. Oof. Am I missing anything? I've never been laid off or fired before so it's all new to me. Just sanity checking myself.

1. Tomorrow I'm going to write down all my job responsibilities before I forget them. For updating my resume.
2. Figure out how to file for unemployment.
3. Figure out what I need for COBRA benefits.
4. Print and sign my separation agreement.
5. Ensure I have access to my paystubs.

The obvious thing being to start applying for new jobs lol.

I'm well aware this post has been asked to death on Reddit, but I couldn't find anything relevant on Lemmy so I thought I'd give it a shot.

I'm starting my first SDE job next week, and to be honest I've never really been a dev in a professional environment before. I've had an internship where the bar was very low so I did decently, and a part-time gig where I just assigned myself tickets. Either way I've never worked on a larger team or in a specific org before.

Apart from the usual like "ask questions when you're stuck", "write proper documentation", "be proactive", and "communicate well", what are some technical things I should be familiar with to make sure I'm not bogging anyone down?

More specifically, are there concepts I should know/I am expected to know of that I might not have learned in university?

Hey everyone first time fullstack noob here, novice python, JS and CSS/HTML dev in the middle of development for a Fullstack Django React Native app, the thing is I made a mess out of my modules and nodes trying to compile with 95 no module found error on the expo CLI, I started with npm and the tried yarn since it was recommended and I ended up with a sorry mess. So since the Django backend API is already running on the messy project I'm going for the new project copy paste old code approach, the front end also has components and screens that may need a few touches but the bulk is already there. I not sure about the proper order and want to make extra sure I have the appropriate folder/project creation order so the compiling and installation is as streamlined as possible as well as the creation of the venv; on the last project I had two that had hardcoded the paths for the django folder and the frontend one since I had some issues with my project finding the appropriate folder, so that's the right approach? at which time during the creation of the projects should the venv creation happen or more precisely which project should be created first with its corresponding venv, Django or React Native Expo, since as far as I understand there's an ideal order that will create and setup some specs automatically. Any help is greatly appreciated! Thanks

Edit; To clarify a bit further I had the django server up and running and getting 200s so when deciding for a frontend approach I got sold on the CSS module separation of concerns/files from my .jsx components and screens on react native and at one point I had the npm installation running smoothly with only 5 critical vulnerabilities but the 'no module found on this folder' still popped up while trying to compile so long story short I tried almost anything that came on goggling and finally I reduced the number of errors from 98 to 95 with a tutorial but while following some instructions on expo or react native documentation it mentioned that yarn was recommended over npm so I thought what the hell, why not, and now I have a broken mess on the frontend project that seems unsurmountable so I decided to start proper and make extra sure I got the correct order as well as venv paths and such.

And does it matter if they show up on applicants LinkedIn profiles or just resumes?

(I know some ATS slurp up LinkedIn profile data, but not sure how prominently it's shown.)

TLDR: I am not talking about the CCNA material (which is great for learning networking, albeit a bit too much detail for software devs), I am asking about the certificate itself, is it worth it to spend months preparing for the certificate, spending $300 on it, passing it and then putting it on your resume? Does it matter if I am open to move to DevOps positions in the future?

Background: I am a self-taught Software dev with about 4 YOE, and in order to teach myself Networking & CyberSecurity, stumbled upon this Jeremy IT Labs UT Course on CCNA. The course has been tremendously helpful in teaching me how networks actually work. It has a lot more detail than I what I needed (the ios cli, labs & configuration etc), but it has been worth it so far (I'm on day 55). However, now I am wondering if I should spend the money and effort to actually get the CCNA certificate itself. (I know 1 course is not enough to pass that certificate, I will have to spend many more hours diving into the details, memorizing things and making connections between concepts and topics)

cross-posted from: https://programming.dev/post/466603

> I have a repository on github for a project that deals with importing/processing/sending reports to clients. There is now talk of creating a similar application for a different set of users, without the import part, but multiple send parts. The existing code base already has 90% of what the new application needs (and some extra that is not needed for this new project). > > Should I fork the existing project and make the new project, or should I use the 'import project' function on github to create a new project based on the old project, or use the commandline to mirror the old project into a new project, or something else? > > In future, there might be more projects that build on top of one of these projects with their own customizations, so I'm looking for a good approach that I can leverage again in future. > > Please advise.

What advice would you give to someone who is trying to teach themselves software development skills? I'm doing that right now, and I'm finding it easy to understand, yet difficult to implement in computer code. I want to move onto more advanced stuff, but I feel that I don't have enough experience quite yet. What skills/courses would you recommend I take? How did you get better on your coding journey? Any tips to make the process go faster? Thanks in advance!

I know other version control software exists, but does anyone use it? Why? What are the differences? All I've ever actually seen people use is git.

I'm a back-end developer who wants to play with some desktop/front-end development.

I found a C++ library and started thinking what would be the best way to wrap this library in a way so that I can create a GUI in either C# or in Typescript.

What would you recommend?

Note: I'm trying to keep the question relatively vague because I want to get some ideas to try instead of finding the solution to my specific problem. I want to learn more about how others would approach such a problem. But I can provide more details, if necessary.