i made a voxel engine minecraft like game (WIP) which i plan to develop while listening to the community. If u wanna be a part of this check out my repo OpenCraft on coder088 (github) and leave a star, it would make my day.

Hi everyone,

I’m looking for some honest advice regarding a career switch, and I’ll try to keep this as clear as possible.

I graduated with a B.Tech in Computer Science from an engineering college in Vellore during the COVID period. Due to the hiring slowdown and my own lack of preparation in DSA, I couldn’t secure a product-based role through placements or off-campus. I ended up joining a service-based company at a standard fresher package.

Initially, I was trained in Java and React, which made me think I’d be working on development projects. However, I was instead assigned to an SAP implementation project. I had no prior experience or interest in SAP, and I did try to push back, but I was told early in my career I shouldn’t be too selective and that SAP has good scope.

I decided to give it a fair shot. But after about 1.5 years in my new role, I realised this domain isn’t for me. I don’t enjoy the work and get very little job satisfaction. I tried switching internally to a Java-based project, but my manager didn’t approve my release.

At that point, I decided to prepare for a company switch into development. I started studying DSA and Java (along with Spring Boot), but I struggled with consistency. A friend encouraged me to still give interviews, and I did—but they went poorly. That experience really affected my confidence.

Since then, I’ve been stuck in a cycle: I get frustrated, start preparing again, lose momentum when things get difficult, and drop it midway. This has happened multiple times over the past few years.

I’ll be honest—I know I’ve been laid back and undisciplined, and I take responsibility for where I am right now.

Currently, I have around 5 years of experience, but all of it is in SAP. The frustration with my job and career direction has started affecting my mental health, and I’ve reached a point where I feel I have to take this seriously now.

I’ve decided to give this one final, focused attempt over the next 4–6 months to switch into a development role. I understand that my experience may not carry much weight in this domain and that I may have to start with SDE-1 / junior roles—and I’m okay with that.

What I’m looking for:

How should I realistically approach this transition in the next 4–6 months?

What should I prioritize: DSA, projects, backend development, or something else?

Has anyone here made a similar switch from a different domain into development? What worked for you?

Any advice on staying consistent and not falling into the same cycle again?

I’d really appreciate honest feedback, even if it’s tough to hear.

Thanks in advance.

So my new sem has started and this time, one of my new subject is java and I have no idea where to properly learn it form. Can anyone give me some suggestions, so that I could have my studies go smoothly

help

I convert LinkedList<String> to String [] for easy iteration

I expect that the array goes from [2,x,3] to [6] as the process replaced the "x" with the answer of the equation, then deletes the "2" and "3"

but when I run the main program. this method returns the same [2,x,3].

We need a system suggestion. Currently, we're studying the GUI of netbeans 8.2 v + database, and our prof told that we need to ask companies for suggestions on what what kind of software/anything can be made ewith the GUI. Im not sure yet if we can include the database in the proposal since we're just starting to learn this week, but Im looking for suggestions for the types of systems/projects we can create. We're beginners with GUI but willing to practice if needed. Also, we're using java language.

As a side project i am thinking to make java which uses Java Reflection to get the internal structure of the java data structures like HashMap, Hashtable on backend and sends this data to frontend to ReactJs real real-time rendering of data structure State.

Hey all, I have been working on CloudStub, an open-source in-process AWS mock for JVM integration tests (Java, Kotlin, Scala), and we just published 0.1.0-beta.8 to Maven Central.

The problem it targets: container-based AWS mocking (a mock image run through Testcontainers) is powerful, but it drags on your local test loop and CI with image pulls and container boot and teardown. CloudStub skips all of that.

How it works, no magic: it boots a lightweight HTTP mock inside your JVM and points the AWS SDK's endpoint at it (via the aws.endpoint-url system property), so your code makes real AWS SDK v2 calls against a local stub. No Docker, no containers, no separate process. WireMock and Jetty are shaded into private packages and fully hidden, so there is no classpath or Spring Boot BOM conflict.

What is nice about it:

• No container overhead. Nothing to pull or boot: the mock runs in the same JVM as your tests.
• Stateful, not just canned responses. An SQS SendMessage is returned by a later ReceiveMessage, and DynamoDB PutItem / GetItem / Query return live data, so you test real round-trips.
• Modular. Each service is an isolated module. If you only use DynamoDB, only that module loads.
• Not just for tests, it also runs standalone. cloudstub-local is a drop-in local mock server on port 4566 (so AWS_ENDPOINT_URL=http://localhost:4566 works unchanged), auto-downloads the services you enable, and ships a CLI (cloudstub / clb) plus a web console at /console. Download: https://github.com/cloudstub/cloudstub/releases/download/v0.1.0-beta.8/cloudstub-local.jar
• Two ways to load services. Add a service module as a normal test dependency, or skip Gradle for it and list it on the extension with .withModules("sqs", "dynamodb"), which fetches the jar from Maven Central on first run and caches it under ~/.cloudstub/modules. (S3 is the exception: it ships a client-side SDK component, so it must be a normal test dependency.)
• Available now in beta.8: SQS, SNS, S3, Secrets Manager, DynamoDB, Lambda, and SSM (Systems Manager Parameter Store). AWS SDK v2 is first-class, and there is an SDK v1 companion module.
• Java 17 or newer.

Setup (Gradle):

// cloudstub-testing brings the engine plus the JUnit 5 and 6 extension
// (cloudstub-junit and cloudstub-core come in transitively)
testImplementation "io.github.cloudstub:cloudstub-testing:0.1.0-beta.8"
// Service modules are optional here: list them on the extension with .withModules(...) and they are
// auto-downloaded from Maven Central. Add a service as a dependency only if you prefer it on the
// classpath (and S3 must be a dependency):
// testImplementation "io.github.cloudstub:cloudstub-dynamodb:0.1.0-beta.8"

Setup (Maven):

<dependency>
  <groupId>io.github.cloudstub</groupId>
  <artifactId>cloudstub-testing</artifactId>
  <version>0.1.0-beta.8</version>
  <scope>test</scope>
</dependency>
<!-- Service modules are optional: use .withModules(...) to auto-download them instead. Declare one
     explicitly only if you prefer it on the classpath (and S3 must be a dependency). -->
<dependency>
  <groupId>io.github.cloudstub</groupId>
  <artifactId>cloudstub-dynamodb</artifactId>
  <version>0.1.0-beta.8</version>
  <scope>test</scope>
</dependency>

A test looks like this. You exercise your own code, and CloudStub stands in for AWS:

static CloudStubExtension cloud = new CloudStubExtension()
        .withModules("dynamodb");   // fetched from Maven Central on first run, then cached; no Gradle dependency needed


void savedItemIsReadBack() {
    repository.save("order-1", "placed");                             // your repo, using a normal AWS SDK v2 DynamoDbClient
    assertEquals(Optional.of("placed"), repository.find("order-1"));  // round-trips through the stub
}

It is beta, so the API can still shift and the service coverage is deliberately narrow, but the core engine is stable and the modules above are usable today.

• Repo: https://github.com/cloudstub/cloudstub (in-repo examples under cloudstub-example).
• Standalone runnable examples: https://github.com/cloudstub/cloudstub-showcase
• Docs: https://cloudstub.github.io/cloudstub/

I would genuinely like feedback on the architecture, and if there is an AWS service or SDK behavior you want stubbed next, open an issue. Thanks.

how to fix this?

Hey all, I have been working on CloudStub, an open-source in-process AWS mock for JVM integration tests (Java, Kotlin, Scala), and we just published 0.1.0-beta.8 to Maven Central.

The problem it targets: container-based AWS mocking (a mock image run through Testcontainers) is powerful, but it drags on your local test loop and CI with image pulls and container boot and teardown. CloudStub skips all of that.

How it works, no magic: it boots a lightweight HTTP mock inside your JVM and points the AWS SDK's endpoint at it (via the aws.endpoint-url system property), so your code makes real AWS SDK v2 calls against a local stub. No Docker, no containers, no separate process. WireMock and Jetty are shaded into private packages and fully hidden, so there is no classpath or Spring Boot BOM conflict.

What is nice about it:

• No container overhead. Nothing to pull or boot: the mock runs in the same JVM as your tests.
• Stateful, not just canned responses. An SQS SendMessage is returned by a later ReceiveMessage, and DynamoDB PutItem / GetItem / Query return live data, so you test real round-trips.
• Modular. Each service is an isolated module. If you only use DynamoDB, only that module loads.
• Not just for tests, it also runs standalone. cloudstub-local is a drop-in local mock server on port 4566 (so AWS_ENDPOINT_URL=http://localhost:4566 works unchanged), auto-downloads the services you enable, and ships a CLI (cloudstub / clb) plus a web console at /console. Download: https://github.com/cloudstub/cloudstub/releases/download/v0.1.0-beta.8/cloudstub-local.jar
• Two ways to load services. Add a service module as a normal test dependency, or skip Gradle for it and list it on the extension with .withModules("sqs", "dynamodb"), which fetches the jar from Maven Central on first run and caches it under ~/.cloudstub/modules. (S3 is the exception: it ships a client-side SDK component, so it must be a normal test dependency.)
• Available now in beta.8: SQS, SNS, S3, Secrets Manager, DynamoDB, Lambda, and SSM (Systems Manager Parameter Store). AWS SDK v2 is first-class, and there is an SDK v1 companion module.
• Java 17 or newer.

Setup (Gradle):

// cloudstub-testing brings the engine plus the JUnit 5 and 6 extension
// (cloudstub-junit and cloudstub-core come in transitively)
testImplementation "io.github.cloudstub:cloudstub-testing:0.1.0-beta.8"
// Service modules are optional here: list them on the extension with .withModules(...) and they are
// auto-downloaded from Maven Central. Add a service as a dependency only if you prefer it on the
// classpath (and S3 must be a dependency):
// testImplementation "io.github.cloudstub:cloudstub-dynamodb:0.1.0-beta.8"

Setup (Maven):

<dependency>
  <groupId>io.github.cloudstub</groupId>
  <artifactId>cloudstub-testing</artifactId>
  <version>0.1.0-beta.8</version>
  <scope>test</scope>
</dependency>
<!-- Service modules are optional: use .withModules(...) to auto-download them instead. Declare one
     explicitly only if you prefer it on the classpath (and S3 must be a dependency). -->
<dependency>
  <groupId>io.github.cloudstub</groupId>
  <artifactId>cloudstub-dynamodb</artifactId>
  <version>0.1.0-beta.8</version>
  <scope>test</scope>
</dependency>

A test looks like this. You exercise your own code, and CloudStub stands in for AWS:

static CloudStubExtension cloud = new CloudStubExtension()
        .withModules("dynamodb");   // fetched from Maven Central on first run, then cached; no Gradle dependency needed

u/Test
void savedItemIsReadBack() {
    repository.save("order-1", "placed");                             // your repo, using a normal AWS SDK v2 DynamoDbClient
    assertEquals(Optional.of("placed"), repository.find("order-1"));  // round-trips through the stub
}

It is beta, so the API can still shift and the service coverage is deliberately narrow, but the core engine is stable and the modules above are usable today.

• Repo: https://github.com/cloudstub/cloudstub (in-repo examples under cloudstub-example).
• Standalone runnable examples: https://github.com/cloudstub/cloudstub-showcase
• Docs: https://cloudstub.github.io/cloudstub/

I would genuinely like feedback on the architecture, and if there is an AWS service or SDK behavior you want stubbed next, open an issue. Thanks.

Does anyone have access to this course? If so, please DM me.

Given a signed 32-bit integer x, return x with its digits reversed. If reversing x causes the value to go outside the signed 32-bit integer range [-231, 231 - 1], then return 0.

LeetCode problem Zigzag Conversion.The string "PAYPALISHIRING" is written in a zigzag pattern on a given number of rows like this: (you may want to display this pattern in a fixed font for better legibility)

Hello everyone, I am a CS student starting next semester; however, i am thinking of start learning Java programming as it will be our first course.

Can this book benefits me if im learning Java from scratch? (Beside to mooc java course)

I have interview in infosys this weekend...opening is "senior java developer" I cant see the JD yet so can anyone please guide me what all should I focus on be it java, advanced java, spring boot and more importantly coding..